KMDF version update fails

NTDEV
1

Hello,

I have this problem with the KMDF update:
We originally developed a USB driver using WDK 6801. The driver worked fine and we installed it on several machines.
Now, we upgraded to WDK 7100 and rebuilt the same driver. When we install it, it installs correctly but fails to load.

We found the root of the problem was that the KMDF framework was not updated on the machine - c:\windows\system32\drivers\wdf01000.sys shows version 6801!
This causes some of the driver’s init functions to fail, since the parameter structure’s lengths have changed from the previous version.

No matter what we do, we can’t get it to upgrade the KMDF version to 7100.
Installing on clean machines, on which we never installed the previous driver, works fine.

Is this a known issue or is there a way around this?

Thanks,
–Jonathan

2

What do the kmdf setup logs say?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: xxxxx@n-trig.com
Sent: Sunday, August 02, 2009 4:31 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] KMDF version update fails

Hello,

I have this problem with the KMDF update:
We originally developed a USB driver using WDK 6801. The driver worked fine and we installed it on several machines.
Now, we upgraded to WDK 7100 and rebuilt the same driver. When we install it, it installs correctly but fails to load.

We found the root of the problem was that the KMDF framework was not updated on the machine - c:\windows\system32\drivers\wdf01000.sys shows version 6801!
This causes some of the driver’s init functions to fail, since the parameter structure’s lengths have changed from the previous version.

No matter what we do, we can’t get it to upgrade the KMDF version to 7100.
Installing on clean machines, on which we never installed the previous driver, works fine.

Is this a known issue or is there a way around this?

Thanks,
–Jonathan

—
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

Hi Doron,

This is from setupact.log:
*******************************************************
WdfCoInstaller: [08/03/2009 01:16.24.454] DIF_INSTALLDEVICE: Pre-Processing

WdfCoInstaller: [08/03/2009 01:16.24.688] ReadComponents: WdfSection for Driver Service usbsamp using KMDF lib version Major 0x1, minor 0x9

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7100

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: KMDF in-memory version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.766] DIF_INSTALLDEVICE: KMDF on-disk version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.782] Service Wdf01000 is running

WdfCoInstaller: [08/03/2009 01:16.24.782] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller’s version.

WdfCoInstaller: [08/03/2009 01:16.24.829] DIF_INSTALLDEVICE: Update is required, because the on-disk KMDF version is older than the coinstaller

WdfCoInstaller: [08/03/2009 01:16.24.891] VerifyMSRoot: exit: error(0) The operation completed successfully.

WdfCoInstaller: [08/03/2009 01:16.25.031] Invoking “C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode Driver Framework Install-v1.9-Vista.msu” /quiet /norestart”.

WdfCoInstaller: [08/03/2009 01:16.48.837] The package was installed successfully: error(0) The operation completed successfully.
.

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: KMDF installed successfully

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: Reboot needed by windows update

WdfCoInstaller: [08/03/2009 01:16.49.617] DIF_INSTALLDEVICE: Post-Processing

*******************************************************

The DpInst log shows the driver installed successfully, and restart is required.
After restart, the KMDF version remains 6801.

BTW, the OS is Vista Ultimate.

Thanks,
–Jonathan

4

The coinstaller can’t update between versions of the framework with the same minor version, even if they are different. You can copy the new versions wdf01000.sys and wdfldr.sys onto the system yourself to update to the newest version.

You can get the new versions of the file by either:

  1. Installing 1.9 on a system that hasn’t seen any previous 1.9 installation OR
  2. Extracting the files from the coinstaller yourself, see http://blogs.msdn.com/bobkjelgaard/archive/2007/12/13/kmdf-1-7-and-the-server-2008-vista-sp1-rc1-wdk.aspx for details on how to do this.

