Almost nobody turns on test mode on purpose, yet the watermark shows up on plenty of PCs. Something with administrator rights changed one boot setting, usually during an install. This guide lists the honest usual suspects so you can identify yours before you switch it off.
Test signing cannot switch itself on. The boot configuration only changes when a command runs with administrator rights, and that means the change happened during something you, or a technician, installed or ran. Knowing the route matters for one practical reason: if a device or program on your PC still needs that setting, it will either stop working when you turn test mode off, or quietly turn it back on. Walk through the usual routes below and see which one sounds like your PC's history.
The most common story. A printer, scanner, capture device, adapter or other hardware is old enough, or obscure enough, that its maker never provided a properly signed driver for modern Windows. The driver package that does exist is test-signed, or its installer enables test signing so the driver can load. The install finishes, the device works, and the watermark is left behind as an unmentioned part of the bargain.
The clue is timing. If the watermark appeared around when a particular device was set up, that device is your suspect, and it is also the device most likely to stop working when test mode goes off.
Many fix guides and videos for stubborn hardware problems include a step like bcdedit /set testsigning on to get an unsigned driver working. The follow-up step, turning it back off once the job is done, is often missing from the guide or skipped in a hurry. The PC then stays in test mode permanently, long after the original problem was solved.
If you have ever followed a forum post or tutorial to force a driver onto this PC, this is very likely your route, and the good news is that nothing usually depends on it anymore.
Some utilities, emulators, phone flashing tools, virtual hardware tools and similar low-level software install their own drivers. A few of their installers enable test signing as part of setup, mentioning it only in a log or not at all. The software works, so nobody questions the watermark.
This route has an extra consequence: software of this kind sometimes re-applies the setting on every launch or every boot. If test mode keeps coming back after you turn it off, a program like this is the first place to look.
Sometimes the cause is legitimate and known: driver development, testing, or a technician who enabled test signing during a repair and forgot the final step. Nothing about this is sinister, but the fix is the same. Finish the job. If the development or repair work is over, run bcdedit /set testsigning off, restart, and confirm the watermark stays gone.
Whatever your route was, the pattern to learn is this: the watermark is a receipt. It tells you a change was made. Before removing it, spend two minutes asking which device or program the change was for, and you will already know whether turning test mode off will be a one-minute fix or the start of a small driver hunt.
See every step done live on a real Windows PC in the Technical Anshu video, including the exact command and the restart.
▶️ Watch Full VideoNot precisely. Windows does not keep a friendly history of boot configuration changes. The practical method is to match the watermark's first appearance with what was installed around that time. Recent driver installs in Device Manager and recently installed programs in Settings are the two lists worth scanning.
Yes, in almost every case. A repair or setup job is finished work, and test mode should have been turned off at the end of it. Turn it off, restart, and check your devices. Only if a specific device stops working is there anything to discuss, and the answer then is a properly signed driver for that device.
That is the most common situation of all, and it changes nothing. Turn test mode off and restart. Windows will tell you the truth immediately: if everything works, the setting was a leftover. If one device stops, you have found the dependent device and can deal with just that one.