This document was formerly KB article 3469.
Description
If the WinPE image used for OS Deployment does not already contain a driver for certain hardware such as the network adapter or the SATA, SCSI, or IDE controller, a driver will have to be added to the WinPE image.
Before adding any storage drivers (SATA, SCSI, etc.) it is recommended that the following article also be consulted. The changes identified in the following article should be made prior to injecting drivers into WinPE: The specified document was not found.
Problems that are seen with both PXE and Vboot
- Blank boot menu. If the network adapter driver is not available in the WinPE image, the boot menu will be blank and a mini-scan will never be sent to the core server.
- After booting, the background screen appears and the device hangs loading network settings.This can be a problem with the network driver or an IRQ conflict with the network card and some other device. Update the network card driver and/or the driver of the conflicting device. In some instances this device was the video card and the correct video card driver resolved this issue.
- WinPE pops up an error "You must have administrator privileges" when a SATA controller driver is not detected.
Problems seen only during a PXE Boot
- The script completes successfully but an image is not actually captured.
If the SATA, SCSI, or IDE controller driver does not exist in the WinPE image, the disk will not be visible. This can be seen by opening a opening a command prompt and running the following commands:
diskpart
list disk When PXE booting, a missing SATA, SCSI, or IDE controller driver will cause a script to process without capturing an image, however the task will still have a successful result.
Problems seen only during a Vboot
- After rebooting, the computer attempts to boot off the ldvpe1.img file but once WinPE is loading, the ramdisk will fail to create with the following error:
Failed to create RAM disk
Cannot find ldvpe1.img
A missing SATA, SCSI, or IDE controller driver prevents a vbooted machine from finding the ldvpe1.img after loading. This also prevents the partition table from being set back to normal and the machine will enter a boot loop, where it continues to try to boot to WinPE and fails.
Resolution
Additional information about the WinPE version and required driver versions for each version of LANDesk Management Suite can be found at WinPE Version Information by LANDesk Management Suite Version
LDMS 9.5
Please see the following article :How to Add Drivers to WinPE for LANDesk 9.5
LDMS 9
Please see the following article : How to add drivers to WinPE for LANDesk 9
LDMS 8.8
To add a driver to WinPE on LDMS 8.7 SP3, please follow the steps below.
As of 8.7 SP3, the LDMS Console wizard has been updated to be a driver management wizard, rather than just a wizard to add drivers. Through this wizard both SATA/SCSI/RAID and NIC drivers can be added and removed.
To launch the wizard, go to Tools | Distribution | OS Deployment in the console.
Click the Add Driver icon shown below.
![]()
Browse to the location of the PE Image to be modified. By default, the wizard points to: \\CORE\ldmain\landesk\vboot\ldvpe1.img.
![]()
Next, view the list of drivers to ensure the driver to be injected is not already injected. If not, click Add.
![]()
Note: If an added driver fails, it may be necessary to remove a similar driver that already exists. For example, if you are adding a driver that is an update to the 3Com Etherlink 10/100 PCI, remove the existing one first.
Select whether the driver is for a SATA drive or NIC drive. For a NIC card, choose the Other Driver option.
![]()
Browse to the required files. This will include the .inf, the .sys, and any additional files such as a .cat, .dll, or .exe that are included in the driver.
![]()
Choose the additional space to be added to the WinPE image.
![]()
If the image is successfully updated, the following message will appear.
![]()
Verify that the driver has been injected by manually inspecting the driver list. Then, click Finish.
![]()
Once the image has been updated, it needs to be delivered to the PXE representatives. To do this, either re-deploy the PXE representative, or see the following article: The specified document was not found.