This means Windows is running in test-signing mode, which allows unsigned drivers, and BattlEye refuses to run in it. Turning it off lets the game start. Jump to your situation below or work through the methods in order.
The Windows Test-Signing Mode not supported error means Windows is booted with test signing enabled, a mode that lets unsigned drivers load, and BattlEye refuses to run in it for security reasons. You often see a Test Mode watermark in the bottom-right corner of the desktop. The fix is to turn test signing off from an administrator Command Prompt with bcdedit /set testsigning off, then restart. If it turns back on by itself, some installed software is enabling test mode to load its own unsigned driver, so you will need to identify and update or remove that software. Note that Secure Boot and test-signing mode are mutually exclusive, so enabling Secure Boot in your BIOS also forces test signing off and keeps it off. Related BattlEye errors in the same family, Kernel Debugging enabled and Windows Kernel modification detected, are fixed the same way, by disabling the mode that BattlEye does not allow. Once test signing is off, BattlEye initializes and the game runs.
Test-signing mode lets Windows load drivers that are not signed by a trusted authority, which is a security risk. BattlEye will not run while it is enabled, so the game fails to start with this error. A Test Mode watermark on the desktop confirms the mode is active.
Turning test signing off with bcdedit and restarting fixes it. If it re-enables, some software is turning it on to load an unsigned driver, which you must address. Enabling Secure Boot also forces test signing off, since the two cannot be active together.
“This one is usually a leftover. Some tool or driver install flipped Windows into test-signing mode so it could load an unsigned driver, and now there is a Test Mode watermark in the corner and BattlEye refuses to run. One command in an admin prompt, bcdedit /set testsigning off, and a restart fixes it. If it keeps coming back, something is re-enabling it, so find that software. And a neat trick: turning on Secure Boot in the BIOS forces test signing off for good, because you cannot have both.”
bcdedit /set testsigning off
bcdedit /debug off
The BattlEye Windows Test-Signing Mode not supported error means Windows is in test-signing mode. Turn it off with bcdedit /set testsigning off from an admin prompt and restart. If it re-enables, find the software turning it on. Enabling Secure Boot also forces test signing off. The Kernel Debugging enabled error is fixed the same way with bcdedit /debug off.
If bcdedit reports the value is set but test mode persists, BitLocker or a Secure Boot policy may be involved; suspend BitLocker before the change, or enable Secure Boot, then re-run the command. You can also submit your error to us for a tailored fix.