If you are running on vista+, you will have to disable system file protection on the wdf files. The steps to do this:

  1. takeown /f
    2. icacls /grant :f

    Brandon

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
    Sent: Monday, August 03, 2009 1:32 AM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] KMDF version update fails

    Hi Doron,

    This is from setupact.log:

    WdfCoInstaller: [08/03/2009 01:16.24.454] DIF_INSTALLDEVICE: Pre-Processing

    WdfCoInstaller: [08/03/2009 01:16.24.688] ReadComponents: WdfSection for Driver Service usbsamp using KMDF lib version Major 0x1, minor 0x9

    WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7100

    WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: KMDF in-memory version: 1.9.6801

    WdfCoInstaller: [08/03/2009 01:16.24.766] DIF_INSTALLDEVICE: KMDF on-disk version: 1.9.6801

    WdfCoInstaller: [08/03/2009 01:16.24.782] Service Wdf01000 is running

    WdfCoInstaller: [08/03/2009 01:16.24.782] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller’s version.

    WdfCoInstaller: [08/03/2009 01:16.24.829] DIF_INSTALLDEVICE: Update is required, because the on-disk KMDF version is older than the coinstaller

    WdfCoInstaller: [08/03/2009 01:16.24.891] VerifyMSRoot: exit: error(0) The operation completed successfully.

    WdfCoInstaller: [08/03/2009 01:16.25.031] Invoking “C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode Driver Framework Install-v1.9-Vista.msu” /quiet /norestart”.

    WdfCoInstaller: [08/03/2009 01:16.48.837] The package was installed successfully: error(0) The operation completed successfully.
    .

    WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: KMDF installed successfully

    WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: Reboot needed by windows update

    WdfCoInstaller: [08/03/2009 01:16.49.617] DIF_INSTALLDEVICE: Post-Processing



    The DpInst log shows the driver installed successfully, and restart is required.
    After restart, the KMDF version remains 6801.

    BTW, the OS is Vista Ultimate.

    Thanks,
    –Jonathan

    —
    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

But I thought that was the promise of WDF! No more driver equivalent of DLL hell, etc., let Microsoft take care of it.

I have at least a number of OS installs where I had to wipe and start over because I could not get WDF updated (in this case, it was going from a beta to production, and I’m glad I didn’t have many beta sites).

IMHO, there should be NO instance where a standard install/upgrade should fail, and again, IMHO, not being able to do point upgrades is a serious failure.

Plus, the method you mention is doable for us, but it’s a customer support nightmare otherwise.

Am I the only one that thinks this is a problem?

G

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Brandon Wilson
Sent: August 03, 2009 10:46 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

The coinstaller can’t update between versions of the framework with the same minor version, even if they are different. You can copy the new versions wdf01000.sys and wdfldr.sys onto the system yourself to update to the newest version.

You can get the new versions of the file by either:

  1. Installing 1.9 on a system that hasn’t seen any previous 1.9 installation OR
  2. Extracting the files from the coinstaller yourself, see http://blogs.msdn.com/bobkjelgaard/archive/2007/12/13/kmdf-1-7-and-the-server-2008-vista-sp1-rc1-wdk.aspx for details on how to do this.

If you are running on vista+, you will have to disable system file protection on the wdf files. The steps to do this:

  1. takeown /f
    2. icacls /grant :f

    Brandon

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
    Sent: Monday, August 03, 2009 1:32 AM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] KMDF version update fails

    Hi Doron,

    This is from setupact.log:

    WdfCoInstaller: [08/03/2009 01:16.24.454] DIF_INSTALLDEVICE: Pre-Processing

    WdfCoInstaller: [08/03/2009 01:16.24.688] ReadComponents: WdfSection for Driver Service usbsamp using KMDF lib version Major 0x1, minor 0x9

    WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7100

    WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: KMDF in-memory version: 1.9.6801

    WdfCoInstaller: [08/03/2009 01:16.24.766] DIF_INSTALLDEVICE: KMDF on-disk version: 1.9.6801

    WdfCoInstaller: [08/03/2009 01:16.24.782] Service Wdf01000 is running

    WdfCoInstaller: [08/03/2009 01:16.24.782] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller’s version.

    WdfCoInstaller: [08/03/2009 01:16.24.829] DIF_INSTALLDEVICE: Update is required, because the on-disk KMDF version is older than the coinstaller

    WdfCoInstaller: [08/03/2009 01:16.24.891] VerifyMSRoot: exit: error(0) The operation completed successfully.

    WdfCoInstaller: [08/03/2009 01:16.25.031] Invoking “C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode Driver Framework Install-v1.9-Vista.msu” /quiet /norestart”.

    WdfCoInstaller: [08/03/2009 01:16.48.837] The package was installed successfully: error(0) The operation completed successfully.
    .

    WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: KMDF installed successfully

    WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: Reboot needed by windows update

    WdfCoInstaller: [08/03/2009 01:16.49.617] DIF_INSTALLDEVICE: Post-Processing



    The DpInst log shows the driver installed successfully, and restart is required.
    After restart, the KMDF version remains 6801.

    BTW, the OS is Vista Ultimate.

    Thanks,
    –Jonathan

    —
    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

