Device driver fails to load after Windows setup completes on Windows Server 2012

Symptoms

Consider the following scenario:

  • Windows Server 2012 setup is initiated from install media
  • An out-of-box 3rd party (OEM) driver is made available to Windows setup via $WinPEDriver$ folder

When Windows setup completes, the device driver made available via $WinPEDriver$ folder is not installed and the associated device is displayed with a yellow exclamation point in Device Manager. Additionally, a temporary hang lasting 5 - 10 minutes may be observed during the 'Installing devices' phase of Windows setup.

Cause

The out-of-box 3rd party driver triggers a driver signature check and this check relies on the cryptography service. As the cryptography service is started, a consistency check is performed between the system catalogs and the system CatDB. A mismatch results in a full rebuild of the CatDB. The rebuild process may take more than 5 minutes and this exceeds the device driver installation timeout.

Resolution

Reinstall the device driver after Windows setup has completed. The driver can be installed manually, or a scripting option can be used with a utility like DevCon.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff544707(v=vs.85).aspx

More Information

A review of the setupapi.setup log, found in the \Windows\Inf directory, will show that a timeout occurred during the installation of the driver.

0x000005b4 (ERROR_TIMEOUT)

     flq:                {_commit_copyfile}
     flq:                     {SPFILENOTIFY_STARTCOPY}
     ndv:                          Saving LastKnownGood file C:\Windows\system32\DRIVERS\<driver>.sys (copy)
     flq:                     {SPFILENOTIFY_STARTCOPY - exit(0x00000001)}
     flq:                     Copying 'C:\Windows\System32\DriverStore\FileRepository\<driver>.inf_amd64_e0b841ef66494924\<driver>.sys' to 'C:\Windows\system32\DRIVERS\<driver>.sys'.
     flq:                     CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\<driver>.inf_amd64_e0b841ef66494924\<driver>.sys'
     flq:                           to: 'C:\Windows\system32\DRIVERS\SETC989.tmp'
     cpy:                     CopyFile Drp is active
     ump:                     Server install process exited with code 0x000005b4 11:54:36.347
<<<  Section end 2012/12/10 11:54:36.347
<<<  [Exit status: FAILURE(0x000005b4)]
Properties

Article ID: 2862010 - Last Review: Jun 24, 2013 - Revision: 1

Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Standard, Windows Server 2012 Standard, Windows Server 2012 Standard, Windows Server 2012 Standard

Feedback