No need to remove the entire game lol, nor Bnet. Simply terminate agent & Bnet from task manager
then change the wine settings to lutris 7.2-2 and try again (or repeat 3 times).
Edit: tried with system 7.16 staging, lutris fshack 7.2 and 7.2-2 not working, cant open the bnet.
Do you have esync and fsync enabled?
IGNORE THIS - My battle.net version in my main prefix was older than 13747 which was causing this issue
So when replacing Agent.exe with the old version, B.net will not launch after you quit and relaunch it again. Removing the Battle.net folder from ProgramData (which does NOT contain Battle.net it self), causes Agent.exe to download (the latest non-working version), then starting b.net works again. Though the original bug still persists. The only current work-around is to start wowclassic.exe or wow.exe directly. Use a VM for updates and copy them over until/if this gets fixed.
This is the current approach that works - also disable esync and fsync, don’t use lutris-ge-proton runners - I still can’t get them working, lutris-7.2-2 or wine-staging-tkg 7.17 are safe
I guess we are all clueless about what is really going on.
My Bnet client just opened without any issues (lutris 7.2-2). I just booted up my laptop again and logged back in Lutris and Bnet. I suspect an unknown issue with the runner itself (probably server limitations or smth related to peer numbers, dunno). Here’s the log file
safenote. co/r/632c572ac290f7@03883146
Link not working
you need to remove the space between the dot and C
Did that and it says it is expired
Renaming the cache folder worked, TY for the link jhu!!!
Your log looks identical to mine when ever I enable VKD3D.
tbh, didn’t touch anything except the runner versions.
Glad to hear it worked - had that one working over 10 hours ago now, but wanted to test it in Bottles and Steam - Bottles also got it working, but something about proton breaks it on Steam and any of the Lutris-proton runners.
Can you share some info about the bottles?
I am not able to run the installer there?
Bottles is the same as Lutris - need to have a copy of the installer downloaded to run inside the created bottle after it fails.
EDIT: From the log file, it looks like you were using a laptop CPU not GPU for the graphics?
I cannot install it with bottles. Probably something with the runners or any additional settings.
I am not sure about the GPU. I use the lutris on my laptop for AFK on Diablo 2 R. When my char starts running the entire screen turns black, only map and GUI visible. Also, since I have the game windowed I see the GPU is getting hot when the game is maximized.
GPU is getting hotter:
And hotter:
Lutris option on the System Options tab for discrete graphics - but if you are doing the AFK game time, then no point playing with this setting.
Tried 7.2.2 and it works. BUT I had to reenable esync and fsync as my bnet launcher would crash (with a crashreport ready to send to blizzard).
Updated WoW WotLK Classic - but it takes a long time reclaiming space.
Did you change runner to lutris-7.2-2 from something else, start Battle.net and then get the Blizzard error? If so, it has nothing to do with esync/fsync - it is the update of the Wine prefix that causes this. Don’t know why, only happens with Battle.net.
I did change it. And you are right the crash report was there only one time. bnet crashed while Reclaiming Space (it froze - I had to kill the process in htop).
I couldnt restart bnet with esync/fsync enabled: it would show the logging in screen and then was loading the launcher but froze there. Disabled the two and now its working for me again. At least the launcher is working (still reclaiming space for Classic WoW).
Very weird stuff going on here
EDIT:
Even though it says “reclaiming space” Icould start WoW classic. Will try to install D2R now
EDIT2:
You could have guessed: it doesnt work 
keeps saying “something went wrong”
