View attachment 796 2016-10-30 13.09.txt /edit I noticed I was supposed to include this file? Hope this helps!
I have scoured the forums and tried many of the solutions but still cannot start Demon Buddy. Any quick solutions would be fantastic!
I receive the following:
Error while initializing memorySystem.IO.FileLoadException: Could not load file or assembly 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0'
at GreyMagic.Executor.InjectDetour()
at GreyMagic.Executor.InitializeDetour()
at GreyMagic.Executor..ctor(ExternalProcessMemory memory, ExecutorInitParams initParams)
at GreyMagic.ExternalProcessMemory.***********(ExternalProcessMemoryInitParams )
at GreyMagic.ExternalProcessMemory.***********(Process , Boolean , Boolean , Boolean , IntPtr , Boolean , Int32 , Boolean , Boolean )
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at Zeta.Game.ZetaDia.TryInitialize(Process proc, String& reason)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Error attaching to Diablo III, Reason:System.IO.FileLoadException: Could not load file or assembly 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0'
at GreyMagic.Executor.InjectDetour()
at GreyMagic.Executor.InitializeDetour()
at GreyMagic.Executor..ctor(ExternalProcessMemory memory, ExecutorInitParams initParams)
at GreyMagic.ExternalProcessMemory.***********(ExternalProcessMemoryInitParams )
at GreyMagic.ExternalProcessMemory.***********(Process , Boolean , Boolean , Boolean , IntPtr , Boolean , Int32 , Boolean , Boolean )
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at Zeta.Game.ZetaDia.TryInitialize(Process proc, String& reason)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Session with specified sid does not exist in NorthAmerica region.
I have scoured the forums and tried many of the solutions but still cannot start Demon Buddy. Any quick solutions would be fantastic!
I receive the following:
Error while initializing memorySystem.IO.FileLoadException: Could not load file or assembly 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0'
at GreyMagic.Executor.InjectDetour()
at GreyMagic.Executor.InitializeDetour()
at GreyMagic.Executor..ctor(ExternalProcessMemory memory, ExecutorInitParams initParams)
at GreyMagic.ExternalProcessMemory.***********(ExternalProcessMemoryInitParams )
at GreyMagic.ExternalProcessMemory.***********(Process , Boolean , Boolean , Boolean , IntPtr , Boolean , Int32 , Boolean , Boolean )
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at Zeta.Game.ZetaDia.TryInitialize(Process proc, String& reason)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Error attaching to Diablo III, Reason:System.IO.FileLoadException: Could not load file or assembly 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Udis86Net, Version=1.0.5912.35682, Culture=neutral, PublicKeyToken=9e501ca4ffc4eff0'
at GreyMagic.Executor.InjectDetour()
at GreyMagic.Executor.InitializeDetour()
at GreyMagic.Executor..ctor(ExternalProcessMemory memory, ExecutorInitParams initParams)
at GreyMagic.ExternalProcessMemory.***********(ExternalProcessMemoryInitParams )
at GreyMagic.ExternalProcessMemory.***********(Process , Boolean , Boolean , Boolean , IntPtr , Boolean , Int32 , Boolean , Boolean )
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at Zeta.Game.ZetaDia.TryInitialize(Process proc, String& reason)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Session with specified sid does not exist in NorthAmerica region.
Last edited:






