WoW not launching properly in 7.3.2 + IS 6244
My config hasn't changed in over a year. I'm still running Win7 Ultimate and Bitdefender AV. 64-bit IS with WoW-64.exe. "Use 664-bit Uplink" and "Use same-bit clients" are both enabled. Originally, it was taking 3-5 minutes per client to launch whereas the battle.net launcher would load them up in 20 seconds or so.
So, I rebooted. Now, any time I attempt to use anything except the explicit WoW 32-bit game profiles and uplink, I get bizarre behavior.
- 64-bit Uplink + Wow launcher setting = 32-bit + game profile = WoW DX9 32-bit = LOADS OK
- 64-bit Uplink + WoW launcher = 64-bit + game profile = WoW default or any 64-bit flavor = "YOU SUCK! Failed to load. Critical error during loading process. Required library WINMM.DLL does not exist." But it does. It's like, right there. In c:\windows\system32. Patching/re-patching/scan for corrupt files in the wow launcher and even cmd.exe->sfc /scannow had no effect. Multiple reboots to no effect.
- 64-bit Uplink + WoW launcher = 32-bit + game profile = WoW default = two wow.exe processes that repeatedly load and exit, with IS console showing "Session Name 'World of Warcraft######' accepted for process c:\games\wow\wow.exe"
- 32-bit Uplink + WoW launcher = 32-bit + game profile = WoW DX9 32-bit = LOADS OK
- 32-bit Uplink + WoW launcher = 32-bit + game profile = WoW default = wow.exe process loads repeatedly and exits forever as above.
- Launching WoW-64.exe manually or via the battle.net launcher works fine.
I think the only thing I haven't tried yet is nuking my isboxer profile from orbit and trying a clean setup, but I really really don't want to lose all the work that went into getting my teams working well.
I'm about tapped out for the night, but since the 32-bit client seems to launch, I'm probably not completely broken. I'd just like to understand what could be causing this as I've never had any issues running full 64-bit before outside of known "blizzard broke the launcher so IS needs to update" stuff.
Cheers,
Ugh