LatencyMon, WhySoSlow and SanityCheck drivers blocked by new Windows policy
Temporary Workarounds for Systems Affected by the Driver Block
Unfortunately, Microsoft has recently decided to remove trust for legacy drivers that were cross-signed. As this policy change is being rolled out more broadly through Windows updates, it is affecting an increasing number of computer systems.
This is the cleanest and safest approach, as it does not require disabling Secure Boot or making any changes to your system configuration.
This option creates a separate boot menu entry that disables Driver Signature Enforcement. However, it requires several additional steps,
including temporarily disabling Secure Boot.
bcdedit /copy {current} /d "Test Mode"
bcdedit /set testsigning on
This approach can be more complex and may reduce certain security protections, so it should only be considered by experienced users who understand the associated risks. For
example, if you skip the step of disabling Secure Boot, the system may fail to boot using the modified startup configuration.
We are have recently requested Microsoft to have our drivers added to their explicit allow list of reputable drivers. Although our initial request was not approved, we continue to actively pursue a resolution.
In parallel, we are currently completing the enrollment process required to gain access to Microsoft's Hardware Developer Center, which is necessary for WHQL driver signing.
This may take several weeks to complete, but it is expected to provide a long-term solution to these issues.
For more information, please see Microsoft's announcement:
Advancing Windows Driver Security
If your system is affected by this issue and you need to run our software, there are currently three ways to work around the restriction.
The following temporary workarounds will allow affected drivers to continue operating:
Temporarily disabling driver signature enforcement during startup
This option temporarily disables Driver Signature Enforcement for the current boot session, allowing drivers that would normally be
blocked to be loaded. Driver Signature Enforcement is automatically restored the next time the system is restarted.
When your system boots and displays Choose an Operating System, select Change defaults or choose other options. Then select
Choose other options -> Troubleshoot -> Advanced Options -> Startup setings -> Restart.
After the system restarts, a Startup Settings menu will be displayed. Select Disable Driver Signature Enforcement.
Then log in to your system and you should be able to run LatencyMon, WhySoSlow and SanityCheck without any warnings.
Creating a separate boot entry configured for Test Signing mode and using that boot option when running the affected product and their drivers
Test Mode allows Windows to load test-signed drivers that would normally be rejected. While this is intended for driver
development and testing and generally has little impact on normal system operation, it reduces one of Windows'
driver security protections and should therefore only be enabled if you understand and accept the implications.
NOTE: If your system uses BitLocker drive encryption, the process becomes more involved, as you may be required to provide your BitLocker recovery key
after disabling Secure Boot.
1. If you system has Secure Boot enabled, enter your BIOS setup utility and temporarily disable Secure Boot.
The option to disable Secure Boot is often located under a menu named Security or Boot Options in your system's BIOS/UEFI setup program.
2. Boot the system and open a command prompt with Administrator Privileges.
3. Create a new boot entry by copying your current boot settings:
4. Reboot your system and select Test Mode at boot time when presented with Choose an Operating System.
5. Enable test mode. Start a command prompt with administrator privileges again and type:
bcdedit /set nointegritychecks on
6. Restart your system. If you previously disabled Secure Boot in your BIOS/UEFI settings, you can now re-enable it. Select
Test Mode at boot time when presented with Choose an Operating System.
7. Log in to your system. A Test Mode watermark appears on the desktop. You should be able to run LatencyMon, WhySoSlow and SanityCheck without any problems.
Disabling the Windows driver-blocking policy on the system
NOTE: If your system uses BitLocker drive encryption, the process becomes more involved, as you may be required to provide your BitLocker recovery key
after disabling Secure Boot.
Instructions on removing the policy can be found below. Scroll down to the FAQ and expand
How do I turn off the Windows Driver policy
Copyright © 1997-2026 Resplendence Software Projects, a trademark of SoftRev Labs S.r.l.s. All rights reserved. Privacy Policy.
Page generated on 2026-06-18 09:22:20 PM. Last updated on 2026-06-18 03:10:02 PM.