Different options to enable Windows Device Driver Installation Logs
Option1: Enable setupapi.dev.log
In Windows 7 the log level is set in the registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\LogLevel. The key may not exits and you may have to create it. The default on my computer turned out to be 0x2000ff00, which means maximal logging is achieved.
On Windows 7, the file is C:\Windows\inf\setupapi.dev.log which can look like this when an successful driver is installed. The helpful information here is mostly which parts of the INF file were read and interpreted, and what was actually installed.
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 23:23:08.208
ndv: Device install status=0x00000000
ndv: Performing device install final cleanup...
ndv: {Core Device Install - exit(0x00000000)} 23:23:08.208
ump: Server install process exited with code 0x00000000 23:23:08.224
ump: {Plug and Play Service: Device Install exit(00000000)}
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 23:23:08.239
dvi: No class installer for 'Xillybus driver for generic FPGA interface'
dvi: No CoInstallers found
dvi: Default installer: Enter 23:23:08.239
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 23:23:08.239
ndv: {Update Driver Software Wizard exit(00000000)}
<<< Section end 2012/02/08 23:23:11.281
<<< [Exit status: SUCCESS
When an unknown PCI device is detected by the system:
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this device.
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 20:55:17.716
ndv: {Core Device Install} 20:55:17.716
! ndv: Installing NULL driver!
dvi: Set selected driver complete.
dvi: {DIF_ALLOW_INSTALL} 20:55:17.716
dvi: No class installer for 'PCI Device'
dvi: Default installer: Enter 20:55:17.716
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 20:55:17.716
dvi: {DIF_INSTALLDEVICE} 20:55:17.716
dvi: No class installer for 'PCI Device'
dvi: Default installer: Enter 20:55:17.716
! dvi: Installing NULL driver!
dvi: Writing common driver property settings.
dvi: {Restarting Devices} 20:55:17.736
dvi: Restart: PCI\VEN_10EE&DEV_EBEB&SUBSYS_EBEB10EE&REV_00\4&27574D66&0&0008
dvi: Restart complete.
dvi: {Restarting Devices exit} 20:55:17.906
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 20:55:17.906
ndv: Device install status=0xe0000203
ndv: Performing device install final cleanup...
! ndv: Queueing up error report since device installation failed...
ndv: {Core Device Install - exit(0xe0000203)} 20:55:17.906
ump: Server install process exited with code 0xe0000203 20:55:17.916
<<< Section end 2012/02/08 20:55:17.916
<<< [Exit status: FAILURE(0xe0000203)]
Need More details, refer here - http://msdn.microsoft.com/en-us/library/gg675585(v=winembedded.60).aspx
---------------------
Option 2: If a driver is installer using Driver Package Installer (DPInst)
Some drivers use DPInst package to install the windows driver. You can find the corresponding logs here DPInst logs high-level installation information and error messages in a log file (%SystemRoot%\DPINST.LOG). The DPInst log file is a plain-text file that you can use to troubleshoot DPInst driver installation.
Read more here http://msdn.microsoft.com/en-us/library/windows/hardware/ff544842(v=vs.85).aspx
Option # 3: Intel driver installation logs
By default all Intel devices driver installation logging is stored at C:\Intel\Logs.
This is very useful if you are looking at install issues related to Intel Graphics, USB andIntel wifi driver install issues.
No comments:
Post a Comment