First post..ever and I cannot find the "advanced" option anywhere. So my apologies in chrome at the moment. I did recently download the new visual basic 2013 as well from a previous post I read. Login like normal, key is still active and got the update yesterday. Log file will be attached but it is just stuck at logging in. Honorbuddy v2.5.12136.758 started. Logging in... T: 5247216599141216669 H: 1057416930 log file: [18:55:46.556 N] Honorbuddy v2.5.12136.758 started. [18:55:48.523 N] Logging in... [18:56:00.709 N] T: 5247216588020270587 H: 2381394247 [18:56:02.706 D] System.IO.FileLoadException: Could not load file or assembly 'RemoteASM, Version=2.5.12136.758, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'RemoteASM, Version=2.5.12136.758, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda' at GreyMagic.ExternalProcessMemory.Init(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh) at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm) at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits) at Honorbuddy.MainWindow.HandleSuccess() at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) 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].
You're not alone here. I am having this same issue. There are some days / times where I am able to login and a majority where I am unable to. I hope they get back to us with a solution.