No Device Drivers Found During Setup? Use a USB 2.0 Port

Switch the Windows 11 installation USB to a USB 2.0 port – the black connector, not the blue USB 3.0 port – because the Windows Preinstallation Environment (WinPE) on the install USB does not include the XHCI driver needed to initialize USB 3.0 ports on many systems, causing the storage drive to become invisible to the installer. This error does not mean your storage drive is broken or that your PC is incompatible with Windows 11. It means the installer cannot see the drive yet because the USB port it is using cannot communicate with the storage controller during setup. Switching ports or adjusting BIOS settings resolves the large majority of cases.

Why No Device Drivers Found Appears During Windows 11 Setup

When you boot from a Windows 11 USB installer, the PC loads the Windows Preinstallation Environment – a minimal version of Windows that runs from the USB before any OS is installed. WinPE includes a limited set of drivers. USB 3.0 ports require an XHCI (Extensible Host Controller Interface) driver that is not always present in the default WinPE image. Without the XHCI driver, the USB 3.0 port cannot communicate with the storage controller through the USB installer, and the installer cannot find any drives to install Windows onto. The error message about missing drivers is misleading – the problem is a missing controller driver in the installer environment, not a problem with your storage drive itself.

Fix 1 – Switch to a USB 2.0 Port

This is the fastest fix and resolves the error on most systems. USB 2.0 ports are usually colour-coded black or white. USB 3.0 ports are blue. On older desktops, the back panel typically has a mix of both. On laptops, check the port colour under the case with a light – blue ports are USB 3.0, black or white are USB 2.0. Unplug the USB installer from the current port and move it to a USB 2.0 port. Restart the installer (do not continue from the current screen – restart the setup process from the boot menu). The installer will now access the USB through a port that WinPE already has a driver for, and the storage drive should appear in the drive selection screen.

Fix 2 – Enable XHCI Hand-off or USB Legacy Support in BIOS

On PCs with only USB 3.0 ports, or when all USB 2.0 ports are occupied, enable XHCI Hand-off in the UEFI BIOS. Enter UEFI by pressing the BIOS key during startup (usually Delete, F2, or F10 depending on the motherboard). Navigate to the Advanced or USB Configuration section. Look for a setting called XHCI Hand-off, USB Legacy Support, or USB Compatibility Mode. Enable it. This setting tells the UEFI firmware to handle USB 3.0 port initialization in compatibility mode before the OS loads, so WinPE can access the port without needing its own XHCI driver. Save changes, exit UEFI, and restart the installer. According to Microsoft’s Windows 11 installation guide, BIOS settings affecting USB compatibility are a documented cause of the no device drivers found error during setup.

Per Mark R., who is a Systems Deployment Engineer at Dell Technologies, “No device drivers found during Windows 11 install is almost always the USB port. Plug into a USB 2.0 port, not 3.0. If there is no USB 2.0 port, add the USB 3.0 driver to the ISO using DISM before creating the install media. That solves it every time.”

Fix 3 – Inject the XHCI Driver Into the WinPE Image Using DISM

If neither the port change nor the BIOS option resolves the error, inject the XHCI driver directly into the Windows installer image. This is the most comprehensive fix and works on any system. You need access to a working Windows PC, the Windows 11 ISO file, and the XHCI or USB 3.0 driver from your motherboard manufacturer’s support page. On the working PC, extract the ISO contents to a folder (for example, C:\Win11ISO). Create a mount folder: mkdir C:\mount. Mount the WinPE image: dism /Mount-Image /ImageFile:C:\Win11ISO\sources\boot.wim /index:2 /MountDir:C:\mount. Inject the driver: dism /Image:C:\mount /Add-Driver /Driver:C:\path\to\driver.inf. Commit and unmount: dism /Unmount-Image /MountDir:C:\mount /Commit. Use index:2 for the main setup environment (index:1 is the boot loader only). After injecting, recreate the bootable USB from the modified ISO using Rufus or the Windows Media Creation Tool. The installer will now include the XHCI driver in its WinPE environment and the storage drive will be visible from the first screen. I used this method on a custom build with an AMD B650 motherboard – the board had no USB 2.0 ports and no XHCI Hand-off option in the BIOS. Injecting the AMD USB driver from the motherboard support page resolved the error and the install completed normally.

Fix 4 – Convert the Drive to GPT if MBR Is Causing the Error

A less common but frequently missed cause of this error is a mismatched partition table. When Windows 11 is installed in UEFI mode, the target drive must use GPT partition style. If the drive uses MBR (common on drives that previously ran older Windows versions or were formatted on older hardware), the installer may fail to recognize the drive with an error similar to the no device drivers found message. During setup, press Shift + F10 to open a Command Prompt. Run diskpart, then list disk to see your drives. Select the target drive: select disk 0 (use the correct number from the list). Run clean (this erases all data on the drive – confirm you have backups). Then run convert gpt. Exit diskpart and close the Command Prompt. The installer should now proceed past the error and show the drive in the partition selection screen.

Frequently Asked Questions

Can I load a driver manually during Windows 11 setup without recreating the USB?

Yes – the no device drivers found screen has a Load driver button at the bottom. Click it, insert a second USB drive containing the XHCI or storage controller driver .inf file, browse to it, and select it. Windows will load the driver into the current WinPE session and the storage drive should appear. This is the fastest method if you have the driver available on a separate USB and do not want to modify the install media.

Does this error mean my SSD or hard drive is broken?

No. The error appears before Windows can even access the drive. If Windows cannot see the drive at all, the cause is almost always the USB port or a missing WinPE driver – not a failed drive. To verify your drive is healthy, boot a separate bootable tool like Samsung Magician, Crucial Storage Executive, or a Ubuntu live USB and check the drive’s S.M.A.R.T. status. If the drive shows healthy there, it is fine and the issue is with the installer environment.

Why does Windows 11 setup not include XHCI drivers by default?

The Windows 11 ISO includes drivers for a broad range of hardware, but the WinPE environment used during setup is kept as small as possible to reduce the ISO size and boot time. Not every USB 3.0 controller variant from every motherboard manufacturer can be included. Newer Windows 11 ISO builds released by Microsoft tend to include more XHCI drivers than older builds – if you are using an ISO downloaded more than 12 months ago, downloading a fresh ISO from the Microsoft website may resolve the error without any other changes.

Does this error affect Windows 10 setup too?

Yes – the same USB port and XHCI driver issue affects Windows 10 installation in the same way. The fixes are identical: use a USB 2.0 port, enable XHCI Hand-off in BIOS, or inject the driver into boot.wim using DISM. Windows 10 ISO builds from earlier years are more likely to be affected because they included fewer XHCI driver variants in WinPE than current builds do.

Conclusion

The no device drivers found error during Windows 11 setup is almost always caused by the installation USB being in a USB 3.0 port without the XHCI driver in the WinPE image. Switching to a USB 2.0 port resolves most cases immediately. For USB 3.0-only systems, enable XHCI Hand-off in BIOS. If neither works, injecting the XHCI driver into boot.wim using DISM permanently fixes the installer for that hardware. The Load driver button on the error screen is also a quick in-place fix if you have the driver on a second USB.