Failure in WDF install when vxbda driver is already installed

Hi,
One of our customers reported an issue when installing my WDF function driver (Built using WinDDK 6000 - WDF 1.5) on a win2k3 X64 machine.
The SE that was present at the customer’s site, did some quick debugging and found the following error in setupact.log:
WdfCoInstaller: [01/28/2008 16:55.38.734] ArpEntryPresent: RegOpenKeyEx(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Wdf01005)

After he created the above key, the install was retried and succeeded.

I further checked the logs, and saw that apparently the customer has previously installed a driver named vxbda which is also a WDF driver. It appears that the install of vxbda somehow caused issue with our driver installation.

Does anyone have an idea as to what may be the problem?

Many thanks,
Eran.

Yes, the KMDF 1.5 coinstaller searched for the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Wdf01005 and if it was not there, then it thought that the KMDF installation was damaged (i.e. the file %windir%\system32\drivers\wdf01000.sys file is there and its version is 1.5, however the Registry key is missing), so it stopped the installation.

In the KMDF 1.7 we’ve changed the behavior. Now, the KMDF 1.7 coinstaller installs, if:
1)wdf01007_on_disk_version < coinstaller_version
OR
2)(wdf01007_on_disk_version == coinstaller_version) && (RegistryEntryMissing || Wdf01000ServiceCannotBeOpened)

So, in your case, the KMDF 1.7 coinstaller would install, because it would go to the 2nd case and it would find that RegistryEntryMissing == TRUE.

Generally, the KMDF 1.7 coinstaller (WinDDK 6001) has many bug fixes and if you migrate to it, then lots of your problems will disappear.

Ilias


From: xxxxx@lists.osr.com [xxxxx@lists.osr.com] On Behalf Of xxxxx@topio.com [xxxxx@topio.com]
Sent: Tuesday, January 29, 2008 6:48 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Failure in WDF install when vxbda driver is already installed

Hi,
One of our customers reported an issue when installing my WDF function driver (Built using WinDDK 6000 - WDF 1.5) on a win2k3 X64 machine.
The SE that was present at the customer’s site, did some quick debugging and found the following error in setupact.log:
WdfCoInstaller: [01/28/2008 16:55.38.734] ArpEntryPresent: RegOpenKeyEx(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Wdf01005)

After he created the above key, the install was retried and succeeded.

I further checked the logs, and saw that apparently the customer has previously installed a driver named vxbda which is also a WDF driver. It appears that the install of vxbda somehow caused issue with our driver installation.

Does anyone have an idea as to what may be the problem?

Many thanks,
Eran.


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

Thanks for the info,
Is 1.7 GAed yet? I thought that it is still in the Beta phase with WDK 6001.

Thanks,
Eran.

The 6001 WDK is in the RC phase, its release is near.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@topio.com
Sent: Tuesday, January 29, 2008 9:37 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Failure in WDF install when vxbda driver is already installed

Thanks for the info,
Is 1.7 GAed yet? I thought that it is still in the Beta phase with WDK 6001.

Thanks,
Eran.


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