CoInstaller not installing

NTDEV
1

All:

I have this driver/custom USB device. Actually there are two devices, each with their own driver. We sell these devices commercially. We have had probably over 500 installs that have happened without a glitch. Every CD that goes to a user is constructed in the same way.

But now I have this one customer for whom the install is not working correctly. For either device. The New Hardware Wizard is coming back with the error “Fatal Error During Installation”.

A look at the setupapi.log file indicates that the problem is installing the WDK CoInstaller. The driver is created using WDK 6000. WdfCoInstaller = 1.005.

I did a web search on the error and found a suggestion that if you delete wdf01000.sys, one can overcome the error. I deleted this, reboot, and tried the install, and everything worked fine. I then tried the sister device mentioned above and got the same error installing the coinstaller. Again, I deleted wdf01000.sys, reboot, and tried the install, and again, there was success.

Looking at the setupapi.log file, the only difference between the two installs is that in the failed install gives a line that says Coinstaller 1 of 1 failed. The successful install reads “doing full install of USB\VIDXXX&PIDXXX”.

Any suggestions?

Rick

2

Obviously deleting WDF0100.sys is a very very bad idea. What OS is this on? Also, v1.5 is now 2 versions old. Many changes/updates have been made to the coinstallers to make them more robust, please try to use v1.9 if you can.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gnotometrics.com
Sent: Monday, September 20, 2010 9:55 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] CoInstaller not installing

All:

I have this driver/custom USB device. Actually there are two devices, each with their own driver. We sell these devices commercially. We have had probably over 500 installs that have happened without a glitch. Every CD that goes to a user is constructed in the same way.

But now I have this one customer for whom the install is not working correctly. For either device. The New Hardware Wizard is coming back with the error “Fatal Error During Installation”.

A look at the setupapi.log file indicates that the problem is installing the WDK CoInstaller. The driver is created using WDK 6000. WdfCoInstaller = 1.005.

I did a web search on the error and found a suggestion that if you delete wdf01000.sys, one can overcome the error. I deleted this, reboot, and tried the install, and everything worked fine. I then tried the sister device mentioned above and got the same error installing the coinstaller. Again, I deleted wdf01000.sys, reboot, and tried the install, and again, there was success.

Looking at the setupapi.log file, the only difference between the two installs is that in the failed install gives a line that says Coinstaller 1 of 1 failed. The successful install reads “doing full install of USB\VIDXXX&PIDXXX”.

Any suggestions?

Rick

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

xxxxx@gnotometrics.com wrote:

I did a web search on the error and found a suggestion that if you delete wdf01000.sys, one can overcome the error. I deleted this, reboot, and tried the install, and everything worked fine. I then tried the sister device mentioned above and got the same error installing the coinstaller. Again, I deleted wdf01000.sys, reboot, and tried the install, and again, there was success.

Is this a machine that belongs to a “power user”? There were issues
like this when people had installed a driver based on one of the beta
releases of KMDF. The co-installer doesn’t recognize that the version
is different.

Removing wdf01000.sys is not necessarily enough. The co-installer
contains the sys file embedded as a resource. If the old co-installer
is still there, it will load up the old sys file. You might try
removing the co-installer (\windows\system32\wdfcoinstaller01005.dll).
If you can get your co-installer in there, then it should unpack the
right sys file.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

4

Ah yes… I knew I forgot something. This is running XP SP3. I am fortunate enough to have the offending system set up at my desk. My company shipped them a ‘loaner’ system.

Rick