Missing drivers during Windows installation from a USB stick typically occur because the media lacks storage controllers like NVMe or RAID, or network adapters. You can resolve this by injecting the necessary drivers into the installation image using DISM before booting, or by loading them manually via "Have Disk" if they are already on a separate drive.
Understanding the Root Cause
When you create a bootable Windows USB stick using standard tools, it contains the generic drivers included in the official Microsoft ISO. Modern hardware often requires specific storage controllers (such as Intel RST, VMD, or AMD RAID) and sometimes Wi-Fi or Ethernet adapters that are not present in that base image. If these drivers are missing, the Windows Setup wizard cannot see your hard drive, leaving the partition selection screen empty. This is distinct from driver issues after installation; this problem happens strictly during the initial setup phase. It is crucial to distinguish between the installation environment and the final OS, as solutions differ significantly. For more context on managing drivers post-installation, you might find
How to Return to Original USB Driver? - Tech Support Guide helpful for understanding driver management workflows later.
Method 1: Injecting Drivers into the ISO (Recommended)
The most robust solution is to modify the Windows installation files on your USB stick to include the required drivers. This ensures that every time you install Windows on that machine, the drivers are available. You will need the original Windows ISO file and the specific drivers for your motherboard or laptop model.
First, mount the Windows ISO file so you can access its contents. Create a folder on your desktop named "WinISO" and copy all the files from the mounted ISO into this folder. Next, extract your storage controller drivers into another folder, such as "Drivers". Ensure you have the correct architecture (x64) and the latest version compatible with your hardware.
Open Command Prompt as an administrator. You will use the Deployment Image Servicing and Management (DISM) tool to integrate these drivers. The syntax requires pointing to the source directory (your extracted ISO files) and specifying the target location. Use the following command structure, replacing paths with your actual locations:
DISM /Image:C:\Path\To\WinISO /Add-Driver:"C:\Path\To\Drivers\driver.inf" /ForceUnsigned
If you have multiple driver files, you can add them individually or use a wildcard if supported by your specific DISM version, though individual addition is safer for ensuring each file loads correctly. After running the command, verify that no errors occurred. Once completed, you must update the boot sector of the USB drive to reflect these changes. If you created the USB using Rufus or Media Creation Tool, you may need to recreate the bootable drive using the modified files in the "WinISO" folder. Note that simply copying files to the USB does not always update the boot configuration properly, so recreating the bootable media from the modified folder is the safest approach.
Method 2: Loading Drivers During Installation
If you do not want to modify the ISO permanently, you can load drivers manually when the installer fails to detect your drive. This method is useful for one-time installations or when you cannot easily access the driver files beforehand.
Boot from your Windows USB stick and proceed through the initial language and keyboard selections until you reach the "Where do you want to install Windows?" screen. If the drive list is empty, click "Load Driver" at the bottom left of the window. You will be prompted to browse for the driver files. Navigate to a folder on your USB stick, a secondary USB drive, or a network share where you have stored the storage controller drivers.
Select the correct .inf file for your storage controller. Windows will scan the file and install the driver temporarily into the RAM-based installation environment. Once installed, refresh the drive list, and your system drives should appear. Select the desired partition and continue with the installation. This process does not persist the drivers into the final Windows image unless you also perform a custom unattend.xml injection, but it allows the installation to complete successfully.
Verifying Driver Compatibility
Before attempting either method, ensure you are downloading the correct drivers. Visit your computer manufacturer’s support page or your motherboard vendor’s website. Look for "Storage," "SATA," "RAID," or "VMD" drivers specifically labeled for Windows 10 or 11. Avoid using generic drivers from third-party sites, as they may lack digital signatures or compatibility layers required by the Windows PE (Preinstallation Environment). Also, check if your BIOS settings are configured correctly. Some systems require switching SATA operation mode from RAID to AHCI to make drives visible without special drivers, though this may affect data integrity if an OS is already installed.
Frequently Asked Questions
Can I use Rufus to inject drivers automatically?
Rufus creates bootable media but does not natively inject storage drivers into the Windows image itself. While Rufus has options to disable signature checks or change partitions, it does not merge external driver files into the \Sources folder. You must use DISM or manual loading methods to add drivers.
What if the driver installation fails with an error code?
Error codes usually indicate mismatched architecture or unsigned drivers. Ensure the driver is for x64 architecture, not ARM or x86. If the driver is unsigned, you may need to disable Secure Boot temporarily or use the /ForceUnsigned flag in DISM, though this is not recommended for production systems due to security risks.
Does resetting Windows fix missing installation drivers?
No, resetting Windows applies to an existing operating system. If you cannot install Windows initially, resetting is impossible. See
Will resetting Windows 11 Solve directx problems? for information on post-installation fixes, which do not apply to the initial setup phase.
Why do I need to reload drivers after installation?
Drivers loaded via the "Load Driver" button during setup only exist in the temporary RAM disk of the Windows PE environment. They are not copied to the final C: drive unless explicitly integrated into the image via DISM or specified in an answer file. Therefore, you must install them again in the final OS.
Is there a risk of losing data when modifying the ISO?
Modifying the ISO files on your USB stick does not affect existing data on your computer’s hard drives. However, always back up important data before installing a new OS, as formatting partitions during installation will erase data regardless of driver issues.