Some World of Warcraft players are encountering the ‘WOW Error #134 (0x85100086) Fatal Condition‘ when trying to launch the game. Error #134 is typically encountered when the main game executable is prevented from making changes to the game file.
Đang xem: Wow error #134 fatal condition
WOW Error #134 (0x85100086) Fatal Condition
There are several different causes that might end up triggering this startup error message with World of Warcraft:
Missing Admin access – As it turns out, one of the most common causes that might trigger this error code is when the game's launcher (Battle.net) doesn't have admin permissions. If this scenario is applicable, you should be able to fix the issue easily by forcing the launcher to run with admin access.Corrupted data inside the Cache folder – WOW has a long and painful history of badly temporary files that end up creating a myriad of errors including this one. If the Cache folder is responsible for this error code, you can fix the issue swiftly by learning the Cache folder from the game installation folder.Missing Editing permissions – Another possibility that might spawn this error is when certain files and folders (wow.exe, data, and update folders) have the Read-only attribute enabled so your OS cannot modify them when a new update is available. If this scenario is applicable, you can fix the issue by opening the properties screens of each file/folder and removing the read-only attribute.Interfering security program – As it's been confirmed by some affected users, this problem can also be facilitated by an overprotective security suite (especially if you're using mods and hosting a private server). In this case, you should try whitelisting the Battle.net app along with the WOW executable or disable/uninstall the problematic AV suite.Corrupted game data – This error code can also be an underlying signal that you are dealing with some type of damaged game files. This typically occurs after a failed update or after a malware scan. In this case, you should run the blizzard repair tool in order to return your game files to a healthy state.Missing OS infrastructure – If you have a lot of missing Windows updates, you can expect to see this error due to missing platform updates that prevent the games from running. In this case, you should install every pending Windows update until you bring your OS build up to date.Outdated GPU drivers – A partially corrupted or severely outdated GPU driver can also be the root cause that might cause Error #134. In this case, you should be able to fix the issue by using Device Manager or the your graphics card proprietary software to update your GPU drivers and physics module.
Method 1: Running Blizzard Battle.net app with Admin access
As it turns out, one of the most common causes that will end up causing the ‘WOW Error #134 (0x85100086) Fatal Condition‘ is a permission issue that's being facilitated by insufficient admin privileges. As it's been reported by other users in a similar situation, this problem typically occurs with the World of Warcraft launcher (Blizzard Battle.net desktop app).
If this scenario is applicable, you should be able to fix the issue by forcing the game launcher to run in administrator mode. This operation will end up fixing various scenarios in which this error code ends up affecting installation, patching, networking, and start-ups.
Follow the instructions below in order to force Blizzard's Battle.Net app to run with administrative privileges in order to resolve the ‘WOW Error #134 (0x85100086) Fatal Condition‘:
Right-click on the Blizzard Battle.net app executable and choose Run as Administrator from the newly appeared context menu.
Running setup.exe as administratorWhen you are prompted by the UAC (User Account Control) prompt, click Yes to grant administrative access. Next, wait for the game launcher to start, then use it to launch World of Warcraft and see if you're still encountering the same problem.In case the same problem doesn't occur now that you have granted admin access, you just pinpointed the problem. However, unless you do some additional modifications, you will need to repeat this step every time you want to launch the game.However, if you want to make things easier for yourself, you can force the executable to always launch with admin access. To do this, right-click on the launcher once again and choose Properties from the context menu.
Right-clicking and selecting “Properties”.Once you're inside the properties screen, select the Compatibility tab from the list of available options, then move over the Settings section and ensure that the checkbox associated with Run this program as administrator is checked.
Run this program as an administrator Click Apply to save the changes. Then repeat the launching process and see if the problem has been fixed.
Read more: escape from the vault wow
In case the same problem is still persisting and you're still seeing the ‘WOW Error #134 (0x85100086) Fatal Condition‘ when you try to launch World of Warcraft, move down to the next potential fix below.
Method 2: Deleting the Game's Cache folder
The game's cache folder is often responsible for the apparition of this particular issue. Some users that were also encountering the WOW Error #134 at every startup attempt have confirmed that they were able to fix the problem by navigation go the game's location and deleting the cache folder.
This operation will end up eliminating any temp file that might serve as the root cause of the apparition of this issue. The next startup will force the game to launch without any remnant data from previous launches.
If you want to give this fix a try, follow the instructions below to clear the Cache folder of World of Warcraft:
Open File Explorer (My Computer on older OS versions) and navigate to the location of your World of Warcraft installation. Unless you installed the game on a custom location, the default location of WOW is:C:Program Files (x86)World of WarcraftOnce you arrive at the correct location, right-click on the Cache folder and choose Delete from the newly appeared context menu.
Deleting the WOW cache folderAfter you've done this, launch the game once again to see if this fix has been succesfull.
In case you still end up seeing the Error #134 (0x85100086) after the initial startup fails, move down to the next troubleshooting step.
Method 3: Eliminating the Read-Only Attribute
Depending on your UAC (User Account Control) settings and whether you applied custom attributes to files belonging to World of Warcraft, you can expect to see this error code due to the fact that the main WOW executable (WOW.exe) and other sub-components are using the Read-only attribute which prevents the game's launcher from modifying and updating the files.
If this is the case in your particular situation and a new update is available, you can expect to see the Error #134 (0x85100086) after a failed attempt to modify these files.
In the event that this scenario is applicable to your particular scenario, follow the instructions below to fix the error by getting rid of the Read-Only attribute:
Open File Explorer and navigate to the location where you installed World of Warcraft. Unless you installed it in a custom location, the default path is:C:Program Files (x86)World of WarcraftOnce you get to the correct location, right-click on Wow.exe and choose Properties from the newly appeared context menu.From the Properties screen, select the General tab at the top, then uncheck the box associated with Read-Only and click Apply to save the changes.
removing the Read-Only Attribute
Note: If the box is already checked, move down to the next potential fix below.Next, repeat step 2 and step 3 with the Data and Update folders to ensure that the Read-Only attribute is not enabled there.Launch the game normally and see if these modifications have successfully allowed you to fix the Error #134 when launching World of Warcraft.
If the same problem is still persisting, move down to the next potential fix below.
Method 4: Whitelist WOW's launcher or disable security suite
As it turns out, the Error #134 (0x85100086) Fatal Condition in World of Warcraft can also occur if your 3rd party suite ends up blocking the connection between the game's launcher and the game's server. In the event that this is caused by a false positive (you AV is overreacting), you can fix this elegantly by whitelisting Blizzard Battle.net Desktop app + the main WOW executable from your AV settings.
Note: If whitelisting doesn't work, you will need to uninstall the 3rd party security suite altogether in order to be certain that you're not dealing with an AV-induced security interference.
A. Whitelisting Battle.net Desktop app + the main WOW executable via Windows Firewall
In case you're using Windows Defender, follow the instructions below to whitelist Battle.net Desktop app + the main WOW executable from Windows Firewall:
Note: The instructions below will work for every recent Windows version (Windows 7, Windows 8.1 and Windows 10)
Note 2: If you are using a 3rd party Antivirus + firewall, you need to search online for specific steps of whitelisting the two executables or follow the second guide below for steps of uninstalling it.