What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Not a valid instance

caellyn65

New Member
Joined
Mar 25, 2012
Messages
28
Reaction score
0
I get the following error when logging into honorbuddy.

-------------------------------
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 #15354
You are currently on build #0
-------------------------------
Honorbuddy is up-to-date

I have checked that I have the following settings:

WoW 32 bit client (NOT 64 BIT CLIENT)
WoW in Windowed mode (Menu --> Options --> Graphics --> Display Mode: Windowed (NOT FULLSCREEN))
WoW in DX9 mode (Menu --> Options --> Advanced --> Graphics API: DirectX 9 - requires client restart)
WoW & HB must be ran as Administrator
Net framework 3.5 sp1 installed

I have reinstalled it a couple of times.

There is no botting dropdown menu after logging into honorbuddy either.

I have run it before and after loggin into my toon in wow.

Please help:)
 
Can you attach the log in your HB, logs folder? make sure to edit names in the log.
 
Problem solved.

HB doesn`t support WoW 64 bits and directx 11. Just open the old WoW.exe and run it on dx 9.

Thanks :)
 
My logs

This is the only log in my honorbuddy logs folder:

[8:51:31 AM:235] Logging in...
[8:51:32 AM:760]
[8:51:33 AM:782] -------------------------------
[8:51:33 AM:782] You have not selected a valid instance of WoW to attach to!
[8:51:33 AM:783] Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
[8:51:33 AM:783] This version of Honorbuddy only supports WoW Build #15354
[8:51:33 AM:784] You are currently on build #0
[8:51:33 AM:784] -------------------------------
[8:51:38 AM:038] Honorbuddy is up-to-date
 
Are you logging into wow first then launching HB as Administrator?
 
This version of Honorbuddy only supports WoW Build #15354
You are currently on build #0

this is caused by 2 things:
full screen
private server

well, 3 if you count W8; we don't support W8
 
I apologize, I had changed all settings before running wow as admin. Once I changed to run as admin, I forgot to change the settings again.

thank you and again I apologize for not catching that.
 
dont worry mate
thats why we are here :)
 
Back
Top