Fix: Please Close Interception Before Starting the Game
The error “Please Close Interception Before Starting the Game“ is a launch-blocking message that can appear in games like Fortnite, Rust, and Apex Legends when the game’s anti-cheat detects the Interception driver (or another low-level input hook that behaves similarly) running on your PC.

Anti-cheat systems block Interception because it uses a kernel-mode input driver that can intercept or modify low-level input before it reaches applications. Even if you used it for legitimate remapping or accessibility, anti-cheat often cannot reliably distinguish that from tools that alter raw input for unfair advantages, so it blocks the input layer entirely.
Do this first (fast path):
- Close all remappers/macro tools (system tray icons) and disable them from Startup (Task Manager > Startup).
- Do Quick Checks to confirm whether Interception (or a similarly named driver) is present.
- If Interception is present, go straight to Method 1 (most reliable fix).
- If Interception is not obvious, start with Method 2 and Method 3 to rule out anti-cheat and other input-hook software.
Quick Checks (Confirm Whether Interception Is Present)
Before changing anything, confirm whether Interception (or a similarly named driver) is actually on the system. These checks are quick, but keep in mind that some tools install similar drivers under different names.
- Check the driver file: open this folder and look for interception.sys:
C:\Windows\System32\drivers
- Check hidden devices: open Device Manager > click View > Show hidden devices. Look under input-related sections for anything clearly tied to remappers, filters, or virtual input.
- Optional (advanced): list installed drivers (may miss drivers that use a different name):
driverquery /v | findstr /i interception
If you see a matching entry, Interception (or something named similarly) is likely installed.
Method 1. Uninstall the Interception Driver
If the Interception driver is installed, it can load at boot and remain detectable even when you are not actively using any remapping tool. Removing the driver stops anti-cheat from seeing an active Interception layer.
Note: The Interception GitHub release includes install-interception.exe, which can properly uninstall the driver.
- Go to the Interception GitHub Releases page and download the ZIP:
Interception GitHub release page

- Right-click the downloaded ZIP file, select Extract All, and choose a location to extract the contents.

- Open the extracted folder and locate install-interception.exe.Tip: If you do not see it immediately, use Windows Search inside the extracted folder and search for install-interception.exe.

- Press Windows + S, type cmd, right-click Command Prompt, and select Run as administrator.

- Run these commands (adjust the folder path to match where you extracted the files):
cd /d "C:\Users\YourName\Desktop\Interception\command line installer"
install-interception.exe /uninstall
Tip: In Command Prompt, type
cd /d(including the space), then drag-and-drop the folder into the window to paste the exact path.
- When the uninstallation finishes, restart your PC to apply the changes.
After reboot: launch the game again. If Interception was the trigger, the anti-cheat check should pass normally.
To confirm Interception is no longer present:
- Check:
C:\Windows\System32\drivers
If interception.sys is gone, that is a good sign.
- Optional (advanced) check:
driverquery /v | findstr /i interception
If it returns nothing, Interception is likely not registered as an installed driver under that name.
Method 2. Disable Third-Party Input Software
Some keyboard, mouse, controller, or macro tools install low-level input hooks for features like macros, rapid-fire, or advanced remapping. Anti-cheat may flag these as suspicious because they can resemble interception-style input filtering.
Examples: macro suites, remappers, virtual controller tools, scripting tools, emulator adapters, or specialized input drivers.
Step A (recommended): close the software completely and stop it from launching with Windows.
- Close the tool from the system tray (not just the window).
- Open Task Manager > Startup tab > disable remappers/macro tools you recognize.

- Restart your PC and test the game.
Step B (best for finding the exact culprit): do a clean boot and test.
- Press Windows + R, type msconfig, press Enter.

- Go to Services > check Hide all Microsoft services > click Disable all.

- Go to Startup > click Open Task Manager > disable non-essential startup apps.
- Restart and try launching the game. If it works, re-enable items gradually to identify the exact software causing detection.
Important: After testing, undo clean boot changes so your PC runs normally again (re-open msconfig and re-enable your usual services/startup items).
Step C (use only if you know what you’re disabling): temporarily disable suspicious input-related devices/drivers in Device Manager.
- Press Windows + X and select Device Manager.

- Look for obvious third-party entries related to remappers, virtual controllers, macro software, or input filters.
- Right-click a suspicious/unused third-party device and choose Disable device.

- Restart your PC and test the game.
Method 3. Temporarily Close Controller/Virtual Input Tools
Controller mapping and virtual input tools can keep a virtual controller layer active in the background. This is not Interception by itself, but it can contribute to anti-cheat input detection when combined with other remappers or leftover input drivers. Use this method only as a quick test if you actively use these tools.
Example: DS4Windows
- Open the DS4Windows menu from the system tray.
- Click Exit (or Stop/Quit, depending on your version).

- Press Ctrl + Shift + Esc to open Task Manager.
- End any tasks related to DS4Windows or other controller/remapping tools.

- Try launching the game again.
If this fixes it: disable the tool from Startup and only run it when you actually need controller mapping.
Method 4. Don’t Force the Game to Run as Administrator
In some setups, running a game with administrator permissions can change how anti-cheat initializes. If you enabled “Run this program as an administrator,” turn it off and test.
These steps show Rust as an example, but the same idea applies to other games.
- Open Steam and go to your Library.
- Right-click Rust (or your affected game) and choose Manage > Browse local files.

- Locate the game executable(s), for example:
RustClient.exe
Rust.exe
- Right-click an EXE and choose Properties.
- Open the Compatibility tab and uncheck Run this program as an administrator.
- Click Apply > OK.

- Close Steam/Epic (if applicable), reopen it, and try launching the game again.
Method 5. Clean Up Leftovers (interception.sys) If It Still Exists
If Interception was previously installed, the driver file can sometimes remain in the Windows drivers folder even after you uninstall. If interception.sys is still present, anti-cheat may keep detecting it.
This method is a fallback. The best fix is still Method 1 (proper uninstall). Use the steps below only if you confirmed the file is still there.
- Go to:
C:\Windows\System32\drivers

- Find interception.sys.
- Try renaming it to something like
interception.bak.

- Restart your PC and launch the game.
Method 6. Reset This PC (Last Resort)
If none of the methods above remove the detection, especially if multiple remapping tools were installed over time, a Windows reset can be the cleanest way to remove stubborn driver hooks and leftover input filters.
Important: Back up your important files first. A reset can remove apps and settings depending on the option you choose.
- Search for Reset this PC and open it.

- Click Get Started.

- Follow the on-screen steps and choose the option that fits your situation.
If you still see the message after a reset, it usually indicates another active remapper/virtual input layer is installed (or being loaded by a peripheral suite). Recheck controller/keyboard/mouse utilities and avoid input-hook tools before launching the game.





