What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

[SOLVED] Unable to launch? v1.1.2952.455

E

eroj1

New Member
Joined
Feb 20, 2016
Messages
8
Reaction score
0
I just downloaded the latest build and reinstalled using the installer, but when I try to launch, it spits out the following error. Repeat reinstall did not help, nor did running as administrator. Anyone else having this problem?

Code: 
System.IO.FileNotFoundException: Could not load file or assembly 'GreyMagic.dll' or one of its dependencies. The specified module could not be found.
File name: 'GreyMagic.dll'
   at Demonbuddy.MainWindow.*‫‎‪*‏*****‏‪*‫‪‬​‏***‏​‬*‎‏**()
   at Demonbuddy.MainWindow.s(B3x\[Kns0$\,5>Qs7\,\]sMnR##.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Demonbuddy.MainWindow.@|wd"{w\.A(`\.L# CmJ\,0/my\&.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)


System.IO.FileNotFoundException: Could not load file or assembly 'GreyMagic.dll' or one of its dependencies. The specified module could not be found.
File name: 'GreyMagic.dll'
   at Demonbuddy.MainWindow.*‫‎‪*‏*****‏‪*‫‪‬​‏***‏​‬*‎‏**()
   at Demonbuddy.MainWindow.s(B3x\[Kns0$\,5>Qs7\,\]sMnR##.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Demonbuddy.MainWindow.@|wd"{w\.A(`\.L# CmJ\,0/my\&.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
 
Hi, Eroj1,

The first thing to check is make certain your Antivirus isn't removing the needed file. This article will walk you through the process:

If that is not the issue, then we need to do a 'clean install'. In this article, substitute "Demonbuddy" for "Honorbuddy:

As stated in the article, please be certain to use a NEW directory for the installation.

cheers,
chinajade
 
This is a fresh Windows 10 install, and I do not have any antivirus software on the system at the moment. I ran the installer as admin just to make sure. The default path was going to Documents but even if I change it to C:\ it still showed the same error on launch.
 
eroj1 said:
This is a fresh Windows 10 install, and I do not have any antivirus software on the system at the moment. I ran the installer as admin just to make sure. The default path was going to Documents but even if I change it to C:\ it still showed the same error on launch.
Click to expand...
Hi again, Eroj1,

You cannot install the to root of a drive and have it work (e.g., C:/). The Buddy bot must be in a sub-directory (e.g., C:/Demonbuddy/).

cheers,
chinajade
 
Right, that is what I meant. It is currently in C:\Demonbuddy\
 
Hi again, Eroj1,

Please show us a full log of the 'clean install' we asked you to perform.

cheers,
chinajade
 
So the error message is exactly the same and the log reflects that same error, so I don't know how helpful it'd be. It also appears someone else is having the same problem. In any case, please see attached log.
 

Attachments

Hi again, Eroj1, and thanks for the fresh log.

Let's try running this tool with Windows administrator privileges:

It may show up as having a virus, but double-checking with the senior staff, its clean and a heuristic problem with several virus checkers at the moment.

cheers,
chinajade
 
Last edited:
Hi again, Eroj1,

Thanks for the follow-up, and glad you are off-and-away!

cheers,
chinajade
 
You must log in or register to reply here.
Back
Top