Released to released upgrades work. Beta to released do not. Are you shipping a product with the beta kmdf bits?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: Gregory Havenga
Sent: Monday, August 03, 2009 10:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

But I thought that was the promise of WDF! No more driver equivalent of DLL hell, etc., let Microsoft take care of it.

I have at least a number of OS installs where I had to wipe and start over because I could not get WDF updated (in this case, it was going from a beta to production, and I’m glad I didn’t have many beta sites).

IMHO, there should be NO instance where a standard install/upgrade should fail, and again, IMHO, not being able to do point upgrades is a serious failure.

Plus, the method you mention is doable for us, but it’s a customer support nightmare otherwise.

Am I the only one that thinks this is a problem?

G

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Brandon Wilson
Sent: August 03, 2009 10:46 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

The coinstaller can’t update between versions of the framework with the same minor version, even if they are different. You can copy the new versions wdf01000.sys and wdfldr.sys onto the system yourself to update to the newest version.

You can get the new versions of the file by either:
1. Installing 1.9 on a system that hasn’t seen any previous 1.9 installation OR
2. Extracting the files from the coinstaller yourself, see http://blogs.msdn.com/bobkjelgaard/archive/2007/12/13/kmdf-1-7-and-the-server-2008-vista-sp1-rc1-wdk.aspx for details on how to do this.

If you are running on vista+, you will have to disable system file protection on the wdf files. The steps to do this:
1. takeown /f
2. icacls /grant :f

Brandon

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Monday, August 03, 2009 1:32 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] KMDF version update fails

Hi Doron,

This is from setupact.log:

WdfCoInstaller: [08/03/2009 01:16.24.454] DIF_INSTALLDEVICE: Pre-Processing

WdfCoInstaller: [08/03/2009 01:16.24.688] ReadComponents: WdfSection for Driver Service usbsamp using KMDF lib version Major 0x1, minor 0x9

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7100

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: KMDF in-memory version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.766] DIF_INSTALLDEVICE: KMDF on-disk version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.782] Service Wdf01000 is running

WdfCoInstaller: [08/03/2009 01:16.24.782] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller’s version.

WdfCoInstaller: [08/03/2009 01:16.24.829] DIF_INSTALLDEVICE: Update is required, because the on-disk KMDF version is older than the coinstaller

WdfCoInstaller: [08/03/2009 01:16.24.891] VerifyMSRoot: exit: error(0) The operation completed successfully.

WdfCoInstaller: [08/03/2009 01:16.25.031] Invoking “C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode Driver Framework Install-v1.9-Vista.msu” /quiet /norestart”.

WdfCoInstaller: [08/03/2009 01:16.48.837] The package was installed successfully: error(0) The operation completed successfully.
.

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: KMDF installed successfully

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: Reboot needed by windows update

WdfCoInstaller: [08/03/2009 01:16.49.617] DIF_INSTALLDEVICE: Post-Processing



The DpInst log shows the driver installed successfully, and restart is required.
After restart, the KMDF version remains 6801.

BTW, the OS is Vista Ultimate.

Thanks,
–Jonathan

—
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

—
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

7

Released to released upgrades work. Beta to released do not. Are you shipping a product with the beta kmdf bits?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: Gregory Havenga
Sent: Monday, August 03, 2009 10:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

But I thought that was the promise of WDF! No more driver equivalent of DLL hell, etc., let Microsoft take care of it.

I have at least a number of OS installs where I had to wipe and start over because I could not get WDF updated (in this case, it was going from a beta to production, and I’m glad I didn’t have many beta sites).

IMHO, there should be NO instance where a standard install/upgrade should fail, and again, IMHO, not being able to do point upgrades is a serious failure.

Plus, the method you mention is doable for us, but it’s a customer support nightmare otherwise.

Am I the only one that thinks this is a problem?

G

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Brandon Wilson
Sent: August 03, 2009 10:46 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

The coinstaller can’t update between versions of the framework with the same minor version, even if they are different. You can copy the new versions wdf01000.sys and wdfldr.sys onto the system yourself to update to the newest version.

