An error is currently causing frustration in World of Warcraft. The “Error 132” prevents many from playing. Here’s how to fix the error!
Nothing works in World of Warcraft
… and suddenly nothing works! Almost spontaneously, WoW crashed for thousands of players at the same time, and since then, logging in has been impossible. The culprit is Error 132, which occurs immediately after logging in and sends the game data into oblivion.
Error 132 is particularly frustrating. Many players instinctively try to run the repair process of World of Warcraft, which can be opened in the Battle.net launcher. But even though the Battle.net program calculates happily for up to half an hour, it rarely leads to a solution: The game crashes again on the next login.
How to fix Error 132?
- To fix the error, you need to open the installation path of World of Warcraft.
- There you will find a number of folders. Open the “Cache” folder.
- In the subfolder, you will now find the folders “ADB”, “WDB”, and “wowbrowser”.
- Delete all three directories! Don’t worry, WoW will recreate these directories the next time you start it up, and then the data (at least for now) will be correct.
How exactly this error occurred is still unknown. Some players also report that the error reappears as soon as they leave the game and then try to enter again. For now, it seems that deleting the interface folder is also necessary. This is particularly frustrating for all players who rely on interface extensions, as the deleted (or renamed) folders contain important data for the addons. For the time being, everyone will have to play with the standard interface until Blizzard resolves the issue on their end.
For more news and articles about Blizzard’s MMORPG, check out our World of Warcraft game page.
