Honorbuddy stops at login

Fresh reinstall 3 times, no Plugins. Cleared Cache. Tried 2 different WoW folders.

Honorbuddy starts, asks for key, and stops on next screen where I get only

Honorbuddy v2.5.10945.744 started.
Logging in...
T: 5247079914074741866 H: 1778574014

Tried using Launcher - same thing. Checked my Firewall, disabled Antivirus.
Only way I can get it to work is by using HBrelog, when it logs in normally.

 

Tony, i checked out all the programs listed, got razer synapse but i closed all the process related to him and still have the problem.

I closed almost EVERY process that i dont need on my computer.

I didnt used my honorbuddy in a almost an year... can that be any problem with my key?

Thanks

 

[20:41:40.022 N] Honorbuddy v2.5.8844.708 started.
[20:41:41.242 N] Logging in...
[20:41:48.771 N] H: 4058516651
[20:41:49.777 N] There was an error during a server request. Please inform a staff member!
[20:41:57.970 N] Authentication failed!

 

really?
[20:41:40.022 N] Honorbuddy v2.5.8844.708 started.

we're on like 744 now buddy.

if you would, please post a full log as an attachment so we can see whats going on.
[Guide] How to attach your log

Download the latest version of honorbuddy.
http://updates.buddyauth.com/GetNewest?filter=Honorbuddy
Then do a clean install into a new folder. Do not reinstall over a previous installation or move items from the old installation into the new one.

 

Same problem here. :/


[22:58:31.017 N] Honorbuddy v2.5.11034.745 started.
[22:58:32.659 N] Logging in...
[22:59:03.630 N] T: 5247087133854484436 H: 2766846572
[22:59:06.562 D] System.ComponentModel.Win32Exception (0x80004005): Somente uma parte de um pedido ReadProcessMemory ou WriteProcessMemory foi concluída
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
at System.Diagnostics.Process.get_MainModule()
at GreyMagic.MemoryBase.get_ImageBase()
at GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
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)

 

no its not the same issue, if you need help, you need to make your OWN thread. never post in a support thread you did not create.

 

As it is not the same issue? The logs are equal. I would make a new thread, I not maked by the similarity of the logs. But ok, after a couple of days this problem did not occur anymore.