32 bit version gone, as of 22-11-17?

Hello buddy's and @Tony . Tony you were active in another topic where someone said that the 32 bit version was removed from the launcher. I spoke there also and said that this was NOT the case. Which at that point wasn't the case. I just now saw that it suddenly after a Battle.net update done by Blizz today, the 32 bit option is removed? Tony could you tell me what this means for us and if we will have a downtime etc?

If you want you may PM me. Kind regards, Drhorror!

 

The blizzard forums are not too clear on this and no ones giving a clear answer there.

 

Assuming the war between Honorbuddy and Blizz. is still heated and ongoing, they might do these things to disrupt the botting software? @Tony : I think you know a little bit what is going on. Maybe you don't wanna be public about it, but i would like to know what is going on. Could you PM me or give us an update? Many of us don't know what is going on, and on my botting account i have been delayed this much currently, that i have to pay for new subscription. The downtime was too insane, so i havent been able botting the gametime all together + extra's for goldselling.

 

The 32bit exe is still there but in battle.net it is gone

I say they are going to remove support soon and make it 64 bit only as it is faster and more safer

 

All I can say Tony it is odd

 

Not before the next expansion.
Legion was originally offered to support both 32bit and 64bit Windows systems, so revoke on one would make them into legal troubles.
But for BfA I suppose they would cease the support for both Windows 7 and Windows 7 64bit. But considering Microsoft still does support 32bit Windows 10, I doubt Blizz would leave this platform uncovered.

 

The "Launch 32 bit client" instead of 64 bit is now removed from the battle.net launcher for WoW. That doesn't mean 32 bit can not still be launched just that the option is removed from blizzards launcher.

 

ok, instead of telling everyone the option is still there and we only have to restart bnet app...
we could be a little more constructive and launch the wow.exe with command line option -noautolaunch64bit

 

How can we do that?

 

I knew there was a workaround for this issue, and i also looked in the same interface, but this code must do the job. I test it tommorrow. Very nice. Too bad my bot is two days delayed now xD! I wish the HB support gave us more and better guidance...... @Tony Not too hard to write that code for us? :/....

 

This is a preview of what's to come but as AION said it won't be before next expansion which more than likely is Sep to Nov 18. I think where we differ is I believe they don't care about Windows 10 support of 32 bit they will pull the trigger then and these hiccups you are seeing is a test and further will happen in the coming days and weeks to ensure viability and then an announcement will be made of the full switch over giving people enough time to upgrade for next expac.

That's my feel.

 

This doesnt fix it for me. You have it in D. I have it on C in x86 and when i put -noautolaunch64bit on all possible places, it still doesnt work. It says it's a wrong path so dunno what to do now.

Also tried x86

Could you please give me some guidance? Appreciated!

@Tony maybe you can post that post you spoke about. I can't find it. Also not via browse through forum. Or help me here? <3 *zooooooooom*

 

Create a shortcut to your wow.exe on Desktop and edit it.
Just put -noautolaunch64bit like in the Screenshot of Ilja's post.
This will work 100%

 

I did what you said, but it's still not working, same problem like Doctorhorror

 

The HB launcher ( Honorbuddy.Launcher.exe ) in your installation directory still works as well. If you can not get either to work, or figured out for yourself, perhaps ask someone you trust to teamviewer in and assist you. Either way is not very complicated.