Skip to main content
Installation of Non-WHQL-Class Driver Packages

The following sections describe considerations that apply when you install non-WHQL-class driver packages on Windows Vista and later versions of Windows:

Wizard Installation of Authenticode-Signed Non-WHQL-Class Driver Packages

Wizard Installation of Unsigned Non-WHQL-Class Driver Packages

Quiet Installation of Authenticode-Signed Non-WHQL-Class Driver Packages

The DIFx tools do not support a quiet installation of unsigned non-WHQL-class driver packages.

Wizard Installation of Authenticode-Signed Non-WHQL-Class Driver Packages

By default, the DIFx tools perform a wizard installation of non-WHQL-class driver packages that have an Authenticode signature. Starting with Windows Vista, the following considerations apply:

  • If the Authenticode signature is valid and the signature's certificate is installed in the per computer (localMachine) Trusted Publishers certificate store, Windows does not display driver signing dialog boxes.

    Note  The localMachine certificate store refers to the certificate store for the local computer that is stored in the system registry under HKEY_LOCAL_MACHINE. This certificate store differs from the per user (currentUser) certificate store that is stored in the system registry under HKEY_CURRENT_USER.

    For more information about certificate store locations, see CertMgr.

  • If the Authenticode signature is valid, but the signature's certificate is not installed in the localMachine Trusted Publishers certificate store, Windows displays a Windows Security dialog box such as the one in the following screen shot.

    Screen shot of the Windows Security dialog box for signed non-WHQL-class driver packages

    If a user selects the Always trust software from check box, Windows will later trust software that is signed by the signature's certificate and will not display the Windows Security dialog box again for software that is signed by the certificate.

  • If the Authenticode signature is not valid, Windows displays a Windows Security dialog box such as the one in the following screen shot.

    Screen shot of the Windows Security dialog box for unsigned non-WHQL-class driver packages

In addition to displaying security dialog boxes, the following is also true for wizard installation of Authenticode-signed non-WHQL-class driver packages on Windows Vista and later versions of Windows:

  • Windows notifies a user by displaying a dialog box if a user must restart the operating system to complete the installation.

  • If a driver package has missing files, the installation will fail.

Wizard Installation of Unsigned Non-WHQL-Class Driver Packages

Starting with Windows Vista, the DIFx tools will perform a wizard installation of unsigned non-WQHL-class driver packages. The following considerations apply:

  • Windows displays a Windows Security warning dialog box such as the one in the following screen shot.

    Screen shot of the Windows Security dialog box for unsigned non-WHQL-class driver packages
  • Windows notifies a user if an operating system restart is required to complete the installation.

  • If a driver package has missing files, the installation will fail.

Quiet Installation of Authenticode-Signed Non-WHQL-Class Driver Packages

By default, the DIFx tools perform a quiet installation for a non-WHQL-class driver package only if the package has a valid Authenticode signature. The following considerations apply:

  • If the signature is not valid, the DIFx tools and Windows do not display user dialog boxes and the installation will fail.

  • If the certificate that was used to sign the driver package is not installed in the user's certificate stores before the installation, the installation will fail.

  • If the driver package has missing files, the installation will fail.

  • Windows typically notifies a user if an operating system restart is necessary to complete an installation. In a quiet installation, if an operating system restart is necessary, this notification is suppressed. However, a required operating system restart does not cause the installation to fail. The DPInst return value or the value of the NeedReboot parameter that the DriverPackageInstall function returns indicates whether an operating system restart is required.

 

 

Send comments about this topic to Microsoft