This is the one situation where test mode is not simply a mistake. A device you own works only with a driver that has no proper signature, and turning test mode off turns the device off. Before you accept a permanently weakened PC, you deserve a clear view of every option and what each one actually costs.
Let us state the trade plainly. Keeping test mode on keeps your device working, and it also keeps the driver signature barrier lowered for the entire PC, every hour of every day, for every program, not just your device. That may still be the right call in a narrow set of circumstances. But it should be a decision, not a default. This guide walks through the options in the order you should try them, including the one most people skip: finding out whether a signed driver actually exists.
Many unsigned driver stories end early because the signed driver existed all along and was simply not the first search result. Check the device maker's own support page for your exact model, not a driver download portal. Check Windows Update's optional driver updates in Settings, which quietly carries signed drivers for a surprising amount of older hardware. And check whether the device works with a generic signed driver already inside Windows, as many printers, serial adapters and audio devices do.
Spend thirty genuine minutes on this before concluding anything. If a signed driver exists, install it, turn test mode off with bcdedit /set testsigning off, restart, and the whole dilemma evaporates.
If the device is cheap or old, replacing it with a current model that has signed drivers is often cheaper in risk than it looks in money, and it ends the problem forever. This is especially true for small USB adapters, capture dongles and ageing peripherals whose makers have moved on.
If the device is valuable or specialised, isolation is the professional answer: keep it on a spare PC, an old laptop, or a dedicated machine where test mode harms little because the machine holds nothing important and touches nothing sensitive. Your main PC returns to full protection, and the device still earns its keep. Technicians run exactly this arrangement for legacy hardware all the time.
If you choose this, choose it completely, with conditions. Know that while test signing is on, any installer that gains admin rights faces a lowered barrier for loading drivers, so be stricter than usual about what you install and from where. Keep your antivirus fully active and updated. Do your banking and sensitive work with extra care, or on another device. Write down why test mode is on and review the decision when the device is retired.
What not to do is drift into this state. The PCs most at risk are the ones in test mode for a device that was thrown away two years ago. If you keep test mode, keep it on a list, with a reason and a review date.
You will find tools and services online offering to sign any driver, remove signature checks entirely, or sell certificates of doubtful origin. Leave all of them alone. At best they replicate the same weakening with extra steps; at worst they are malware delivery dressed as a favour. The honest routes are only three: a genuinely signed driver, an isolated machine, or a knowingly accepted risk. Anything else is a worse version of the problem.
See every step done live on a real Windows PC in the Technical Anshu video, including the exact command and the restart.
▶️ Watch Full VideoThe risk is real but not instant doom. It means one of Windows' strongest driver protections is relaxed for everything, all the time. Most days nothing bad happens. The danger is the one day a malicious or careless installer uses the open door. That is why isolating the device is preferred: it keeps the convenience and removes the exposure.
You can switch it with bcdedit and a restart each time, and some people with rare-use devices do exactly that: on for the session, off afterwards, restart both ways. It is tedious but honest, and for a device used once a month it is a reasonable middle path that keeps the PC protected the rest of the time.
Sometimes a successor company, a chipset maker's reference driver, or Windows' own generic driver covers the hardware, since many devices share the same underlying chip. Identify the hardware ID in Device Manager and search by that, carefully, preferring the chipset maker's site. If none of those yield a signed driver, the honest options are isolation or replacement.