sodcalculator

10 Tech How-To

Fix No Signed Device Drivers Were Found Error

Guide 10-32148 · Updated · Step by step

If you see the “No signed device drivers were found” error during Windows installation, the fix is usually to disable Secure Boot or load the correct storage driver. This guide explains why the error appears and walks through the most reliable solutions.

What Causes This Error?

Windows Setup checks that every driver it loads is digitally signed. When you install Windows on a newer PC (especially one with an Intel 11th-gen CPU or later, or an AMD Ryzen with a similar chipset), the storage controller may not be recognized. The installer then cannot find a signed driver for your hard drive or SSD, so it stops with that message.

Common triggers include:

  • Intel VMD (Volume Management Device) or AMD RAID mode enabled in BIOS
  • Missing IRST (Intel Rapid Storage Technology) driver on the installation USB
  • Secure Boot blocking unsigned or third-party drivers
  • Using a Windows ISO that lacks the latest storage drivers

Fix 1: Disable Secure Boot and VMD/RAID in BIOS

The quickest fix is to change BIOS settings. Restart your PC and press the key shown on screen (usually Del, F2, F10, or Esc) to enter UEFI/BIOS. Then:

  1. Find Secure Boot (often under Security or Boot tab) and set it to Disabled.
  2. Look for VMD or Intel Rapid Storage Technology (or AMD RAID) and set it to Disabled or AHCI mode.
  3. Save changes and exit (usually F10).
  4. Boot from your Windows USB again and try the installation.

If you don’t see these options, check your motherboard manual – they can be under “Advanced” or “PCH Storage Configuration.”

Fix 2: Load the Storage Driver During Setup

If you cannot disable VMD/RAID (or prefer to keep it), you can supply the driver manually. Windows Setup has a “Load driver” button on the screen where you choose the disk. You need the driver files (usually a .inf or .sys) on a separate USB stick.

  1. Download the appropriate driver from your PC manufacturer’s support page (e.g., “Intel VMD controller driver” or “AMD RAID driver”).
  2. Extract the files to a USB drive (FAT32 format works).
  3. During Windows Setup, when you reach the “Where do you want to install Windows?” screen, click Load driver.
  4. Browse to the USB drive, select the driver, and click Next. Windows will install it and then show your drive.

Make sure the driver matches your Windows version (64-bit vs 32-bit) and your processor generation.

Fix 3: Use a Windows ISO with Integrated Drivers

If the error persists, the ISO you are using may be outdated. Microsoft’s Media Creation Tool downloads the latest version, but some OEM PCs need a special ISO that includes the VMD driver. You can:

  • Download the latest Windows ISO from Microsoft’s website.
  • Use a tool like Rufus to create the bootable USB – it can inject the driver automatically if you have the .inf file.
  • Alternatively, use the PC manufacturer’s recovery media if they provide one.

This is especially common when installing Windows 10 on a laptop designed for Windows 11.

Why Does This Happen on Newer PCs?

Intel introduced VMD with 11th-gen processors (codenamed Tiger Lake) to improve storage performance and security. When VMD is enabled, the SSD is not visible to Windows Setup unless the VMD driver is loaded. AMD has a similar feature called “RAID mode” on their chipsets. Both features are off by default on many motherboards, but some OEMs enable them from the factory. That’s why you see the error on a brand-new laptop but not on an older desktop.

Common Mistakes and Misconceptions

Many users think the error means their hard drive is broken – it usually isn’t. Another mistake is trying to format the drive from a different tool before loading the driver; that doesn’t help. Also, disabling Secure Boot alone won’t fix the issue if VMD is still on. And if you load the wrong driver (e.g., a 32-bit driver on a 64-bit Windows), Setup will reject it with the same error.

One misconception is that you must enable “Compatibility Support Module” (CSM) to fix this. CSM is for legacy BIOS boot, and it can actually cause other problems. Stick to UEFI mode with Secure Boot off (or the correct driver loaded).

Alternatives If Nothing Works

If you still get the error:

  • Try a different USB port (preferably USB 2.0) and recreate the bootable USB.
  • Check if your BIOS has an update – manufacturers often add better VMD support.
  • Reset BIOS to defaults (often F9 or “Load Optimized Defaults”) and try again.
  • If you are installing on an NVMe SSD, try a SATA SSD temporarily – it may be recognized without a driver.

If all else fails, contact your PC manufacturer’s support – they may have a specific driver package for your model.

Frequently Asked Questions

Does disabling Secure Boot affect Windows 11 installation?

Yes, Windows 11 requires Secure Boot to be enabled. If you disable it to install Windows 10, you can re-enable it after installation, but you may need to load the VMD driver first. For Windows 11, you can load the driver while Secure Boot is on – the driver is signed, so it works.

Can I use a USB 3.0 drive for the driver?

Yes, but if Windows Setup doesn’t see the USB drive, try a USB 2.0 port. Some BIOS versions don’t initialize USB 3.0 during setup.

Is it safe to disable VMD?

Yes, disabling VMD just makes the storage controller work in standard AHCI mode. You may lose some advanced features like Intel Optane memory support, but your data remains intact.

Why does the error say “no signed drivers” when I’m using an official Microsoft ISO?

Because the storage controller is not recognized by the generic Microsoft driver. The “signed” part refers to the driver signature, not the ISO. The VMD driver is signed, but it’s not included in the default Windows installation.

Can I install Windows on a RAID array with this error?

Yes, but you must load the RAID driver from your motherboard manufacturer. The process is the same as loading the VMD driver – just use the RAID driver instead.

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 →