Re: Non-WHQL signed driver accepted by Vista but not XP. Why?



You mix 2 kinds of signing: a) WHQL signing and b) Authenticode signing.

You did only the second one. Yes, it is a must to load on Vista x64, but
will give you nothing on XP except possibly the Digital Signature tab in Device
Manager/Properties.

For your driver to be ranked high and to be installed without bothering
users with the UI, both on XP and Vista - WHQL is a must.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com

"Peter Jaquiery" <Peter Jaquiery@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF6776DF-D75E-46B7-868C-93A8B6E62EC5@xxxxxxxxxxxxxxxx
I have a non-WHQL USB device driver that we are signing successfully and
installing using DIFxApp on Vista. When I run the same install against XP
(x86) the driver files are installed, but the .cat file is not saved to
catroot and the driver is not recognized as a signed driver, although it
works correctly otherwise.

If I perform a software first install on a cleanly installed XP system then
plug in the hardware I get the new device wizard. On completing the wizard,
if I examine the driver properties using device manager I notice that the
driver is claimed to be not signed.

If I plug the device into a clean XP system, cancel the wizard, then perform
the install, the driver is installed for that device without the wizard
coming up or any other interruptions to the install process. The device
plugged in prior to the install is now available for use, although Device
manager reports that the driver is not signed. If I subsequently plug in
another device the new hardware wizard appears.

In both cases DIFxApp seems to recognize the driver as a signed driver. From
the install log:

DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: INFO: x.inf: checking signature with catalog 'C:\Program
Files\Common Files\x\x.cat' ...
DIFXAPP: INFO: Driver package 'x.inf' is Authenticode signed.

but in neither case is a new .cat file added to
c:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}. However
the TimeStamp file is updated during the install process and Wdf01005.cat is
added.

What do I need to do to fix this problem?

.



Relevant Pages

  • Re: Cannot disable add new hardware wizard
    ... Although the 'Add New Hardware' wizard started every time I blinked and the ... Device manager was unknown device, unknown driver, unknown...blah, blah ... So, with my printer and all the drivers installed, I put the install cd in, ...
    (microsoft.public.windowsxp.general)
  • Re: Cannot disable add new hardware wizard
    ... Hardware wizard /did/ run was, ... >> installed, I put the install cd in, started it, and after ... >>> Trying to install the driver did not work. ...
    (microsoft.public.windowsxp.general)
  • Re: XP HOME BOOT FAILURE
    ... you remove the driver for the graphics card, ... >> If you run a repair install as I initially described, ... A repair install should bypass that but it will ... >>>> on, follow the screens. ...
    (microsoft.public.windowsxp.accessibility)
  • Problems with Touchpad,keyboard and USB after Ideacom update (solu
    ... and keyboard .I have made fresh install of XP Home and have all updated ... recomended update from Driver detective,that i use offten. ... allready and when i do this it knocks off my USB mouse leaving me not able to ... 2.Mutil-Access driver HCT driver verify crash fix! ...
    (microsoft.public.windowsxp.general)
  • Re: Problems installing printers
    ... Cari (MS-MVP Windows Client - Printing, Imaging & Hardware) ... > The problem I have is that when I browse for the driver, ... > attached first then tried to install the drivers for 2 of the 3 printers. ... When the Found New Hardware Wizard starts at startup of the computer, ...
    (microsoft.public.windowsxp.general)