Hardware Dev Center

Known DPInst Bugs and Limitations

DPInst has the following known bugs and limitations:

Slow signature checking on Windows 2000

On Microsoft Windows 2000, depending on how a driver package was signed, verifying a signature can be slow. To speed up signature verification, install the Windows 2000 update that is described in Knowledge Base article 329433.

While a signature is being verified, DPInst displays a user dialog box that informs the user that the signature is being verified by Windows 2000.

Note  This problem does not exist on Windows XP and later versions of Windows.
Supports only a single distribution disc

If you distribute an installation package on a distribution disc such as a CD, all of the source files for the installation package must be contained on only one distribution disc. DPInst does not prompt users to insert distribution discs to locate source files.

Always creates the initial dialog in the upper-left corner of the screen

DPInst always creates the initial installation dialog in the upper-left corner of the screen. DPInst does not provide a mechanism to change the initial position of the dialog.

Unidentified Publisher dialog on Windows Vista and later versions of Windows

In Windows Vista and later versions of Windows, running DPInst.exe will cause a warning dialog box to be displayed that states that DPInst.exe is from an unidentified publisher. Microsoft intentionally did not digitally sign DPInst.exe because it is intended to be redistributed as part of your driver installation package. To avoid this dialog, digitally sign DPInst.exe using your own code signing certificate.

For more information about code signing, see the following websites:

Introduction to Code Signing

Code Signing Best Practices

/q command line option suppresses notice of installation failure

The /q command line switch (quiet install) suppresses the display of wizard pages, user dialog boxes, and other user messages that DPInst and Windows generate. This includes anything that would notify a user of an installation failure. The status of a quiet installation can be determined from the DPInst return code.

You can also determine the status of a quiet installation by examining the DPInst installation log, which can be found at %SystemRoot%\dpinst.log. If DPInst.exe is called at a command prompt, the /c command line switch will cause DPInst to display the text of the log messages in the Command Prompt window.



Send comments about this topic to Microsoft

© 2015 Microsoft