Export (0) Print
Expand All
1 out of 1 rated this helpful - Rate this topic

DIFx Installation Guidelines

The DIFx tools support a wizard-install mode and a quiet-install mode. In wizard-install mode, the DIFx tools display all the wizard pages, user dialog boxes, and other user messages that the DIFx tools and Windows generate during an installation. However, in quiet-install mode, the DIFx tools do not display the user interface items that the DIFx tools and Windows generate. By default, the DIFx tools operate in wizard-install mode.

For more information about how to configure the DIFx tools in quiet-install mode, see the following topics:

The DIFx tools install WHQL-class or non-WHQL-class driver packages. A WHQL-class driver package is one that was digitally signed by Microsoft Windows Hardware Quality Labs (WHQL) or a Microsoft Authenticode signature. A non-WHQL-class driver package is one of the following:

  • A driver package that is intended for development and test. This driver package was digitally signed by the independent hardware vendor (IHV) by using a Microsoft Authenticode signature. For more information, see Signing Drivers during Development and Test.

  • A driver package that is intended for public release. This driver package was also digitally signed by the IHV by using a Microsoft Authenticode signature. For more information, see Signing Drivers for Public Release.

  • An unsigned driver package.

The INF file from each digitally-signed driver package must specify a catalog file, which contains the signature for the driver package. The DIFx tools do not support catalog files that contain signatures for more than one driver package.

For general information about driver signing, see Driver Signing.

The DIFx tools can also be configured to install unsigned driver packages or driver packages with missing files in legacy mode. For information about how to configure the DIFx tools in legacy mode, see the following topics:

Additional installation guidelines depend on the Windows version, the driver type, the installation mode, whether a driver is signed, and the signature type. These guidelines are described in the following topics:

Installation Guidelines (Windows Vista and Later)

Installation Guidelines (Windows Server 2003)

Installation Guidelines (Windows XP and Windows 2000)

Note   By default, before a DIFx tool preinstalls a signed driver package in the driver store, it verifies that a required signature is valid and that the signature's certificate is installed in the trusted publisher certificates store. This verification ensures that when a DIFx tool calls Windows to install a driver package, an installation should not fail because a signature is invalid or because the certificate is not installed in the trusted publisher certificates store. If this type of installation failure occurs, it indicates that the driver package, the signature, or the certificate changed after the DIFx tool copied the driver package to the driver store. For more information about why an installation failed, see the log file that is produced by the DIFx tool.

 

 

Send comments about this topic to Microsoft

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.