World of Warcraft Error #134 (0x85100086) “Fatal Condition” means the game was blocked from changing one of its own files. Blizzard lists three causes: wrong file permissions, a security program getting in the way, or a damaged game file. The quickest fix in November 2026 is to close the game, rename the Cache folder, and start the Battle.net app with Run as administrator. If that doesn’t work, add Battle.net to your antivirus exceptions, update Windows and your drivers, then run Scan and Repair. Reinstalling is the last step.
World of Warcraft is one of the best-known MMORPGs ever made. Blizzard Entertainment launched it in North America on November 23, 2004, and the Windows and Mac OS X versions came out at the same time. It is still a PC and Mac game today. The Midnight expansion came out on March 2, 2026, and Blizzard keeps releasing 12.x content patches. Each patch rewrites game files, which is exactly the moment Error #134 tends to show up.
What WoW Error #134 means
Error #134 appears when World of Warcraft tries to open or write a game file and Windows says no. You usually see “Error #134 (0x85100086) Fatal Condition” as soon as you press Play. Some versions add “Failed to open required archive… with error: 5”. On Windows, error 5 means “access denied.”
The exact trigger varies from PC to PC, but it falls into a few groups:
- Missing administrator rights. The Battle.net app or Wow.exe can’t write to its own folder.
- Corrupted game data or cache. A damaged file in the Cache folder or the game archives stops the game from loading.
- Missing permissions or a read-only flag. Wow.exe or the game folder is marked read-only, so updates can’t be written.
- Outdated graphics or audio drivers, or an outdated Windows build.
- Conflicts with other programs. Antivirus suites, firewalls and DNS filtering solutions can treat the launcher or the login module as a threat and block it.
Admin rights and corrupted files are the same things that cause many other launcher failures. That’s why the fixes below look a lot like the advice for problems such as Borderlands 3 not launching on Steam.
How to solve World of Warcraft Error #134
Try the fixes below in order. They start with the quickest and safest and end with a full reinstall. After each one, open World of Warcraft from the Battle.net app and check whether the error is gone before you move on.
Fix 1: Clear the WoW Cache folder and run Battle.net as administrator
This fix deals with the two most common causes together: a bad cache and missing admin rights. It takes about five minutes and doesn’t touch your characters, which are stored on Blizzard’s servers.
- Close World of Warcraft completely.
- Open the Battle.net app and select World of Warcraft.
- Click the gear icon next to the Play button and choose Show in Explorer. File Explorer opens the World of Warcraft folder.
- Open the folder for the version you play: retail for the current game, or classic or classic_era for Classic.
- Find the Cache folder. Blizzard suggests renaming it to CacheOld instead of deleting it, so you can put it back if you need to. Right-click it and choose Rename (or select it and press F2). You can also delete it, because the game rebuilds it.
- Close the Battle.net app fully. Right-click its icon in the system tray (bottom-right of the taskbar) and choose Exit.
- Right-click the Battle.net shortcut and choose Run as administrator. When User Account Control asks, click Yes.
- Launch World of Warcraft from Battle.net and check whether the error is gone.
To make Battle.net always run as administrator:
- Right-click the Battle.net shortcut and choose Properties. On Windows 11, you may need to click Show more options first.
- Open the Compatibility tab.
- Tick Run this program as an administrator.
- Click Apply, then OK.
Only rename the Cache folder for now. The WTF and Interface folders hold your keybindings, settings and add-ons. Renaming them resets your interface, so leave them alone unless Blizzard support tells you otherwise. Clearing a cache is a common first fix in many games, from WoW’s Cache folder to the shader rebuild you get when you see Modern Warfare installing shaders stuck.
Fix 2: Update your drivers, remove the read-only attribute and reinstall WoW
If Fix 1 didn’t help, check your drivers, your file permissions and Windows itself. Reinstall only if none of those work.
Update your graphics and audio drivers
- Type Device Manager in the Windows search bar and open it.
- Click the arrow next to Display adapters to expand it. Right-click your graphics card and choose Update driver.
- Choose Search automatically for drivers. Windows installs a newer driver if it finds one.
- Do the same under Sound, video and game controllers for your audio device.
Device Manager often says “the best drivers are already installed” even when a newer version exists. For your graphics card, the vendor’s own tool is more reliable: the NVIDIA app for GeForce cards, AMD Software: Adrenalin Edition for Radeon cards, or Intel Driver & Support Assistant for Intel graphics. Download these only from NVIDIA, AMD or Intel directly, never from third-party driver sites.
After the update, restart your PC and try the game again.
Remove the read-only attribute from Wow.exe
- Use Show in Explorer from the Battle.net gear menu again, then open the retail folder.
- Right-click Wow.exe and choose Properties.
- On the General tab, untick Read-only if it is ticked.
- Click Apply, then OK, and launch the game.
If you see “Read-only (Only applies to files in folder)” on the World of Warcraft folder itself, that box is a normal Windows display and usually doesn’t mean anything is wrong. The flag on Wow.exe is the one that matters.
Update Windows
Blizzard lists outdated operating systems as one cause of this error. On Windows 11, go to Settings > Windows Update and click Check for updates. Install everything offered, restart, and run WoW again.
On Windows 10, the path is Settings > Update & Security > Windows Update. Microsoft ended standard support for Windows 10 on October 14, 2025. Unless your PC is enrolled in Extended Security Updates, it no longer gets regular fixes.
Reinstall World of Warcraft
WoW doesn’t have a Repair option in Control Panel. Blizzard handles uninstalling and reinstalling through the Battle.net app:
- In Battle.net, select World of Warcraft.
- Click the gear icon next to Play and choose Uninstall. If you want to keep your interface layout, copy your WTF and Interface folders somewhere safe first.
- When it finishes, restart your PC.
- Open Battle.net as administrator and install World of Warcraft again. If you have space, choose a folder outside Program Files, such as C:\Games. This avoids many permission problems.
Fix 3: Allow the Battle.net app through your firewall and run Scan and Repair
Security software is one of the three causes Blizzard names for Error #134. Windows Defender Firewall or a third-party antivirus can block the launcher or the game. Add Battle.net as an exception, then repair the game files.
Allow Battle.net through Windows Defender Firewall
- Type Control Panel in the Windows search bar and open it.
- Go to System and Security > Windows Defender Firewall.
- Click Allow an app or feature through Windows Defender Firewall.
- Click Change settings, then Allow another app… at the bottom.
- Click Browse, go to the Battle.net install folder (usually C:\Program Files (x86)\Battle.net), select Battle.net.exe, and click Add.
- Make sure Battle.net is ticked, along with both the Private and Public boxes. Click OK.
If you use a third-party antivirus, such as Norton, McAfee, Bitdefender or Avast, add the Battle.net folder and the World of Warcraft folder to its exclusion or exception list too. Blizzard notes that some security programs mistake the game’s login module for a threat. Don’t turn your antivirus off permanently. An exception gives the same result without leaving your PC exposed.
Run Scan and Repair
Whitelisting won’t help if your game data is already damaged. Battle.net’s built-in repair tool checks every game file and replaces any bad ones:
- Open the Battle.net app as administrator.
- Select World of Warcraft.
- Click the gear icon next to the Play button.
- Choose Scan and Repair, then click Begin Scan.
- Let it finish, then launch the game.
On a slow drive or connection, the scan can take a while. If Scan and Repair is greyed out, close Battle.net completely and reopen it with Run as administrator.
If nothing works
If the error survives a fresh install, the problem is probably your Windows account or file permissions, not the game. Try signing in to Windows with a different administrator account and launching WoW from there. If it works on that account, the permissions on your main account are the problem.
At that point, contact Blizzard Support through the Battle.net app or Blizzard’s support website. Include the full error text and the file name it mentions. Blizzard’s technicians can also ask for a system report that shows conflicts you can’t easily see yourself.
FAQ
Is WoW Error #134 a server problem?
No. Error #134 happens on your own PC, when World of Warcraft can’t change one of its local files. Waiting for the servers won’t fix it. Check permissions, security software and file damage instead.
Will deleting the Cache folder delete my characters or settings?
No. Characters live on Blizzard’s servers, and the Cache folder only holds temporary data that the game rebuilds. Your keybindings and add-on settings are stored in the WTF and Interface folders, so leave those alone unless you want a full interface reset.
What does “error: 5” mean in the Error #134 message?
Error 5 is the Windows code for “access denied.” Something blocked WoW from opening a file it needed, usually missing admin rights, a read-only flag or a security program. Running Battle.net as administrator and adding an antivirus exception are the most direct fixes.
Can Error #134 happen in WoW Classic too?
Yes. Classic and retail use the same Battle.net launcher and the same kind of file setup, so the causes and fixes are the same. Just open the classic or classic_era folder instead of retail when you clear the cache.
Does Error #134 happen on Mac?
The error is mostly reported on Windows, but file permission problems can happen on macOS too. On a Mac, use the gear icon in Battle.net to run Scan and Repair first. Then check your security software and make sure the World of Warcraft folder isn’t locked.
Do I need to reinstall Windows to fix Error #134?
Almost never. A cache reset, admin rights, an antivirus exception and Scan and Repair fix most cases. Reinstalling the game is the next step after that. Contact Blizzard Support before you think about anything as drastic as reinstalling Windows.
Sources
- Blizzard Support: Error #134
- Blizzard Support: An updated version of World of Warcraft is available
- Blizzard Support: Battle.net app game options (Scan and Repair)
- Blizzard Support: World of Warcraft troubleshooting (Cache, Interface and WTF folders)












