Prev: Assertion in KeUpdateRunTime with Free Build of Windows Vista.
Next: USB device detection via query registry information
From: dsrking2006 on 29 Aug 2008 03:19
Hi Doron,

Thanks for Reply.

I read the link as you mentioned above and follow the steps.

In my wdf1007.log file, the following error message displayed.
************************************************************************************************************
0.047:
================================================================================
0.047: 2008/08/29 12:24:25.250 (local)
0.047: f:\16c06cbf342c200edf87a8a8017806\update\update.exe (version
6.3.4.1)
0.078: Hotfix started with following command line: /quiet /o /ER
0.078: CheckSystem: GetCheckedFree
failed :STATUS_CHECKED_FREE_MISMATCH
0.078: DoInstallation: CheckSystem Failed: 0xf002
0.094: Wdf01007 Setup cannot update a checked (debug) system with a
free (retail) version of Wdf01007, or vice versa.
0.094: Update.exe extended error code = 0xf002

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

Here, I cant get clear idea about STATUS_CHECKED_FREE_MISMATCH error.

Can you explain this?

And also I changed the coinstaller version to 1.5 and and again load
it through devcon utility. Here the inf is accepted but finally it
shows yellow mark on device manager.

And also setupapi.log shows,

#-199 Executing "D:\TESTING\hidusbfx2\Install\devcon.exe" with command
line: devcon install hidusbfx2.inf "hidusbfx2"
#I060 Set selected driver.
#-019 Searching for hardware ID(s): hidusbfx2
#I022 Found "hidusbfx2" in d:\testing\hidusbfx2\install\hidusbfx2.inf;
Device: "KMDF HID Minidriver for OSR USB-FX2 Device"; Driver: "KMDF
HID Minidriver for OSR USB-FX2 Device"; Provider: "Vendor Name"; Mfg:
"Vendor Name"; Section name: "hidusbfx2.Inst".
#I087 Driver node not trusted, rank changed from 0x00000000 to
0x00008000.
#I023 Actual install section: [hidusbfx2.Inst.NT]. Rank: 0x00008000.
Effective driver date: 08/29/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [hidusbfx2.Inst] in "d:
\testing\hidusbfx2\install\hidusbfx2.inf".
#I320 Class GUID of device remains: {745A17A0-74D3-11D0-
B6FE-00A0C90F57DA}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ROOT\HIDCLASS\0000".
#E366 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn, user said ok).
Error 0xe000022f: The third-party INF does not contain digital
signature information.
#-024 Copying file "d:\testing\hidusbfx2\install\hidusbfx2.sys" to "C:
\WINDOWS\system32\DRIVERS\hidusbfx2.sys".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
The third-party INF does not contain digital signature information.
#-336 Copying file "d:\testing\hidusbfx2\install\hidkmdf.sys" to "C:
\WINDOWS\system32\DRIVERS\hidkmdf.sys" via temporary file "C:\WINDOWS
\system32\DRIVERS\SET5C.tmp".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
The third-party INF does not contain digital signature information.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [hidusbfx2.Inst.NT.Interfaces] from "d:
\testing\hidusbfx2\install\hidusbfx2.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\HIDCLASS\0000".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
The third-party INF does not contain digital signature information.
#I163 Device not started: Device has problem: 0x25:
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.


==================================

and also I cant clear idea about "CM_PROB_FAILED_DRIVER_ENTRY"?

Thanks in Advance.

Regards - Dsrking.



From: Doron Holan [MSFT] on 29 Aug 2008 23:49
STATUS_CHECKED_FREE_MISMATCH means you are either trying to
a) install a chk coinstaller on a fre install
b) isntall a fre coinstaller on a chk build

what build are you running on?

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


