You typed the correct command and Windows refused it. That is frustrating, but BCDEdit errors are unusually honest: each message points at one specific cause, and none of them means Windows is broken. Match your error below and fix that one thing.
The command to turn off test mode is short, bcdedit /set testsigning off, but it touches the boot configuration, the most protected settings store on the PC. When it fails, it fails for a reason: the window was not elevated, Secure Boot is protecting the value, the command was typed slightly wrong, or the boot store itself needs attention. Guessing and retyping will not help. Reading the exact error will. This guide goes through the real messages one by one, in the order people actually meet them.
This is the number one failure by a long way. Being signed in with an administrator account is not enough. The Command Prompt window itself must be running elevated, or BCDEdit will not even open the boot store.
cmd, right-click it and choose Run as administratorbcdedit /set testsigning off again. It should now answer The operation completed successfully.If the error says the value is protected by Secure Boot policy and cannot be modified or deleted, Windows is telling you Secure Boot is enabled and is locking this boot setting. That is Secure Boot doing its job, and it has its own dedicated guide in this set because the handling belongs in the BIOS or UEFI settings, not in more command attempts.
One useful side observation: test-signed drivers cannot load while Secure Boot is on anyway, so if you see this error, your PC's situation is slightly different from the usual watermark case and worth handling carefully rather than forcefully.
A message saying the specified element cannot be found, or that the store could not be opened for a different reason, usually means one of two things. Either the command was aimed at the wrong entry because it was typed with extra changes, or the PC was booted in a way that the default store is not the live one, which happens on some dual-boot setups.
bcdedit with no switches. If a normal boot list appears, the store is fine and the problem is the command linebcdedit /set testsigning off. Watch for smart quotes pasted from a web page, a missing space, or the word written as one word like testsigningoffbcdedit itself fails, restart the PC and try again from an elevated window before assuming deeper damageA success message with the watermark still present after a restart is a different complaint from a failed command, and it deserves a calm check rather than stronger commands. Run bcdedit /enum {current} and read the testsigning line. If it says No, the setting is genuinely off and a leftover watermark display usually clears on the next full restart; make sure you restarted rather than shut down with fast startup keeping the old session. If it says Yes again despite your successful command, something with administrator rights is setting it back, and that culprit hunt has its own guide.
What not to do in any of these cases: do not download BCDEdit repair tools or boot editors from random sites. The built-in tool plus the right window and the right BIOS state solves every error on this page.
testsigning is one word, /set needs its space, and the command is bcdedit /set testsigning off exactly. Paste it into the elevated window and most mystery errors never happen.See every step done live on a real Windows PC in the Technical Anshu video, including the exact command and the restart.
▶️ Watch Full VideoAlmost. That message means the boot configuration now has test signing off. Restart the PC, because the change takes effect at boot. After the restart the watermark should be gone. The success message plus a restart is the complete fix.
The boot configuration decides what code runs before and inside Windows itself, so Windows guards it at the highest level. Any tool or person who could change it freely could also weaken boot security. The elevation requirement is the protection working as intended, not an obstacle.
Usually not. First make sure the window is elevated and that you are booted into the Windows installation you think you are, which matters on dual-boot PCs. If a plain bcdedit command still cannot open the store after a restart, that points to a boot configuration problem that deserves proper diagnosis with recovery tools, which is a separate and bigger topic than test mode.