Error 134 in World of Warcraft: Forever means the game could not open or change one of its own files, so it stops with “ERROR #134 (0x85100086) Fatal condition!” before it finishes loading. Blizzard’s Error #134 support article puts it down to wrong file permissions, a security program blocking the game, or a damaged game file, and the first two fixes to try are running the Battle.net app as an administrator and then running Scan and Repair on WoW: Forever.
Below are the fixes in the order to try them, which of them come straight from Blizzard, what to do when the error names something other than an archive, and when a reinstall is the answer. Everything here is checked against Blizzard’s support pages and its WoW Forever launch posts as of November 5, the day after launch.
What Error 134 Means
The error window has two lines that matter: the code, ERROR #134 (0x85100086) Fatal condition!, and a description under it. The description tells you which kind of Error 134 you have.
| Description line | What it points to | Start with |
|---|---|---|
| “Failed to open required archive” | The game was blocked from reading or changing one of its files | Admin mode, then Scan and Repair |
| “Invalid schema … for Table StartupFiles” | The game’s own data files | Scan and Repair, then a reinstall |
| Anything else | A damaged or locked file | A restart, then Scan and Repair |
Blizzard’s article covers the first line, the classic form of the error, and says it happens when World of Warcraft is prevented from making changes to a game file. Around WoW Forever’s launch the same code also turned up with the “Invalid schema” line when the game was started, which is a problem with the installed data rather than with permissions.
Error 134 is always on your PC. It is not a server outage, so checking whether WoW Forever’s servers are down will not help with this one.
How to Fix Error 134, Step by Step
Try launching WoW: Forever after each step, and stop as soon as it loads.
- Restart your PC. A restart is the first thing in Blizzard’s World of Warcraft Technical Troubleshooting article, and it frees a game folder that another program is still holding open.
- Run the Battle.net app as an administrator. Fully exit Battle.net first: right-click its icon in the Windows system tray and choose Exit. Then right-click the Battle.net shortcut and choose Run as administrator. Blizzard lists admin mode first, because it gets around the file permission problems that cause the classic form of the error.
- Scan and Repair WoW: Forever. In the Battle.net app, select World of Warcraft, pick WoW: Forever in the Game Version menu, click the gear icon next to Play, choose Scan and Repair, then Begin Scan. This is the repair tool Blizzard’s article points to: it checks the install and replaces damaged files. Check that the Game Version menu says Forever before you start, because modern WoW and Classic are separate installs with separate repairs.
- Let your security software through. Blizzard names security programs as one cause. Add Battle.net and your World of Warcraft folder to your antivirus and firewall exceptions, or switch the security software off for a single test launch and turn it straight back on.
- Update Windows and your graphics drivers. Blizzard lists both in its fixes. While you are there, check your graphics card against Blizzard’s minimum for WoW Forever, which our GPU requirements story covers, because an unsupported card is a different problem that no repair fixes.
- Reinstall WoW: Forever. Blizzard’s last step for an error that keeps coming back. Uninstall it from the same gear menu, then install it again from the Game Version menu. If you want to keep your addons and settings, copy the
InterfaceandWTFfolders out ofWorld of Warcraft\_forever_first and put them back afterwards.
If your error says “Invalid schema”, skip ahead: steps 3 and 6 are the ones that deal with the game’s data files, so run Scan and Repair and, if the error survives it, reinstall.
Things Specific to WoW Forever
- Start it from Battle.net, not the game file. Blizzard’s install steps are to open the Battle.net app, choose WoW: Forever in the Game Version menu and click Play. Starting the game’s .exe straight from its folder skips the app, which is where updates and repairs happen.
- Forever has its own folder. WoW Forever lives in
World of Warcraft\_forever_, apart from modern WoW’s_retail_folder and the Classic folders, as our addon install guide explains. Repairing or clearing another version’s folder does nothing for Forever. - Your characters are safe. Characters live on Blizzard’s servers. A repair or a reinstall only touches the files on your PC, so the worst you lose is local settings you did not back up.
If the Game Crashes After It Loads Instead
Error 134 at start-up is a file problem. If WoW Forever opens and then crashes or throws errors once you are in the world, look at your interface first. Blizzard’s WoW Forever Info and Known Issues post reminds players to make sure their addons are updated at launch, while addon authors are still catching up.
- At character select, click the AddOns button and turn every addon off, then log in. If the problem stops, turn them back on a few at a time to find the culprit.
- If that is not enough, follow Blizzard’s Resetting your User Interface steps: close the game and rename the
Cache,InterfaceandWTFfolders inside_forever_(for example, toCacheOld). The game rebuilds clean copies the next time it starts.
When you set your interface up again, our list of the best WoW Forever addons that work is a good place to restart from.
When to Contact Blizzard
If Error 134 survives a full reinstall, write down the whole error text, both lines, and open a ticket through Blizzard Support. If the error started for everyone at the same moment, for example right after a patch, check @BlizzardCS on X and Blizzard’s WoW Forever forums before you spend time on your own PC.
Every other WoW Forever guide we have, from rulesets to professions, is on our World of Warcraft hub.
Frequently Asked Questions
What is Error 134 in WoW Forever? It is the “Fatal condition” error, code 0x85100086. The game could not open or change one of its files, usually because of permissions, security software or a damaged file.
What is the quickest fix for Error 134? Exit Battle.net, run it as an administrator, then use Scan and Repair on WoW: Forever from the gear icon next to Play.
Does Error 134 mean the WoW Forever servers are down? No. It is a problem with the game files on your PC, not with Blizzard’s servers.
Will reinstalling WoW Forever delete my characters? No. Characters are stored on Blizzard’s servers. A reinstall only removes local files such as addons and interface settings, which you can back up from the _forever_ folder first.
Why do I get Error 134 in WoW Forever but not in modern WoW? Each version has its own install and its own files. A damaged or blocked file in WoW Forever’s folder does not affect modern WoW, so repair WoW: Forever specifically.