Need to remove Windows 10 Pro test mode? The desktop watermark means Windows is allowing test-signed drivers. The supported fix is a BCDEdit command followed by a restart, but first identify any unsigned driver that may stop working when normal signature enforcement returns.
Open Command Prompt as administrator, run bcdedit -set TESTSIGNING OFF, and restart the PC. If Secure Boot blocks the change, save your BitLocker recovery key, temporarily disable Secure Boot, run the command, then enable Secure Boot again.
Test mode is a documented Windows state, not a virus or an activation failure. Microsoft calls it test signing. It lets Windows load drivers signed for testing rather than through the normal certification path.
Windows displays Test Mode in the lower-right corner while this setting is active. Microsoft explains the behavior in its test-signing documentation.
Why Windows Entered Test Mode
An unsigned or test-signed driver
Older peripherals, specialist hardware, virtual audio devices, capture hardware, and development tools may install a driver that depends on test signing.
Software with a low-level driver
Some emulation, VPN, backup, overclocking, or legacy protection software installs kernel components and may enable the setting during setup.
A previous manual workaround
A technician or earlier owner may have enabled it to make one device work and then left it active.
Test signing is a boot setting. It stays enabled across ordinary restarts and updates until a tool or administrator changes it.
Check Before You Remove Windows 10 Pro Test Mode
Turning test signing off restores normal signature enforcement. An unsigned driver that currently loads may stop, along with the device it controls.
- Identify hardware or driver software installed just before the watermark appeared.
- Find a current signed driver from the device manufacturer.
- Save your BitLocker recovery key before changing UEFI settings.
- Create a restore point before changing boot configuration.
BCDEdit changes Windows boot configuration. Type only the documented command below. Microsoft warns that incorrect BCDEdit changes can make a PC unbootable.
Use this broader diagnostic guide when a driver or Windows error accompanies the watermark.
How to Remove Windows 10 Pro Test Mode
- Open Start and type
cmd. - Right-click Command Prompt and choose Run as administrator.
- Run the command below exactly as written.
- Confirm that Windows reports the operation completed successfully.
- Restart the PC.
bcdedit -set TESTSIGNING OFF
Administrator rights and a restart are required. Microsoft documents both requirements in its BCDEdit /set reference.
Windows Terminal or PowerShell also works when opened as administrator. Use the same command without changing its spelling.
If Secure Boot Blocks the Command
The message The value is protected by Secure Boot policy and cannot be modified or deleted means the firmware policy is blocking the change.
- Save the BitLocker recovery key and suspend BitLocker if it protects the system drive.
- Restart into the PC manufacturer’s UEFI settings.
- Temporarily disable Secure Boot and save the change.
- Start Windows and run
bcdedit -set TESTSIGNING OFFas administrator. - Return to UEFI and enable Secure Boot again.
- Resume BitLocker protection if you suspended it.
Do not leave Secure Boot disabled. Firmware menus differ by manufacturer, so use the support instructions for your exact PC or motherboard.
If the Watermark Returns After Restarting
A program is enabling it again
Remove or update the suspected driver utility, restart, and repeat the supported command. Do not use watermark-hiding software.
Another integrity setting is present
Run bcdedit by itself and review the current Windows Boot Loader entry. If you previously changed other integrity settings, reverse only changes you recognize. Avoid copying unrelated BCDEdit commands from forums.
The wrong boot entry was changed
Dual-boot and repaired systems may contain several loader entries. The active entry is normally marked {current}. Get expert help before editing a different identifier.
Does This Work on Windows 11?
Yes. Microsoft documents the same TESTSIGNING setting for current Windows driver development. Windows 11 systems may also use Memory Integrity, which can block incompatible drivers even when test signing is enabled. A device that requires multiple protections to be disabled needs a current signed driver or replacement hardware.
Restore the broader Windows security protections after resolving the driver issue.
Is Leaving Test Mode On Risky?
Test mode is not malware, but it relaxes a driver trust check. Kernel drivers operate with deep system access, so leaving the setting enabled increases the consequence of installing an unsafe or badly written driver.
Use test mode only for a known development or compatibility need. On an everyday PC used for work, banking, or personal files, restore standard enforcement as soon as the required signed driver is available.
Avoid Watermark Removal Tools
Utilities that merely hide the watermark do not necessarily disable test signing. Some patch system files, which can create servicing problems while leaving the underlying security setting active. Use the supported BCDEdit setting instead.
If driver instability causes crashes, follow the Windows stop-error troubleshooting guide separately.
How to Confirm Test Mode Is Off
- Open Command Prompt as administrator.
- Run
bcdedit. - Find the current Windows Boot Loader entry.
- Check that
testsigningis absent or readsNo.
A missing watermark plus an absent or disabled testsigning value confirms the change. If a device now shows a warning in Device Manager, install a current signed driver from its manufacturer.
Frequently Asked Questions
Will removing test mode delete files?
No. It changes a boot configuration setting. Your documents and applications remain in place.
Can I turn test mode back on?
Yes. The documented opposite setting is bcdedit -set TESTSIGNING ON, followed by a restart. Use it only for a known test-driver need.
Why does BCDEdit say access is denied?
The terminal is not elevated. Close it and reopen Command Prompt, Terminal, or PowerShell with Run as administrator.
Does Test Mode mean Windows is not activated?
No. Windows activation and driver test signing are separate systems and display different messages.
Is Test Mode the same as Safe Mode?
No. Safe Mode is a diagnostic startup with limited drivers. Test mode is a normal startup that permits test-signed drivers.
Why did a device stop working afterward?
Its driver may have depended on test signing. Install a supported signed driver, or contact the manufacturer before temporarily re-enabling test mode.
Final Takeaway
Use the Microsoft-supported TESTSIGNING setting, restart, and verify the current boot entry. If a driver stops working, replace that driver rather than hiding the watermark or permanently weakening Secure Boot and driver enforcement.
