Ilias,
In all cases the Wdf01000.sys and wdfLdr.sys files remain at 1.5.6000. The
files in the device properties dialog indicate that WdfCoInstaller01007.dll
is being used alongwith the driver.
Here’s the setupact file diff
WdfCoInstaller: [02/22/2008 13:14.13.564] DIF_INSTALLDEVICE: Pre-Processing
WdfCoInstaller: [02/22/2008 13:14.13.829] ReadComponents: WdfSection for
Driver Service HealthMonitorUsbDrv using KMDF lib version Major 0x1, minor
0x7
WdfCoInstaller: [02/22/2008 13:14.13.861] DIF_INSTALLDEVICE: Coinstaller
version: 1.7.6001
WdfCoInstaller: [02/22/2008 13:14.13.907] GetInMemoryVersionUlong: No
information about in-memory KMDF version
WdfCoInstaller: [02/22/2008 13:14.13.939] DIF_INSTALLDEVICE: KMDF in-memory
version: 0.0.0
WdfCoInstaller: [02/22/2008 13:14.13.986] DIF_INSTALLDEVICE: KMDF on-disk
version: 1.5.6000
WdfCoInstaller: [02/22/2008 13:14.14.001] Service Wdf01000 is running
WdfCoInstaller: [02/22/2008 13:14.14.079] DIF_INSTALLDEVICE: Reboot is
required, so that the newer KMDF version will be loaded to memory
WdfCoInstaller: [02/22/2008 13:14.14.189] VerifyMSRoot: exit: error(0) The
operation completed successfully.
WdfCoInstaller: [02/22/2008 13:14.14.564] Invoking
“C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode
Driver Framework Install-v1.7-Vista.msu” /quiet /norestart”.
WdfCoInstaller: [02/22/2008 13:14.31.517] Update process returned error code
0 :error(0) The operation completed successfully.
WdfCoInstaller: [02/22/2008 13:14.31.704] InstallComponents: KMDF installed
successfully
WdfCoInstaller: [02/22/2008 13:14.31.782] InstallComponents: Reboot needed
by windows update
WdfCoInstaller: [02/22/2008 13:14.32.861] DIF_INSTALLDEVICE: Post-Processing
WdfCoInstaller: [02/22/2008 13:39.21.111] DIF_INSTALLDEVICE: Pre-Processing
WdfCoInstaller: [02/22/2008 13:39.21.314] ReadComponents: WdfSection for
Driver Service FalconDrv using KMDF lib version Major 0x1, minor 0x7
WdfCoInstaller: [02/22/2008 13:39.21.361] DIF_INSTALLDEVICE: Coinstaller
version: 1.7.6001
WdfCoInstaller: [02/22/2008 13:39.21.439] GetInMemoryVersionUlong: No
information about in-memory KMDF version
WdfCoInstaller: [02/22/2008 13:39.21.532] DIF_INSTALLDEVICE: KMDF in-memory
version: 0.0.0
WdfCoInstaller: [02/22/2008 13:39.21.611] DIF_INSTALLDEVICE: KMDF on-disk
version: 1.5.6000
WdfCoInstaller: [02/22/2008 13:39.21.704] Service Wdf01000 is running
WdfCoInstaller: [02/22/2008 13:39.21.814] DIF_INSTALLDEVICE: Reboot is
required, so that the newer KMDF version will be loaded to memory
WdfCoInstaller: [02/22/2008 13:39.22.001] VerifyMSRoot: exit: error(0) The
operation completed successfully.
WdfCoInstaller: [02/22/2008 13:39.22.111] Invoking
“C:\Windows\system32\wusa.exe “C:\Windows\Temp\WdfTemp\Microsoft Kernel-Mode
Driver Framework Install-v1.7-Vista.msu” /quiet /norestart”.
WdfCoInstaller: [02/22/2008 13:39.37.814] Update process returned error code
0 :error(0) The operation completed successfully.
WdfCoInstaller: [02/22/2008 13:39.37.876] InstallComponents: KMDF installed
successfully
WdfCoInstaller: [02/22/2008 13:39.37.923] InstallComponents: Reboot needed
by windows update
WdfCoInstaller: [02/22/2008 13:39.38.782] DIF_INSTALLDEVICE: Post-Processing
Ashok
“Ilias Tsigkogiannis” wrote in message
news:xxxxx@ntdev…
> Ashok,
> Can you do the following:
> 1) Install a KMDF 1.7 driver.
> 2) Look at the files %windir%\system32\drivers\wdf01000.sys and
> %windir%\system32\drivers\wdfldr.sys. Reboot (if needed). Look at the
> driver in the device manager.
> 3) Install a 2nd KMDF 1.7 driver (or update the previous one)
> 4) Look at the files %windir%\system32\drivers\wdf01000.sys and
> %windir%\system32\drivers\wdfldr.sys. Reboot (if needed), and look again
> at the files and at the driver in the device manager.
> 5) Paste the diff of %windir%\setupact.log that corresponds to these 2
> driver installations?
>
> In the log that you pasted before, there are a couple of lines missing.
> Each installation starts with the line:
> DIF_INSTALLDEVICE: Pre-Processing
> and ends with the line
> DIF_INSTALLDEVICE: Post-Processing
>
> Thanks,
> Ilias
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Ilias
> Tsigkogiannis
> Sent: Thursday, February 21, 2008 12:58 PM
> To: Windows System Software Devs Interest List
> Subject: RE: Re:[ntdev] Re:RE:Upgrading to KDMF 1.7
>
> Ops 
> Yes
> I meant that the KMDF 1.5 coinstaller didn’t have to install the KMDF 1.5
> files in Vista, since KMDF 1.5 was inbox. That’s why nothing the KMDF 1.5
> coinstaller doesn’t log anything in %windir%\windowsupdate.log and
> windir%\logs\cbs\cbs.log (which are being used by the KMDF 1.7
> coinstaller). That’s why they are not mentioned in that post. Sorry!
>
> Ilias
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
> Sent: Thursday, February 21, 2008 12:47 PM
> To: Windows System Software Devs Interest List
> Subject: RE: Re:[ntdev] Re:RE:Upgrading to KDMF 1.7
>
>> KMDF 1.5 didn’t support Vista
>
> I think that is a bit of a typo ;). Vista shipped with v1.5, what I think
> ilias meant to say was that the v1.5 coinstaller did nothing on a vista
> device installation b/c it knew that KMDF was already present.
>
> d
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Ilias
> Tsigkogiannis
> Sent: Thursday, February 21, 2008 12:33 PM
> To: Windows System Software Devs Interest List
> Subject: RE: Re:[ntdev] Re:RE:Upgrading to KDMF 1.7
>
> No, I meant that KMDF 1.7 was released with Vista SP1 (it’s inbox in Vista
> SP1). If you install SP1, then the KMDF 1.7 files are also installed, so
> the coinstaller doesn’t have to install them. That’s why you see that the
> KMDF files are replaced, after you install Vista SP1. KMDF 1.7 supports
> all Windows versions from 2k and afterwards.
>
> Thanks for the feedback on my post. Could you give me the link to Doron’s
> post that you are referring to? You can also use the Wdf Verifier for
> additional options, if you don’t want to dig into the registry. It’s in
> %winddk%\tools\wdf<arch>\wdfverifier.exe.
>
> Also, you mentioned that you’re using dpinst.exe. Is it possible that you
> can use devcon and see, if that works or not?
>
> KMDF 1.5 didn’t support Vista, that’s why it talks about Wdf01005Inst.log.
> In Vista, the corresponding files are %windir%\windowsupdate.log and
> %windir%\logs\cbs\cbs.log. Is it possible that you can paste what you see
> in there, after you try to install KMDF 1.7? I need just the diff of
> “before” and “after” (even the diff will be a huge one, so it’s better to
> attach it in a separate file).
>
> I’ll dig a bit deeper into this.
>
> Ilias
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Ashok Bruno
> Sent: Thursday, February 21, 2008 8:50 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Re:RE:Upgrading to KDMF 1.7
>
> Hi
>
> I was reading through your post
> http://blogs.msdn.com/iliast/archive/2007/12/13/wdf-1-7-rc1-has-been-released.aspx
>
> I noticed that you mentioned Vista support with SP1 in brackets. Does this
> mean that KMDF 1.7 is only supported on Vista with SP1 ? As I mentioned
> before in one of my earlier replies, when I updated to SP1 on one of my
> systems the problem was resolved, however I do have systems on which I
> don’t
> have SP1 installed on which the driver just loads fine - on these systems
> however I had to uninstall all old instances of the driver and install the
> newer driver with the updated KMDF CoInstaller, and that seemed to make it
> work.
>
> Ashok
>
>
> “Ashok Bruno” wrote in message
> news:xxxxx@ntdev…
>> Hi,
>>
>> Let me provide some more information.
>>
>> I am using the Vista Business x64 Edition. I am running the system in
>> test
>> mode with my driver signed with a certificate generated on my build
>> machine and installed on the target.
>>
>> I have the same problem on another system and I am looking at the logs. I
>> don’t see the logs Wdf01005Inst.log or Wdf01007Inst.log. I used the OSR
>> tool to turn on detailed logging. I also looked in the registry to make
>> sure that HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\LogLevel
>> was set to 0x2000ffff
>>
>> Here is an extract from the setupact log.
>>
>> WdfCoInstaller: [02/21/2008 10:32.02.660] InstallComponents: KMDF
>> installed successfully
>> WdfCoInstaller: [02/21/2008 10:32.02.817] InstallComponents: Reboot
>> needed
>> by windows update
>> WdfCoInstaller: [02/21/2008 10:32.03.223] DIF_INSTALLDEVICE:
>> Post-Processing
>> WdfCoInstaller: [02/21/2008 10:32.19.270] DIF_INSTALLDEVICE:
>> Pre-Processing
>> WdfCoInstaller: [02/21/2008 10:32.19.364] ReadComponents: WdfSection for
>> Driver Service HealthMonitorUsbDrv using KMDF lib version Major 0x1,
>> minor
>> 0x7
>> WdfCoInstaller: [02/21/2008 10:32.19.395] DIF_INSTALLDEVICE: Coinstaller
>> version: 1.7.6001
>> WdfCoInstaller: [02/21/2008 10:32.19.442] GetInMemoryVersionUlong: No
>> information about in-memory KMDF version
>> WdfCoInstaller: [02/21/2008 10:32.19.504] DIF_INSTALLDEVICE: KMDF
>> in-memory version: 0.0.0
>> WdfCoInstaller: [02/21/2008 10:32.19.567] DIF_INSTALLDEVICE: KMDF on-disk
>> version: 1.5.6000
>> WdfCoInstaller: [02/21/2008 10:32.19.614] Service Wdf01000 is running
>> WdfCoInstaller: [02/21/2008 10:32.19.629] DIF_INSTALLDEVICE: Reboot is
>> required, so that the newer KMDF version will be loaded to memory
>> WdfCoInstaller: [02/21/2008 10:32.19.676] VerifyMSRoot: exit: error(0)
>> The
>> operation completed successfully.
>>
>> but after the reboot I get a bang on the driver. when I look at the
>> version of the Wdf files in the system32\drivers folder I see 1.5.6000,
>> however I do see that the WdfCoInstaller01007.dll is present in the
>> folder
>> alongwith WdfCoInstaller01005.dll
>>
>> Here is the relevant extract from the DpInst log.
>>
>> INFO:
>> INFO: 02/21/2008 10:32:15
>> INFO: Product Version 2.1.0.0.
>> INFO: Version: 6.0.6000
>> INFO: Platform ID: 2 (NT)
>> INFO: Service Pack: 0.0
>> INFO: Suite: 0x0100, Product Type: 1
>> INFO: Architecture: AMD64.
>> INFO: Interactive Windows Station
>> INFO: Command Line: '“\FolderName\DPInst.exe” '
>> INFO: DPInst is a multi-lingual binary.
>> INFO:
>> INFO: Current working directory: ‘\FolderName’
>> INFO: Running on path ‘\FolderName’
>> INFO: User UI Language is 0x409.
>> INFO: Install option set: Prompt if driver is not better.
>> INFO: Found driver package: ‘\FolderName\filename.inf’.
>> INFO: Preinstalling ‘\FolderName\filename.inf’ …
>> INFO: ENTER: DriverPackagePreinstallW
>> SUCCESS:\FolderName\filename.inf is preinstalled.
>> INFO: RETURN: DriverPackagePreinstallW (0x0)
>> INFO: ENTER: DriverPackageGetPathW
>> INFO: RETURN: DriverPackageGetPathW (0x0)
>> INFO: ENTER: DriverPackageInstallW
>> INFO: Installing INF file ‘\FolderName\filename.inf’ (Plug and Play).
>> INFO: Looking for Model Section [Standard.NTAMD64]…
>> INFO: Installing devices with Id “USB\VID_05FF&PID_1010&REV_0100” using
>> INF
>> “C:\Windows\System32\DriverStore\FileRepository\filename.inf_d6169c03\filename.inf”.
>> INFO: ENTER UpdateDriverForPlugAndPlayDevices…
>> SUCCESS:RETURN UpdateDriverForPlugAndPlayDevices.
>> INFO: Installation was successful.
>> SUCCESS:Install completed
>> INFO: RETURN: DriverPackageInstallW (0x0)
>> INFO: Successfull installation of ‘\FolderName\filename.inf’.
>> INFO: Created entry in Add or Remove Programs for
>> ‘C:\Windows\System32\DriverStore\FileRepository\filename.inf_d6169c03\filename.inf’.
>> INFO: Machine will have to be rebooted to complete installation.
>> INFO: Returning with code 0x40000001
>> INFO: 02/21/2008 10:32:26
>>
>> I haven’t installed an RC1 version of KMDF in the past.
>>
>> I appreciate the blog post, if you could put the information required to
>> turn on logging(which I found in Doron’s blog - the link is outdated)
>> along with the post that would be great.
>>
>> Thanks much,
>> Ashok
>>
>> “Ilias Tsigkogiannis” wrote in message
>> news:xxxxx@ntdev…
>>> I have a post in my blog at
>>> http://blogs.msdn.com/iliast/archive/2007/11/28/analyzing-the-installation-of-umdf-and-kmdf-1-5-drivers.aspx
>>> about how to debug the problems in UMDF/KMDF 1.5 drivers. Now that WDF
>>> 1.7 is out, I need to write a new post about 1.7 drivers, however could
>>> you take a look at it and see, if it helps you?
>>>
>>> Generally, you can take a look at %windor%\setupact.log to see the logs
>>> of the coinstaller and at %windor%\inf\setupapi.dev.log to see the logs
>>> of the PNP manager. I can provide more help, if needed.
>>>
>>> Ilias
>>>
>>> P.S. When you say “the old version”, which version is that? Have you by
>>> any chance installed an RC1 version of KMDF in the past?
>>>
>>> ________________________________________
>>> From: xxxxx@lists.osr.com
>>> [xxxxx@lists.osr.com] On Behalf Of Ashok Bruno
>>> [xxxxx@hotmail.com]
>>> Sent: Wednesday, February 20, 2008 11:24 AM
>>> To: Windows System Software Devs Interest List
>>> Subject: Re:[ntdev] RE:Upgrading to KDMF 1.7
>>>
>>> I use DpInst.exe to install the driver with a test certificate with the
>>> OS
>>> in test mode. The process returns Success, but I get a bang on the
>>> driver,
>>> saying the driver cannot start. When I look at the drivers folder, I
>>> still
>>> see that Wdfldr.sys and Wdf01000.sys are the old version.
>>>
>>> I am using the RTM version of server 2008.
>>>
>>> On the unit I tried upgrading to SP1 and that seemed to fix the problem
>>> ??? !!! I am sure I will see it on other systems, that I might be
>>> able
>>> to
>>> reproduce.
>>>
>>>
>>>
>>> “Doron Holan” wrote in message
>>> news:xxxxx@ntdev…
>>>> I am a little confused, are the files that cannot be replaced are the
>>>> WDF
>>>> files (wdfldr.sys, wdf01000.sys) or your own driver file(s)? Which 1.7
>>>> coinstaller are you using ? the one from the RTM version of the server
>>>> 2008 wdk? Or a prerelease version?
>>>>
>>>> -----Original Message-----
>>>> From: xxxxx@lists.osr.com
>>>> [mailto:xxxxx@lists.osr.com] On Behalf Of
>>>> xxxxx@gmail.com
>>>> Sent: Wednesday, February 20, 2008 10:34 AM
>>>> To: Windows System Software Devs Interest List
>>>> Subject: RE:[ntdev] Upgrading to KDMF 1.7
>>>>
>>>> Ashok Bruno wrote:
>>>>
>>>>> I recently tried upgrading from 1.5 to 1.7, and it’s been a nightmare
>>>>> to say the least. I was able to upgrade on some systems by unloading
>>>>> all instances of my driver and then installing the new version.
>>>>>
>>>>> I currently have a system where I am unable to upgrade to using the
>>>>> newer version of the WDF files. The sys files in the drivers folder
>>>>> are
>>>>> the old version, and cannot be replaced.
>>>>
>>>> And so it begins…
>>>>
>>>> —
>>>> 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
>
> —
> 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
>