<dsrking2006(a)gmail.com> wrote in message
news:cd29bd30-bd5e-4ad7-934a-46b4d97b2b95(a)o40g2000prn.googlegroups.com...
> Hi Doron,
>
> Thanks for Reply.
>
> I read the link as you mentioned above and follow the steps.
>
> In my wdf1007.log file, the following error message displayed.
> ************************************************************************************************************
> 0.047:
> ================================================================================
> 0.047: 2008/08/29 12:24:25.250 (local)
> 0.047: f:\16c06cbf342c200edf87a8a8017806\update\update.exe (version
> 6.3.4.1)
> 0.078: Hotfix started with following command line: /quiet /o /ER
> 0.078: CheckSystem: GetCheckedFree
> failed :STATUS_CHECKED_FREE_MISMATCH
> 0.078: DoInstallation: CheckSystem Failed: 0xf002
> 0.094: Wdf01007 Setup cannot update a checked (debug) system with a
> free (retail) version of Wdf01007, or vice versa.
> 0.094: Update.exe extended error code = 0xf002
>
> ************************************************************************************************************
>
> Here, I cant get clear idea about STATUS_CHECKED_FREE_MISMATCH error.
>
> Can you explain this?
>
> And also I changed the coinstaller version to 1.5 and and again load
> it through devcon utility. Here the inf is accepted but finally it
> shows yellow mark on device manager.
>
> And also setupapi.log shows,
>
> #-199 Executing "D:\TESTING\hidusbfx2\Install\devcon.exe" with command
> line: devcon install hidusbfx2.inf "hidusbfx2"
> #I060 Set selected driver.
> #-019 Searching for hardware ID(s): hidusbfx2
> #I022 Found "hidusbfx2" in d:\testing\hidusbfx2\install\hidusbfx2.inf;
> Device: "KMDF HID Minidriver for OSR USB-FX2 Device"; Driver: "KMDF
> HID Minidriver for OSR USB-FX2 Device"; Provider: "Vendor Name"; Mfg:
> "Vendor Name"; Section name: "hidusbfx2.Inst".
> #I087 Driver node not trusted, rank changed from 0x00000000 to
> 0x00008000.
> #I023 Actual install section: [hidusbfx2.Inst.NT]. Rank: 0x00008000.
> Effective driver date: 08/29/2008.
> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> #I063 Selected driver installs from section [hidusbfx2.Inst] in "d:
> \testing\hidusbfx2\install\hidusbfx2.inf".
> #I320 Class GUID of device remains: {745A17A0-74D3-11D0-
> B6FE-00A0C90F57DA}.
> #I060 Set selected driver.
> #I058 Selected best compatible driver.
> #-124 Doing copy-only install of "ROOT\HIDCLASS\0000".
> #E366 An unsigned or incorrectly signed file "d:\testing
> \hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
> OSR USB-FX2 Device" will be installed (Policy=Warn, user said ok).
> Error 0xe000022f: The third-party INF does not contain digital
> signature information.
> #-024 Copying file "d:\testing\hidusbfx2\install\hidusbfx2.sys" to "C:
> \WINDOWS\system32\DRIVERS\hidusbfx2.sys".
> #E362 An unsigned or incorrectly signed file "d:\testing
> \hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
> OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
> The third-party INF does not contain digital signature information.
> #-336 Copying file "d:\testing\hidusbfx2\install\hidkmdf.sys" to "C:
> \WINDOWS\system32\DRIVERS\hidkmdf.sys" via temporary file "C:\WINDOWS
> \system32\DRIVERS\SET5C.tmp".
> #E362 An unsigned or incorrectly signed file "d:\testing
> \hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
> OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
> The third-party INF does not contain digital signature information.
> #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> #I056 Coinstallers registered.
> #-166 Device install function: DIF_INSTALLINTERFACES.
> #-011 Installing section [hidusbfx2.Inst.NT.Interfaces] from "d:
> \testing\hidusbfx2\install\hidusbfx2.inf".
> #I054 Interfaces installed.
> #-166 Device install function: DIF_INSTALLDEVICE.
> #I123 Doing full install of "ROOT\HIDCLASS\0000".
> #E362 An unsigned or incorrectly signed file "d:\testing
> \hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
> OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
> The third-party INF does not contain digital signature information.
> #I163 Device not started: Device has problem: 0x25:
> CM_PROB_FAILED_DRIVER_ENTRY.
> #I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.
>
>
> ==================================
>
> and also I cant clear idea about "CM_PROB_FAILED_DRIVER_ENTRY"?
>
> Thanks in Advance.
>
> Regards - Dsrking.
>
>
>

From: dsrking2006 on 1 Sep 2008 09:05
Hi Doron,

Thanks for Reply,

ya fine . I corrected the "STATUS_CHECKED_FREE_MISMATCH" error as u
explained above. Now After loading sys file , it shows Error code 10
and the setupapi.log file shows as follows,
==================================================
The third-party INF does not contain digital signature information.
#I163 Device not started: Device has problem: 0x25:
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.
===================================================

I cant clear the "CM_PROB_FAILED_DRIVER_ENTRY" error.

Is any solution for this?

Thanks in Advance.

Regards - Dsrking.

From: Doron Holan [MSFT] on 1 Sep 2008 12:53
try disabling/enabling the device in device manager to try to reload the
driver. before you do this, break into windbg and set an unresolved
breakpoint to your driver's DriverEntry

bu <yourdriver>!DriverEntry

and see if it gets hit

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


<dsrking2006(a)gmail.com> wrote in message
news:a755f0bb-8cc9-4fbf-bc3c-46cc42fe5fde(a)b38g2000prf.googlegroups.com...
> Hi Doron,
>
> Thanks for Reply,
>
> ya fine . I corrected the "STATUS_CHECKED_FREE_MISMATCH" error as u
> explained above. Now After loading sys file , it shows Error code 10
> and the setupapi.log file shows as follows,
> ==================================================
> The third-party INF does not contain digital signature information.
> #I163 Device not started: Device has problem: 0x25:
> CM_PROB_FAILED_DRIVER_ENTRY.
> #I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.
> ===================================================
>
> I cant clear the "CM_PROB_FAILED_DRIVER_ENTRY" error.
>
> Is any solution for this?
>
> Thanks in Advance.
>
> Regards - Dsrking.
>

From: dsrking2006 on 2 Sep 2008 06:03
Hi Doron,

Thank you so much.

I loaded successfully hidusbfx2 as virtual one.

bu command is very useful for this kind of errors.

Is there any user manual for windbg commands?

Once again Thanks.

Warm Regards - Dsrking.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Assertion in KeUpdateRunTime with Free Build of Windows Vista.
Next: USB device detection via query registry information