You can get the new versions of the file by either:
1. Installing 1.9 on a system that hasn’t seen any previous 1.9 installation OR
2. Extracting the files from the coinstaller yourself, see http://blogs.msdn.com/bobkjelgaard/archive/2007/12/13/kmdf-1-7-and-the-server-2008-vista-sp1-rc1-wdk.aspx for details on how to do this.

If you are running on vista+, you will have to disable system file protection on the wdf files. The steps to do this:
1. takeown /f
2. icacls /grant :f

Brandon

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Monday, August 03, 2009 1:32 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] KMDF version update fails

Hi Doron,

This is from setupact.log:

WdfCoInstaller: [08/03/2009 01:16.24.454] DIF_INSTALLDEVICE: Pre-Processing

WdfCoInstaller: [08/03/2009 01:16.24.688] ReadComponents: WdfSection for Driver Service usbsamp using KMDF lib version Major 0x1, minor 0x9

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7100

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: KMDF in-memory version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.766] DIF_INSTALLDEVICE: KMDF on-disk version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.782] Service Wdf01000 is running

WdfCoInstaller: [08/03/2009 01:16.24.782] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller’s version.

WdfCoInstaller: [08/03/2009 01:16.24.829] DIF_INSTALLDEVICE: Update is required, because the on-disk KMDF version is older than the coinstaller

WdfCoInstaller: [08/03/2009 01:16.24.891] VerifyMSRoot: exit: error(0) The operation completed successfully.

WdfCoInstaller: [08/03/2009 01:16.25.031] Invoking “C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode Driver Framework Install-v1.9-Vista.msu” /quiet /norestart”.

WdfCoInstaller: [08/03/2009 01:16.48.837] The package was installed successfully: error(0) The operation completed successfully.
…

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: KMDF installed successfully

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: Reboot needed by windows update

WdfCoInstaller: [08/03/2009 01:16.49.617] DIF_INSTALLDEVICE: Post-Processing



The DpInst log shows the driver installed successfully, and restart is required.
After restart, the KMDF version remains 6801.

BTW, the OS is Vista Ultimate.

Thanks,
–Jonathan

—
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

—
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

8

Of course not - but I had to beta my stuff in a close group, and that was grief enough.

What I’m worried about is having the same thing happen between released versions.

G

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: August 03, 2009 10:58 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Released to released upgrades work. Beta to released do not. Are you shipping a product with the beta kmdf bits?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: Gregory Havenga
Sent: Monday, August 03, 2009 10:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

But I thought that was the promise of WDF! No more driver equivalent of DLL hell, etc., let Microsoft take care of it.

I have at least a number of OS installs where I had to wipe and start over because I could not get WDF updated (in this case, it was going from a beta to production, and I’m glad I didn’t have many beta sites).

IMHO, there should be NO instance where a standard install/upgrade should fail, and again, IMHO, not being able to do point upgrades is a serious failure.

Plus, the method you mention is doable for us, but it’s a customer support nightmare otherwise.

Am I the only one that thinks this is a problem?

G

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Brandon Wilson
Sent: August 03, 2009 10:46 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

The coinstaller can’t update between versions of the framework with the same minor version, even if they are different. You can copy the new versions wdf01000.sys and wdfldr.sys onto the system yourself to update to the newest version.

You can get the new versions of the file by either:
1. Installing 1.9 on a system that hasn’t seen any previous 1.9 installation OR
2. Extracting the files from the coinstaller yourself, see http://blogs.msdn.com/bobkjelgaard/archive/2007/12/13/kmdf-1-7-and-the-server-2008-vista-sp1-rc1-wdk.aspx for details on how to do this.

If you are running on vista+, you will have to disable system file protection on the wdf files. The steps to do this:
1. takeown /f
2. icacls /grant :f

Brandon

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Monday, August 03, 2009 1:32 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] KMDF version update fails

Hi Doron,

This is from setupact.log:

WdfCoInstaller: [08/03/2009 01:16.24.454] DIF_INSTALLDEVICE: Pre-Processing

WdfCoInstaller: [08/03/2009 01:16.24.688] ReadComponents: WdfSection for Driver Service usbsamp using KMDF lib version Major 0x1, minor 0x9

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7100

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: KMDF in-memory version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.766] DIF_INSTALLDEVICE: KMDF on-disk version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.782] Service Wdf01000 is running

WdfCoInstaller: [08/03/2009 01:16.24.782] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller’s version.

WdfCoInstaller: [08/03/2009 01:16.24.829] DIF_INSTALLDEVICE: Update is required, because the on-disk KMDF version is older than the coinstaller

WdfCoInstaller: [08/03/2009 01:16.24.891] VerifyMSRoot: exit: error(0) The operation completed successfully.

WdfCoInstaller: [08/03/2009 01:16.25.031] Invoking “C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode Driver Framework Install-v1.9-Vista.msu” /quiet /norestart”.

WdfCoInstaller: [08/03/2009 01:16.48.837] The package was installed successfully: error(0) The operation completed successfully.
.

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: KMDF installed successfully

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: Reboot needed by windows update

WdfCoInstaller: [08/03/2009 01:16.49.617] DIF_INSTALLDEVICE: Post-Processing



The DpInst log shows the driver installed successfully, and restart is required.
After restart, the KMDF version remains 6801.

BTW, the OS is Vista Ultimate.

Thanks,
–Jonathan

—
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

—
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

9

Like I said, upgrading from RTM v.cur to RTM v.cur+N is supported. No need to worry about that

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Gregory Havenga
Sent: Monday, August 03, 2009 11:03 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Of course not - but I had to beta my stuff in a close group, and that was grief enough.

What I’m worried about is having the same thing happen between released versions.

G

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: August 03, 2009 10:58 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Released to released upgrades work. Beta to released do not. Are you shipping a product with the beta kmdf bits?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: Gregory Havenga
Sent: Monday, August 03, 2009 10:53 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

But I thought that was the promise of WDF! No more driver equivalent of DLL hell, etc., let Microsoft take care of it.

I have at least a number of OS installs where I had to wipe and start over because I could not get WDF updated (in this case, it was going from a beta to production, and I’m glad I didn’t have many beta sites).

IMHO, there should be NO instance where a standard install/upgrade should fail, and again, IMHO, not being able to do point upgrades is a serious failure.

Plus, the method you mention is doable for us, but it’s a customer support nightmare otherwise.

Am I the only one that thinks this is a problem?

G

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Brandon Wilson
Sent: August 03, 2009 10:46 AM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

The coinstaller can’t update between versions of the framework with the same minor version, even if they are different. You can copy the new versions wdf01000.sys and wdfldr.sys onto the system yourself to update to the newest version.

You can get the new versions of the file by either:
1. Installing 1.9 on a system that hasn’t seen any previous 1.9 installation OR 2. Extracting the files from the coinstaller yourself, see http://blogs.msdn.com/bobkjelgaard/archive/2007/12/13/kmdf-1-7-and-the-server-2008-vista-sp1-rc1-wdk.aspx for details on how to do this.

If you are running on vista+, you will have to disable system file protection on the wdf files. The steps to do this:
1. takeown /f
2. icacls /grant :f

Brandon

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Monday, August 03, 2009 1:32 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] KMDF version update fails

Hi Doron,

This is from setupact.log:

WdfCoInstaller: [08/03/2009 01:16.24.454] DIF_INSTALLDEVICE: Pre-Processing

WdfCoInstaller: [08/03/2009 01:16.24.688] ReadComponents: WdfSection for Driver Service usbsamp using KMDF lib version Major 0x1, minor 0x9

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: Coinstaller version: 1.9.7100

WdfCoInstaller: [08/03/2009 01:16.24.735] DIF_INSTALLDEVICE: KMDF in-memory version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.766] DIF_INSTALLDEVICE: KMDF on-disk version: 1.9.6801

WdfCoInstaller: [08/03/2009 01:16.24.782] Service Wdf01000 is running

WdfCoInstaller: [08/03/2009 01:16.24.782] DIF_INSTALLDEVICE: Reboot is required, because the in-memory KMDF version is older than the coinstaller’s version.

WdfCoInstaller: [08/03/2009 01:16.24.829] DIF_INSTALLDEVICE: Update is required, because the on-disk KMDF version is older than the coinstaller

WdfCoInstaller: [08/03/2009 01:16.24.891] VerifyMSRoot: exit: error(0) The operation completed successfully.

WdfCoInstaller: [08/03/2009 01:16.25.031] Invoking “C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode Driver Framework Install-v1.9-Vista.msu” /quiet /norestart”.

WdfCoInstaller: [08/03/2009 01:16.48.837] The package was installed successfully: error(0) The operation completed successfully.
.

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: KMDF installed successfully

WdfCoInstaller: [08/03/2009 01:16.48.915] InstallComponents: Reboot needed by windows update

WdfCoInstaller: [08/03/2009 01:16.49.617] DIF_INSTALLDEVICE: Post-Processing



The DpInst log shows the driver installed successfully, and restart is required.
After restart, the KMDF version remains 6801.

BTW, the OS is Vista Ultimate.

Thanks,
–Jonathan

—
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

—
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

—
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

> Am I the only one that thinks this is a problem?

Most definitely not the only one.

And I too throw in my vote for “this seems a bit silly”.

The version information contains Major, Minor, Build, and QFE #s. You mean
to say that somewhere in all of that it was not possible for the coinstaller
to be able to handle going from a *beta* version (with a lower version rank)
to a release version (with a higher version rank) and to simply ensure that
but qfe#/build# reflects the promotion from ‘beta’ to ‘release’?

I don’t get the rational but I am sure somebody had one. Perhaps if the
core rational for this decision was explained it could illuminate us all.

Dave Cattley

11

Dave,
If you have beta KMDF 1.9 installed and you try to install RC KMDF 1.9, this will fail. However, if you try to install RTM KMDF 1.9, this should be successful (there is no contract for that so no future guarantees, but we’re trying to keep this scenario working and AFAIK it works). So, the non-RTM KMDF 1.9 builds cannot be used to update each other, however the RTM one overwrites all the non-RTM ones. The OP was trying to install a RC KMDF 1.9 on top of beta KMDF 1.9 (if I recall the version numbers correctly) and that’s why it was failing.

Does this make sense?

Ilias

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Monday, August 03, 2009 12:09 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Am I the only one that thinks this is a problem?

Most definitely not the only one.

And I too throw in my vote for “this seems a bit silly”.

The version information contains Major, Minor, Build, and QFE #s. You mean
to say that somewhere in all of that it was not possible for the coinstaller
to be able to handle going from a *beta* version (with a lower version rank)
to a release version (with a higher version rank) and to simply ensure that
but qfe#/build# reflects the promotion from ‘beta’ to ‘release’?

I don’t get the rational but I am sure somebody had one. Perhaps if the
core rational for this decision was explained it could illuminate us all.

Dave Cattley

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

12

Small clarification: By saying that something will “fail” I meant that the driver installation will continue as it should, but the framework will not be updated.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Ilias Tsigkogiannis
Sent: Monday, August 03, 2009 3:06 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Dave,
If you have beta KMDF 1.9 installed and you try to install RC KMDF 1.9, this will fail. However, if you try to install RTM KMDF 1.9, this should be successful (there is no contract for that so no future guarantees, but we’re trying to keep this scenario working and AFAIK it works). So, the non-RTM KMDF 1.9 builds cannot be used to update each other, however the RTM one overwrites all the non-RTM ones. The OP was trying to install a RC KMDF 1.9 on top of beta KMDF 1.9 (if I recall the version numbers correctly) and that’s why it was failing.

Does this make sense?

Ilias

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Monday, August 03, 2009 12:09 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Am I the only one that thinks this is a problem?

Most definitely not the only one.

And I too throw in my vote for “this seems a bit silly”.

The version information contains Major, Minor, Build, and QFE #s. You mean
to say that somewhere in all of that it was not possible for the coinstaller
to be able to handle going from a *beta* version (with a lower version rank)
to a release version (with a higher version rank) and to simply ensure that
but qfe#/build# reflects the promotion from ‘beta’ to ‘release’?

I don’t get the rational but I am sure somebody had one. Perhaps if the
core rational for this decision was explained it could illuminate us all.

Dave Cattley

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

13

Ilias,

Well that certainly sounds better. And yes, I have seen that I cannot get
the RC bits to update the Beta bits. That scenario is only a minor PITA
for me where I might have deployed beta bits for testing on a NT6 (or
earlier) system that has not yet exploded and been re-imaged.

Thanks for clarifying that.

As soon as I have RTM bits I guess I will see about the more important case.
And speaking of that… Do we get an RTM WDK any day soon?

Cheers,
Dave Cattley

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ilias Tsigkogiannis
Sent: Monday, August 03, 2009 6:12 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Small clarification: By saying that something will “fail” I meant that the
driver installation will continue as it should, but the framework will not
be updated.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ilias Tsigkogiannis
Sent: Monday, August 03, 2009 3:06 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Dave,
If you have beta KMDF 1.9 installed and you try to install RC KMDF 1.9, this
will fail. However, if you try to install RTM KMDF 1.9, this should be
successful (there is no contract for that so no future guarantees, but we’re
trying to keep this scenario working and AFAIK it works). So, the non-RTM
KMDF 1.9 builds cannot be used to update each other, however the RTM one
overwrites all the non-RTM ones. The OP was trying to install a RC KMDF 1.9
on top of beta KMDF 1.9 (if I recall the version numbers correctly) and
that’s why it was failing.

Does this make sense?

Ilias

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Monday, August 03, 2009 12:09 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Am I the only one that thinks this is a problem?

Most definitely not the only one.

And I too throw in my vote for “this seems a bit silly”.

The version information contains Major, Minor, Build, and QFE #s. You mean
to say that somewhere in all of that it was not possible for the coinstaller
to be able to handle going from a *beta* version (with a lower version rank)
to a release version (with a higher version rank) and to simply ensure that
but qfe#/build# reflects the promotion from ‘beta’ to ‘release’?

I don’t get the rational but I am sure somebody had one. Perhaps if the
core rational for this decision was explained it could illuminate us all.

Dave Cattley

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

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

14

Thanks Brandon and Ilias,

Your workaround solved my problem. I never would have thought of it.

Looking forward for the RTM WDK.

–Jonathan

15

No problem.
An easier workaround that you can use for testing purposes is to just uninstall the beta KMDF from the system (in Vista you have to go to Control Panel -> Programs and Features -> Installed Updates -> Search for Kernel-Mode Driver Framework). Be careful, because if you have installed any KMDF 1.9 drivers and you reboot the system, it will cause a blue screen (i.e. you’ll have to uninstall those drivers before uninstalling KMDF 1.9 beta). After you revert back to KMDF 1.7 (or whatever was there earlier), you can install your KMDF 1.9 RC driver without a problem.

Ilias

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Tuesday, August 04, 2009 1:39 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] KMDF version update fails

Thanks Brandon and Ilias,

Your workaround solved my problem. I never would have thought of it.

Looking forward for the RTM WDK.

–Jonathan

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

16

I think that the RTM WDK will be available before the end of this month. Possibly somebody from the WDK team might have more detailed information about it.

Ilias

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Monday, August 03, 2009 3:24 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Ilias,

Well that certainly sounds better. And yes, I have seen that I cannot get
the RC bits to update the Beta bits. That scenario is only a minor PITA
for me where I might have deployed beta bits for testing on a NT6 (or
earlier) system that has not yet exploded and been re-imaged.

Thanks for clarifying that.

As soon as I have RTM bits I guess I will see about the more important case.
And speaking of that… Do we get an RTM WDK any day soon?

Cheers,
Dave Cattley

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ilias Tsigkogiannis
Sent: Monday, August 03, 2009 6:12 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Small clarification: By saying that something will “fail” I meant that the
driver installation will continue as it should, but the framework will not
be updated.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ilias Tsigkogiannis
Sent: Monday, August 03, 2009 3:06 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Dave,
If you have beta KMDF 1.9 installed and you try to install RC KMDF 1.9, this
will fail. However, if you try to install RTM KMDF 1.9, this should be
successful (there is no contract for that so no future guarantees, but we’re
trying to keep this scenario working and AFAIK it works). So, the non-RTM
KMDF 1.9 builds cannot be used to update each other, however the RTM one
overwrites all the non-RTM ones. The OP was trying to install a RC KMDF 1.9
on top of beta KMDF 1.9 (if I recall the version numbers correctly) and
that’s why it was failing.

Does this make sense?

Ilias

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Monday, August 03, 2009 12:09 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:[ntdev] KMDF version update fails

Am I the only one that thinks this is a problem?

Most definitely not the only one.

And I too throw in my vote for “this seems a bit silly”.

The version information contains Major, Minor, Build, and QFE #s. You mean
to say that somewhere in all of that it was not possible for the coinstaller
to be able to handle going from a *beta* version (with a lower version rank)
to a release version (with a higher version rank) and to simply ensure that
but qfe#/build# reflects the promotion from ‘beta’ to ‘release’?

I don’t get the rational but I am sure somebody had one. Perhaps if the
core rational for this decision was explained it could illuminate us all.

Dave Cattley

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

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