Hello, I've tried multiple things to get it to work such as running as administrator, restarting my computer, and redownloading HonorBuddy. Here is my log below, if you could help I would appreciate it! Thanks! Code: Logging in... Error attaching Honorbuddy to WoW! - System.TypeInitializationException: The type initializer for 'MainDev.RemoteASM.RemoteAsm' threw an exception. ---> System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. at System.Reflection.Module._GetTypesInternal(StackCrawlMark& stackMark) at System.Reflection.Assembly.GetTypes() at (Object ) at MainDev.RemoteASM.RemoteAsm..cctor() --- End of inner exception stack trace --- at MainDev.RemoteASM.RemoteAsm..ctor() at Styx.WoWInternals.ObjectManager.Initialize(Memory blackmagic) at Honorbuddy.MainWindow.#TUc() ------------------------------- You have not selected a valid instance of WoW to attach to! Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with! This version of Honorbuddy only supports WoW Build #15050 You are currently on build #15050 ------------------------------- Honorbuddy is up-to-date
after updating .net 3.5 sp1 did you restart wow? after changing from dx11 to dx9 did you restart wow?
it shouldnt have net framework issues on Win 7 since it comes with windows installation(unless something is broken) to the OP make sure that you have all the latest Windows updates
before trying it again and after your updates make a new Hb installation from scratch and make sure that all Hb files are under the same folder(including the exe and run Hb exe from the folder not from a shortcut or something)
happened to me few times. what i did was 1. restart HB few times. or reinstall it. 2. run wow, login and get into character. then when run HB, quickly click wow window. that solved it for me somehow.
Nope this did nothing EDIT: I've disabled anti-virus, UAC, etc. I have also redownloaded HB plenty of times. If anyone has fixed this error before I could use some help.