sodcalculator

10 Tech How-To

Driver Cannot Be Loaded on This Device: Fixes

Guide 10-35142 · Updated · Step by step

If you see the error “Driver cannot be loaded on this device,” it usually means Windows has blocked a kernel-mode driver from loading, often due to a security policy, a corrupted driver file, or an incompatible driver version. The fix typically involves checking the driver’s signature, updating it through the manufacturer’s site, or adjusting Windows security settings—but the exact solution depends on the driver and the error’s context. Below, we break down the causes, step-by-step fixes, and answers to common questions.

What Does This Error Actually Mean?

Windows loads drivers as part of its kernel, the core of the operating system that has full access to hardware. To protect system stability and security, Windows 10 and 11 enforce driver signing—every kernel driver must have a valid digital signature from a trusted source. When a driver is unsigned, has an expired signature, or is blocked by a security feature like Memory Integrity (HVCI), Windows refuses to load it and shows the “Driver cannot be loaded on this device” message. This error can also appear when a driver is corrupted, outdated, or incompatible with your Windows version.

Common Causes and Contexts

The error appears in several scenarios, and knowing which one you’re facing helps narrow the fix:

  • Memory Integrity (HVCI) blocking: Windows Security’s Core Isolation feature can block drivers that aren’t compatible with virtualization-based security. This is the most common cause on newer Windows 11 systems.
  • Unsigned or improperly signed drivers: Older hardware or third-party drivers may lack the required signature, especially after a Windows update.
  • Corrupted driver files: A failed update or disk issue can leave driver files damaged.
  • Incompatible driver version: Installing a driver meant for a different Windows version (e.g., a Windows 7 driver on Windows 11) triggers this error.
  • Group Policy restrictions: On managed or corporate PCs, an administrator may have set a policy that blocks certain drivers.

Step-by-Step Fixes to Try

Work through these solutions in order, testing the driver after each one. You’ll need administrator privileges for most steps.

  1. Check the driver’s signature: Right-click the driver setup file, select Properties, and look at the Digital Signatures tab. If it says “No signature was present,” the driver is unsigned. In that case, you’ll need to either find a signed version or use the advanced startup option to allow unsigned drivers (see step 4).
  2. Update or reinstall the driver: Go to Device Manager, find the device (often shown with a yellow warning icon), right-click it, and select Update driver. If that doesn’t work, download the latest driver from the hardware manufacturer’s website, uninstall the current driver (right-click > Uninstall device, then check “Delete the driver software for this device”), and install the fresh one.
  3. Temporarily disable Memory Integrity: Open Windows Security > Device security > Core isolation details, and toggle Memory integrity off. Restart your PC, then try loading the driver again. If it works, you’ll need to decide whether to keep the driver and leave Memory Integrity off (not recommended for security) or find a compatible driver. Re-enable Memory Integrity after testing.
  4. Use advanced startup to allow unsigned drivers: If the driver is unsigned and you must use it, restart your PC while holding Shift, go to Troubleshoot > Advanced options > Startup Settings, and click Restart. After the reboot, press 7 or F7 to select “Disable driver signature enforcement.” Note that this only lasts for that session; you’ll need to repeat it each boot. This is a temporary workaround, not a permanent fix.
  5. Check Group Policy: Press Win + R, type gpedit.msc, and navigate to Computer Configuration > Administrative Templates > System > Driver Installation. Look for policies like “Code signing for device drivers” and set them to Not Configured or Enabled with “Warn” instead of “Block.” Note that gpedit.msc is only available on Pro or Enterprise editions of Windows.
  6. Check for Windows updates: Sometimes a pending Windows update resolves compatibility issues. Go to Settings > Windows Update and install all available updates, then restart and try again.

When the Error Occurs on a Specific Device

If the error names a particular driver (e.g., a printer, GPU, or network adapter), the fix may be more specific. For example, with a printer, the error often appears after a Windows update that breaks the printer driver. In that case, uninstalling the printer from Settings > Bluetooth & devices > Printers & scanners and re-adding it can help. For GPU drivers, using a tool like Display Driver Uninstaller (DDU) in Safe Mode ensures a clean installation. Always download drivers from the manufacturer’s official website, not from third-party driver update tools, which often bundle malware or outdated files.

What NOT to Do

Some online advice suggests disabling driver signature enforcement permanently or using command-line tricks to force-load unsigned drivers. Avoid these because they weaken Windows security and can cause system instability. Similarly, don’t download “driver updater” software that claims to fix all driver issues—these are often adware or worse. If a driver is truly incompatible with your Windows version, the correct solution is to find a newer driver or contact the hardware manufacturer for support, not to bypass the security checks.

Frequently Asked Questions

Q: Can I permanently disable driver signature enforcement?
No, not through normal means. You can enable test mode via bcdedit /set testsigning on in an elevated command prompt, but this permanently weakens security and is not recommended. It’s better to find a signed driver.

Q: Why does the error appear after a Windows update?
Windows updates can change security policies or introduce a new version of Memory Integrity that blocks older drivers. It can also replace a driver with a Microsoft-provided one that conflicts with your hardware. Reinstalling the manufacturer’s driver usually fixes it.

Q: Does this error mean my hardware is broken?
No, it’s a software issue. The driver is being blocked or is corrupted, but the hardware itself is likely fine. If the device stops working entirely, try connecting it to another PC to confirm.

Q: What if the driver is for a peripheral like a USB device?
USB devices often use generic Windows drivers, so this error is less common. If it happens, unplug the device, uninstall the driver from Device Manager, and plug it back in. Windows will reinstall the driver automatically.

Q: Is it safe to turn off Memory Integrity?
Memory Integrity is a security feature that protects against malicious code running in high-privilege areas. Disabling it reduces your system’s security. Only do this temporarily to test, and re-enable it as soon as possible.

Q: Can I fix this in Safe Mode?
Yes, booting into Safe Mode loads only essential drivers, which can help you uninstall a problematic driver. To enter Safe Mode, hold Shift while clicking Restart, then go to Troubleshoot > Advanced options > Startup Settings and press 4 or F4.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →