I also had that error show up and yes running Win 7.
I updated my video card drivers, and ran the d11 legacy fix in the cmd line, and all for “graphic card not supported”. Ugh. I have a GT 610.
I know I’m running on a potato and should have looked at the new requirements better, but I saw Win 7 and skimmed over them. So now I’m outta luck unless I buy a new machine - I’m at the max for operating system and hardware.
I wouldn’t be surprised for those running the GTX 580, 650 and 780, you will end up with the “video card not supported” once the dll problem is fixed.
I just wish Blizz wouldn’t “artifically” prevent people from running the game on old potatos. I always run on super low settings even if the computer has way more capability. If my card burns up and it wasn’t supported by Blizz so be it - I won’t blame them. Just let me try at least.
But what if it doesn’t burn up. What if it runs, kinda, but maybe causes crashes, or switches to slide show mode, or blanks out at unfortunate times? I suspect you would blame Blizzard plenty, and if not you, certainly thousands of potato-PC Andys will.
The published minimum is published and enforced to prevent wasting Technical Support’s time.
I had that same error and installed the missing .dll files required, but i got the same error 132 with api-ms-win-downlevel-kernel32-l2-1-0.dll missing from my computer. I’m currently trying to update my video card driver to see if that gets me in but from other posts it might be a wait and see thing for us Windows 7 users.
We’re aware of a bug affecting WoW on Windows 7 systems which is causing the game to crash with Error #132 or causing an “api-ms-win-core-com-l1-1-0.dll is missing” error on launch. Our WoW team will be releasing a new client update soon which should resolve this.
In the meantime forcing the game to launch in DirectX 11 Legacy should work around the problem as others have shared. I’ll post the steps again in case anyone has not seen them in previous posts.
Start the Battle.net app
Select the WoW game icon at the top
Click on the Options icon (next to the Play button) and select Game Settings
Check the box “Additional command line arguments”
In the new text box, type the following command:
-d3d11legacy
Click Done at the bottom to save the changes, then hit Play to launch the game again.
It is also a good idea to update graphics drivers if you haven’t already, to make sure the game runs smoothly
Once the client update is released with the bug fix please feel free to go back in and remove the command line argument. We will post an update in this thread once the update goes out that includes the fix.
Lastly, please note that Error #132 is a generic error. This forum thread is specifically for Windows 7 users encountering this crash on launch. If you are not on Windows 7 but you’re experiencing Error #132 crashes please try the steps in our Error 132 troubleshooting article and create a new thread with your DXDIAG report. Thanks!
That work around did not work for me. I really do hope you guys do release a fix for this huge bug…but that was said before…I think… and nothing has helped yet.
But before I forget thanks for at least acknowledging there is still a big problem for windows 7 users!
Hey Jambrix, thank you very much for the information. Unfortunantely the work-around didnt work for me. I will be waiting for the new client update Thanks!
I am having the same exact issue on windows 11.
Deleted everything (interface, wtf) no fix
Updated drivers to the latest version, no fix
Uninstalled wow completely and reinstalled fresh, no fix.
Yo Bliz, this just started a few days prior to DF release, ie after one of your background patches. What is the fix?
Same! Ashran was fine, every other facet of the game is working fine except while in Wintergrasp the game froze up and gave me this error. Weird. I used the workaround to be able to play, but for some reason Wintergrasp gives this error at some point.
Just to be counted, still not working for me after trying the workaround; thanks though for the attempt and at least acknowledging the situation. Hope the next update is soon!
Thanks!