> Hi Maxim, Thanks for raising this. We’re not aware of any known issues like this. What OS version
is this seen on?
The issue is also described here (it seems to be widely known and not only for our company):
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/appcrash-shortly-after-start-updriver-installation/b1335fab-05b9-457f-bc7d-19a95b55dd9c
and here:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/326726df-e33e-424a-a59b-1bb0b56ab898/windows-2008-r2-will-not-install-any-drivers?forum=winservergen
So, several Windows versions are vulnerable.
Based on the STATUS_DLL_INIT_FAILED error, this seems like there is something pretty
fundamentally wrong with some Windows system files while loading DRVINST.EXE and its DLL
dependencies.
I also think so.
Store or registry/database entries (a DLL initialization error would likely happen before anything
there is even touched) so I don’t think it’s necessary to repair those.
Yes, good point.
Can you send a snippet of the log entry that shows the failure?
For now, I can only send the one from the above pages, not our own. I’m in the process of communicating with the guys to get our own log file.
The log below is from the person who claims it can occur during just plain in-place upgrade of Windows:
dvi: {Plug and Play Service: Device Install for STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT1}
ump: Creating Install Process: DrvInst.exe 16:57:03.512
ump: Server install process exited with code 0xc0000142 16:57:03.528
ump: {Plug and Play Service: Device Install exit(c0000142)}
ndv: Device Install failed for new device…installing NULL driver.
dvi: {Plug and Play Service: Device Install for STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT1}
ump: Creating Install Process: DrvInst.exe 16:57:03.528
ump: Server install process exited with code 0xc0000142 16:57:03.528
ump: {Plug and Play Service: Device Install exit(c0000142)}
ndv: {Update Driver Software Wizard exit(c0000142)}
<<< Section end 2012/01/30 16:57:13.358
Now from the second URL:
Problem Event Name: APPCRASH
Application Name: DrvInst.exe
Application Version: 6.0.6002.18005
Application Timestamp: 49e023db
Fault Module Name: USER32.dll
Fault Module Version: 6.0.6002.18005
Fault Module Timestamp: 49e0421d
Exception Code: c0000142
So, it looks like the init code of USER32.DLL has failed.
If you have access to some machine where this is happening, is it possible to run a binary
dependency walker tool like DEPENDS.EXE against DRVINST.EXE and see if everything looks OK
Yes, good idea.
–
Maxim S. Shatskih
Microsoft MVP on File System And Storage
xxxxx@storagecraft.com
http://www.storagecraft.com