Note: nProtect INCA Internet developed the anti-cheating rootkit GameGuard, also known as GG. It is commonly deployed in numerous online games in order to block potentially dangerous exploits and prevent common cheating techniques. GameGuard uses rootkits to prevent the execution of cheat software. GameGuard conceals the game application process, monitors the entire memory range, terminates applications, blocks specific calls to Direct X functions and Windows APIs, logs keyboard input for improper behavior, and self-updates as new potential threats emerge. But because GameGuard functions effectively as a rootkit, players may encounter unforeseen and perhaps undesirable side effects. The most common scenario is a common glitch that occurs when GameGuard has not been shut down properly. Other potential scenarios that will spawn this error include: spyware interference, missing a security update, collision with another program, or corrupted GameGuard installation. Here’s a list of confirmed methods that other affected users have successfully used to get past the Initialization fail (Error code 114)
1. Reboot the system
Because it’s functioning like a rootkit closely tied to the game, GameGuard will often throw the Initialization Fail (114) error whenever the game it’s attached to is closed unexpectedly. If you’re just starting to troubleshoot the issue, the first thing you need to do is reboot your system and fix the common instance where GameGuard has not been shut down properly. With a lot of game titles protected by nProtect GameGuard (especially legacy titles), you can expect to see this error with every installed game that uses this rootkit until you reboot your system and allow the anti-cheat engine to reinitialize. If you haven’t tried this already, and you experience this issue with every game that uses GameGuard, simply reboot your system and see if the Initialization Fail (114) error is fixed at the next startup.
2. Run the game launcher with admin access
If you experience this issue with one or two games that are protected by Game Guard, you might be dealing with a permission issue. Because this anti-cheat engine is acting as a rootkit, it needs admin access to access all the required dependencies. A lot of users have experienced this issue with legacy game titles because a deprecated DirectX dependency was not accessible. If you get the ‘Initialization error 114′ every time you launch a particular game, try forcing it to launch with admin access and see if the issue is bypassed. To test if you’re dealing with a permission issue, right-click on the game (or the game’s launcher) that’s throwing the error and click on Run as administrator from the context menu. Note: When prompted by the User Account Control (UAC), click Yes to grant admin access. If the game launches without issues once you’ve successfully forced admin access, you’ve successfully resolved the permission issue. However, you will need to repeat this action every time you launch the game, unless you follow the steps below to reconfigure the game’s executable to always launch with admin access:
3. Install the latest Security update
Looking back, GameGuard has a rocky history if we’re referring to the sheer amount of security updates that ended up causing the anti-cheat engine to malfunction. It’s not uncommon to see the ‘Initialization error 114′ because of a collision with a Windows Security update that prevents the anti-cheat game engine from accessing certain dependencies. This has happened numerous times in the past and every time the issue gets rectified by a Windows Security update that fixes the collision. If this scenario is applicable, all you need to do to fix this issue is to access the Windows Update menu and ensure that you have every security update installed. Follow the instructions below for specific instructions on how to update your Windows version to the latest build: Note: The instructions below will work with every recent Windows version.
4. Disable or Uninstall 3rd party antivirus (if applicable)
There are certain AV suites & firewalls that are not very friendly with the rootkit-like architecture that GameGuard has. AVG and Comodo antivirus are two prime examples of 3rd party AV suites that are not very accommodating to GameGuard. If you use a 3rd party AV suite (with or without a firewall component) and you see this error with every game that uses the GameGuard anti-cheat engine, this is probably the reason why you see the ‘Initiatialization error 114′ message after every failed attempt. Note: If you are not utilizing a third-party security suite, you can skip this step and proceed to the one following. It is not confirmed that Windows Defender caused this issue. If you are using AVG, Comodo, or any other 3rd party suite, disable it temporarily and see if you can launch your games normally. In most cases, you can disable the problematic AV simply by right-clicking the taskbar icon and clicking on Disable real-time protection from the context menu. Note: Make sure you disable it for a set number of minutes (or permanently) to ensure that you can restart without the shields clicking back into action. The exact menus will be different from AV to AV. In some cases, you won’t be able to disable the AV directly from the taskbar menu and you’ll need to access the dedicated settings. After you disabled the active 3rd party AV, reboot your PC and see if you can launch the game that was previously triggering the 114 error once the next startup is complete. Important: If the 3rd party AV component includes a firewall, you will likely not be able to solve the issue just by disabling the AV part. In this case, you will need to either whitelist the entire GameGuard installation inside your firewall settings (instructions below) or you’ll need to uninstall the 3rd party app altogether. If you prefer the latter, ensure that you perform a complete uninstall of the security program so you don’t leave behind any remnant files that can produce the same behavior.
5. Add Gameguard Execution files to Firewall’s Exception list
It’s good practice to whitelist the entire GameGuard installation from your firewall to avoid false positives where the anti-cheat engine gets treated like a malicious rootkit. Important: If you installed multiple games that are using GameGuard, you will find multiple instances of this anti-cheat engine. In this case, you must whitelist every instance of this executable to prevent this issue from occurring. If you’re using a 3rd party firewall, the instructions for doing this will be different from software to software. However, you should be able to find a Whitelisting / Exclusion tab inside your firewall settings and add the main executable of Gameguard. In case, you’re using the default firewall from Windows Security (Windows Firewall), follow the instructions below to add GameGuard to the exception list:
6. Prevent interrupting programs from causing the error (applicable)
Besides Antivirus and firewalls, GameGuard is also known to conflict with a wide array of other applications. Game tracking services, some legacy games (running concurrently), video playback programs, macro assigning software, controller mapping software, and other anti-hack software or emulator software can all collide with GameGuard if they are running at the time when the main GameGuard service is started. To make it easier for you, We’ve made a list of programs that might cause the 114 error with GameGuard: Game Tracking devices: Legacy Games: Video Players: Macro Assigning Software Controller Mapping Software Anti-Hack Software Emulator software If you have any of the tools mentioned above installed on your PC, make sure you prevent them from colliding with GameGuard by following the instructions below: Note: Keep in mind that there might be other 3rd party programs or games that will still collide with the anti-cheat engine and are not mentioned above. To ensure that no 3rd party service is causing this problem, achieve a clean boot state and launch the game once again.
7. Delete the GameGuard folder
If the problem lies within the local files used by GameGuard, you can simply delete the main GameGuard folder inside the game installation folder. This is confirmed to be effective by a lot of gamers that we’re experiencing the 114 error with MMOs like Elsword that we’re launched through a launcher like Steam or GoG. Note: Because GameGuard is an integral part of the game, every launcher will check for the anti-cheat dependencies and regenerate them if needed. So if the game that throws the ‘Initiatialization error 114’ is launched through Steam, GoG, Epic Games, EA Play or HumbleBundle, follow the instructions below to delete the Game Guard folder: Important: If you don’t launch the legacy game through a launcher, deleting the Game Guard folder will likely force you to reinstall the game. (follow the next methods for instructions)
8. Perform an AV scan & reinstall the affected game/s
If you’re experiencing this issue with a legacy game, it’s possible that some game files have been quarantined by the security suite and are now missing from the installation folder. Although this might happen due to a false positive, you should always assume that you’re dealing with a threat first. Other users dealing with this problem have managed to fix the issue by performing an AV scan before reinstalling the affected game from the Programs and Features menu. Note: Our recommendation is to deploy a deep scan with Malwarebytes even if you already have a premium subscription to an AV suite. This will help you eliminate any adware that might be producing this issue. Here’s what you need to do:
