Driver Injection
Injecting drivers for devices
Driver injection is not required for the deployments to work. Driver injection happens during the deployPE process. The wizard searches the Drivers folder on the iiDeploy Extra USB partition for matching hardware drivers and injects them into the image. This partition is created during the flash USB process.
Recommended approach
On modern versions of Windows (Windows 10 and later), Windows Update pulls most drivers reliably. However, Windows Update may not always provide the latest manufacturer-specific drivers. We recommend using manufacturer update tools during the post-deploy software install process to keep drivers up to date. Offline injection is a fallback for edge cases.
When to use offline injection
- Deployment is failing to boot
- Hardware-specific issues after imaging
- You want faster first-boot Windows Update
How to set it up
Plug in the USB, open This PC in file explorer, locate the iiDeploy Extra partition, and navigate to the Drivers folder. Dump all the drivers for the models you plan to image into this folder. The wizard scans subfolders automatically and matches drivers to each machine during deployment. No naming convention is required, but naming folders by model (e.g., dell-3420) keeps things organized.
Driver pack sources
| Manufacturer | Driver pack catalog |
|---|---|
| Dell | Dell Driver Pack Catalog |
| HP | HP Driverpack Matrix |
| Lenovo | Lenovo Catalog |
For other manufacturers, search "[manufacturer] driver pack" or email us at support@iideploy.com any help. If no driver pack is available, download individual drivers and extract them to the Drivers folder using 7Zip.
Preparing drivers
Driver packs may come as .exe or .cab files. You must extract these with 7zip into the Drivers folder so the wizard can inject the drivers properly.
Support
For any issues, email support@iideploy.com.