This topic contains information about common causes for failures when you attempt to add driver packages to a server or boot image.
Failures when adding packages to a server
Common causes for failed packages in this scenario include the following:
- A corrupt package or a package that is
missing files.
- A network connectivity issue.
- An unsigned x64-based driver package
(x64-based driver packages must be signed).
- An .inf file that is not authored
correctly.
If you are adding driver packages using the MMC snap-in, then to view details about the package, double-click it from the list of failed packages. If you are adding driver packages using WDSUTIL /Add-AllDriverPackages and one or more packages could not be added, then a list of the failed packages will be printed in the console. To see a more detailed error message for one of the packages, try to add it individually using WDSUTIL (for example, WDSUTIL /verbose /Add-DriverPackage /InfFile:"C:\Temp\Display.inf").
If you cannot resolve the issue, contact the manufacturer of the package to obtain a new package and try the operation again.
Failures when adding packages to a boot image
Common causes for failed packages in this scenario include the following:
- Adding a package that does not match the
architecture of the image.
- Adding a driver package to an unsupported
image (for example, an install image).
- Adding a package to an older boot image. You
can only add packages to boot images that are based on Windows 7
and Windows Server 2008 R2.