This sort of error means that something other than the application you’re trying to open is currently managing your resources. If you’re trying to open a game, the first places to start looking are applications like GameGuard or external antivirus suites. But before you do anything else, do a simple restart and see if the “debugger has been found running in your system” error is resolved. Some users reported that the issue went away after they did a restart. If you’re currently struggling with the “debugger has been found running in your system” error and a restart didn’t help, start following the methods below. This article contains a selection of potential fixes that other users have used successfully to fix or get around this issue. Please follow each method in order until you encounter a fix that manages to resolve the problem in your situation.
Method 1: Making sure Windows 10 is up-to-date (if applicable)
From our investigations, the “debugger has been found running in your system” error mainly occurs on Windows 10 systems that are not up to date. Quite a few users have reported that the issue is fixed on their Windows 10 computers after installing the pending Windows update. Note: If you don’t have Windows 10 or if your OS is up-to-date, skip straight to Method 3. Here’s a quick guide on installing the missing updates on your Windows 10 OS: If you’re still encountering the same error when opening certain applications or games, move over to Method 2.
Method 2: Adding the game/application folder to Antivirus exception list (if applicable)
Most of the time, users affected by the “debugger has been found running in your system” error have managed to identify their external antivirus solution as the culprit. Note: If you’re not using a 3rd party security suite, skip straight to Method 3. Affected users have managed to resolve the issue either by adding the game or application folder to the exception list or by uninstalling the 3rd party antivirus completely. It turns out that Windows Defender will not produce this sort of problem. The vast majority of user reports point towards AVG or Mc Afee as the main external security suites that will create false positives resulting in the “debugger has been found running in your system” error. One way to deal with this conflict is to navigate to your antivirus settings and add the whole application folder (containing the executable that is showing the “debugger has been found running in your system” error) to the Exclusion list. Going this route will enable you to continue using your 3rd party antivirus. But keep in mind that the exact steps are highly dependable on which external security suite you use. Note: If you’re using AVG you can reach the exception list by navigating to Options > Advanced Settings > Exceptions. Once you arrive there, click on Add Exception, select Folder as the Exception Type and choose the folder containing the executable that is displaying the “debugger has been found running in your system” error. If your AV doesn’t have an exclusion list or you can’t find it, you can also uninstall the security suite completely from your system. To do this, open a Run box (Windows key + R) and press Enter to open The Programs and Features window. Then, scroll through the application list and uninstall your 3rd antivirus. If this method wasn’t applicable or didn’t help you to fix the “debugger has been found running in your system” error, move down to Method 3.
Method 3: Reinstalling GameGuard
If your external antivirus was not to blame for the “debugger has been found running in your system” error, let’s see if GameGuard is causing the issue. Some users have reported that the error went away after they reinstalled or completely removed GameGuard from their systems. Note: Keep in mind that most games that are released nowadays are using their own systems to protect against cheats and other types of exploits. Because of this, GameGuard is largely unnecessary (unless you’re playing a very old MMO). Even more, GG is known to conflict with certain games producing the “debugger has been found running in your system” error. Here’s a quick guide on reinstalling or removing GameGuard: If this method wasn’t applicable or didn’t enable you to get around the “debugger has been found running in your system” error, move down to Method 3.
Method 4: Opening the application in Safe Mode
While this might not treat the cause of the issue, it will most likely allow you to open the application/game in question. Some users have managed to get around this issue by opening the executable in Safe Mode. This likely happens because the application is opening without interference caused by other 3rd-party processes that might be running in the background. To boot in safe mode, click the Start icon (bottom-left corner) and hold the Shift key while clicking the Restart button. Once your computer boots up into safe mode, open the application and see whether it opens without the “debugger has been found running in your system” error. If it opens without problems, open Programs and Features (Windows key + R, then type “appwiz.cpl” and hit Enter) and systematically uninstall any 3rd party application that might be causing the interference. If you’re still getting the “debugger has been found running in your system” error at a start of an application, move down to the method below.
Method 5: Using a system restore point
If all of the methods above have failed you, one sure way to go around resolving the “debugger has been found running in your system” error is to use a system restore point to restore your machine to a state where you were able to open the application without issues. However, this method might not be applicable if you don’t have a system restore point older than when you first started experiencing these symptoms. Here’s a quick guide on using a previous System Restore point to restore your machine to a state where the “debugger has been found running in your system” error was not manifesting:
Fix: A debugger has been found running in your systemFIX: Account has been disabled. Please see your System AdministratorHow to Fix No Boot Disk Has Been Detected or the Disk Has FailedFix: The CPU has been disabled by the guest operating system
