WDK7 bug--Could not install driver in Vista

NTDEV
1

Hello all,

I met a problem here. My driver codes built with WDK7 could not be installed in Windows Vista unless the system is rebooted. Whereas, the driver built with WDK6 could be installed successfully without reboot problem.

Thanks in advance!

Joseph

2

What’s type of your driver?
In my opinion, it’s more about pnp manager, not WDK version.

Hello all,
I met a problem here. My driver codes built with WDK7 could not be installed in Windows Vista unless the system is rebooted. Whereas, the driver built with WDK6 could be installed successfully without reboot problem.
Thanks in advance!
Joseph

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

Perhaps due to different kmdf versions?

On Aug 22, 2010 9:45 PM, wrote:
> Hello all,
>
> I met a problem here. My driver codes built with WDK7 could not be
installed in Windows Vista unless the system is rebooted. Whereas, the
driver built with WDK6 could be installed successfully without reboot
problem.
>
> Thanks in advance!
>
> Joseph
>
> —
> 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

4

Is it a KMDF driver? What build window (ie target OS) did you build your driver in?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of luming419@163.com
Sent: Sunday, August 22, 2010 6:47 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDK7 bug–Could not install driver in Vista

Hello all,

I met a problem here. My driver codes built with WDK7 could not be installed in Windows Vista unless the system is rebooted. Whereas, the driver built with WDK6 could be installed successfully without reboot problem.

Thanks in advance!

Joseph

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

5

He’s running on Vista (1.05 or 1.07) but built with the Win7 WDK. He needs
to install the 1.09 version of WDF.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Sunday, August 22, 2010 9:46 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WDK7 bug–Could not install driver in Vista

Is it a KMDF driver? What build window (ie target OS) did you build your
driver in?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of luming419@163.com
Sent: Sunday, August 22, 2010 6:47 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDK7 bug–Could not install driver in Vista

Hello all,

I met a problem here. My driver codes built with WDK7 could not be installed
in Windows Vista unless the system is rebooted. Whereas, the driver built
with WDK6 could be installed successfully without reboot problem.

Thanks in advance!

Joseph

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

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

6

How about looking into the installer log files and finding out why a
boot was done *BEFORE* making unproven claims about bugs?

http://catb.org/esr/faqs/smart-questions.html

7

Use the Vista build env in WDK7

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntdev…
> Hello all,
>
> I met a problem here. My driver codes built with WDK7 could not be installed in Windows Vista unless the system is rebooted. Whereas, the driver built with WDK6 could be installed successfully without reboot problem.
>
> Thanks in advance!
>
> Joseph
>

8

I’ve run into this and every time it’s because it needed to update the WDF version.

Look into windows\info\setupapi.dev.log and see if it’s complaining about WDF versions and needing to reboot. It should say something about the version on disk vs. what’s in memory, don’t recall the exact wording.

9

I had no luck with that, Max. The current drivers I have work on both Vista
and Win7, and I build all of them with the latest Win7 WDK, and in their
appropriate build environment. I still had to install 1.09 when I first
installed the driver on Vista.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Monday, August 23, 2010 8:10 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WDK7 bug–Could not install driver in Vista

Use the Vista build env in WDK7

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntdev…
> Hello all,
>
> I met a problem here. My driver codes built with WDK7 could not be
installed in Windows Vista unless the system is rebooted. Whereas, the
driver built with WDK6 could be installed successfully without reboot
problem.
>
> Thanks in advance!
>
> Joseph
>

—
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

10

Thank all for your help. The cause of this bug has been found. I have got some information from
a Microsoft file -"WDFVersioning.doc". Below are some fragment of it.

At installation, a new minor release overwrites the older existing minor release. Thus a system can have at most one minor release of each major release at any one time. UMDF supports rollback to an earlier minor version through the Add or Remove Programs application in Control Panel. The KMDF co installer does not currently support rollback.
Example 1: Framework version 1.4 is present on the system. The user installs a driver that is packaged with the co installer for framework version 1.2. Because the existing minor version is more recent, the co installer does not install the framework and the new driver is linked to framework version 1.4.
Example 2: Framework version 1.4 is present on the system. The user installs a driver that is packaged with the co installer for framework version 1.5. Because the existing framework is older than the one in the driver package, the co installer installs version 1.5 and both the new driver and all existing drivers that require major version 1 are linked to version 1.5.
? For KMDF, if version 1.4 is already loaded in memory when the user installs the new driver, the user must reboot the system so that the existing drivers can relink against version 1.5.
? For UMDF, if existing devices are already using version 1.4, the co installer temporarily stops all of the UMDF devices on the system, installs version 1.5, and then restarts all the devices. If a driver for any of the devices vetoes the query-stop request, the co installer prompts the user to reboot the system.
Version 1.4 is deleted from the system.

According to the file, Edward Averill is right. Thanks much. I think the way to read the error log is quite a shortcut.

Joseph

11

But I haven’t found some clue like Edward Averill said “something about the version on
disk vs. what’s in memory” in the setupapi.dev.log. Could you please show me some more comments on it? Thanks much.

Joseph