How to Set the Driver Signing Policy for Windows 2000 Unattended Setup

This article was previously published under Q236029
This article has been archived. It is offered "as is" and will no longer be updated.
Driver signing is the process of checking the signature of the driver to determine if it has been signed as a known-good driver indicating it has been tested with Windows 2000. This can help provide greater system stability because a poorly written third-party driver can degrade system performance. Driver signing has three modes:
  • Ignore
  • Warn
  • Block
During Setup, this policy is set to warn. Under certain circumstances, you may want to alter this setting for use in unattended Setup. This article describes how to do so.
Using unattended Setup, you can set the mode of driver signing to what is desired for the client. For example, this may be useful if your deployment is utilizing a vendor-supplied driver that has not been signed. To configure unattended Setup to not generate a warning about an unsigned file, add the following entry to the [Unattended] section
DriverSigningPolicy = policy setting
where policy setting is one of the following settings:
  • Ignore
  • Warn
  • Block
WARNING: Setting this policy setting to "ignore" disables any warnings from driver signing about unsigned vendor-supplied drivers.

Article ID: 236029 - Last Review: 12/05/2015 15:05:22 - Revision: 3.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbinfo KB236029
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)