-
Need help with error 132
Hey there everyone,
Just started playing WoW again after a 3 year hiatus. I played for about 30 minutes until the game crashed. Fortunately there was an error message so I believe somebody who is more knowledgeable might be able to help me. In the link below there is a screenshot of the message I am getting.
https://i.imgur.com/WKNt8ZC.png
Googling yielded some suggestions which I did try, such as using the command sfc/ scannow in cmd. I would be glad if anyone comes up with a solution.
Thanks in advance!
-
Its a bug that appears very often on warmane. don't worry about that
-
Is there any way to fix it? Seems kind of disruptive.
-
this is more then distruptive, it litterly makes the game none playable on those chars in shrine of two moons
-
I've deleted wtf,cache and interface. Currently using the battlenet repair utility. Will update with results.
UPDATE: Apparently I broke my installation. The repair utility updated the client to WoD.
-
I have same problem but I can not even log into game. When I type password it shows "connecting" then this error. Tried more than 10 times, still same problem
-
Also I do not play for years I wanted to continue but does not make me get that gives me error
-
I have error 132 crashes on Frostwolf a good bit when I'm trying to log on in a populated city like Orgrimmar or Shrine. It doesn't happen nearly as much when I log on and off in smaller cities like Thunder Bluff, so that's what I do.
I wish they'd fix it, but it's more an annoyance than anything- I usually manage to log on the second try.