Install issues on Win 7 RC Ultimate 64-bit

My frustrations have multiplied. I finally got the driver signing to work,
so now I have a signed SwrxDriver.sys and a signed driver package. I have
verified the signature on my development machine before zipping it up, and
verified the signatures on the target machine after un-zipping the package.

When I "Update the driver" for the board currently under an un-signed
driver, I got the message code 52 - driver unsigned... what? or why? So I
restarted the machine and tried again with the help of F8. The board shows
error code 18 and recommends that I reinstall. So I do so only to be told
that my driver is up-to-date. But the board is still banged out. And this
is while having the signature checking turned off.

What should I do next? Uninstall and delete the software? Remove the board
and clean the registry? Recompile my driver with a new version number, update
my inf file, resign the driver, inf2cat, and resign the cat file, rezip,
redeploy? Can I uninstall the Driver Store so I can get my work done?

Are my customers going to run into this in the field? Are they going to
have something go wrong, then be unable to load a perfectly good version of
my driver until I build a new one, exactly the same, except for the version
number?

I need a little bit more knowledge about what is going on here, so that I
can quit freaking Win7 out with my driver testing.
--
Mr. Fixit needs your help! - John Bond , LLC

"John Bond" wrote:

> My frustrations have multiplied. I finally got the driver signing to work,
> so now I have a signed SwrxDriver.sys and a signed driver package. I have
> verified the signature on my development machine before zipping it up, and
> verified the signatures on the target machine after un-zipping the package.
>
> When I "Update the driver" for the board currently under an un-signed
> driver, I got the message code 52 - driver unsigned... what? or why? So I
> restarted the machine and tried again with the help of F8. The board shows
> error code 18 and recommends that I reinstall. So I do so only to be told
> that my driver is up-to-date. But the board is still banged out. And this
> is while having the signature checking turned off.
>
> What should I do next? Uninstall and delete the software? Remove the board
> and clean the registry? Recompile my driver with a new version number, update
> my inf file, resign the driver, inf2cat, and resign the cat file, rezip,
> redeploy? Can I uninstall the Driver Store so I can get my work done?
>
> Are my customers going to run into this in the field? Are they going to
> have something go wrong, then be unable to load a perfectly good version of
> my driver until I build a new one, exactly the same, except for the version
> number?
>
> I need a little bit more knowledge about what is going on here, so that I
> can quit freaking Win7 out with my driver testing.
> --
John Bond continues in his trials:

Okay, so I chose to uninstall and checked the box to uninstall the software.
Then I scanned for new hardware. Then I reinstalled the software for which
"signtool verify /v /pa SwrxDriver.sys" said all was good and happy , which
happens to be the latest. After it was complete, I got error code 1, device
is not configured correctly. (Positive attitude time Awesome!

So I uninstalled the driver, shut down and unistalled that board (DP3209).
Then I installed an NGX800 and restarted Win 7 RC Ultimate 64-bit. Went to
Computer Manager/Device Manager and check on the state of my NGX800, device
status reads Code 52, Windows cannot verify the digital signature... however
in the next window, signtool verify /v /pa SwrxDriver.sys yeilds "files
successfully Verified: 1". And then fc SwrxDriver.sys
c:\Windows\System32\drivers\SwrxDriver.sys says "FC: no differences
encountered"

Stay tuned to this Bat-channel while I try recompiling the exact same code
with a new version number using the same signing process...

> "John Bond" wrote:
>
> > My frustrations have multiplied. I finally got the driver signing to work,
> > so now I have a signed SwrxDriver.sys and a signed driver package. I have
> > verified the signature on my development machine before zipping it up, and
> > verified the signatures on the target machine after un-zipping the package.
> >
> > When I "Update the driver" for the board currently under an un-signed
> > driver, I got the message code 52 - driver unsigned... what? or why? So I
> > restarted the machine and tried again with the help of F8. The board shows
> > error code 18 and recommends that I reinstall. So I do so only to be told
> > that my driver is up-to-date. But the board is still banged out. And this
> > is while having the signature checking turned off.
> >
> > What should I do next? Uninstall and delete the software? Remove the board
> > and clean the registry? Recompile my driver with a new version number, update
> > my inf file, resign the driver, inf2cat, and resign the cat file, rezip,
> > redeploy? Can I uninstall the Driver Store so I can get my work done?
> >
> > Are my customers going to run into this in the field? Are they going to
> > have something go wrong, then be unable to load a perfectly good version of
> > my driver until I build a new one, exactly the same, except for the version
> > number?
> >
> > I need a little bit more knowledge about what is going on here, so that I
> > can quit freaking Win7 out with my driver testing.
> > --
> John Bond continues in his trials:
>
> Okay, so I chose to uninstall and checked the box to uninstall the software.
> Then I scanned for new hardware. Then I reinstalled the software for which
> "signtool verify /v /pa SwrxDriver.sys" said all was good and happy , which
> happens to be the latest. After it was complete, I got error code 1, device
> is not configured correctly. (Positive attitude time Awesome!
>
> So I uninstalled the driver, shut down and unistalled that board (DP3209).
> Then I installed an NGX800 and restarted Win 7 RC Ultimate 64-bit. Went to
> Computer Manager/Device Manager and check on the state of my NGX800, device
> status reads Code 52, Windows cannot verify the digital signature... however
> in the next window, signtool verify /v /pa SwrxDriver.sys yeilds "files
> successfully Verified: 1". And then fc SwrxDriver.sys
> c:\Windows\System32\drivers\SwrxDriver.sys says "FC: no differences
> encountered"
>
> Stay tuned to this Bat-channel while I try recompiling the exact same code
> with a new version number using the same signing process...

The new driver, 5.1.101.514, received error code 52 as well. Now I am
restarting the machine with F8 to disable the signature check. OK, got error
18, which tells me to reinstall. No way, been there, done that. I will
uninstall the board and software. Then reboot without any supported boards
installed. Shutdown install the DP3209, restart with F8... Okay, before I
could install anything PNP seems to have beat me to it. And the install
failed, thanks Win 7 PNP, I wanted to try that myself... X-(

Do I have to reinstall Win 7 on this hard drive, or should I try using XP
64-bit?

> > "John Bond" wrote:
> >
> > > My frustrations have multiplied. I finally got the driver signing to work,
> > > so now I have a signed SwrxDriver.sys and a signed driver package. I have
> > > verified the signature on my development machine before zipping it up, and
> > > verified the signatures on the target machine after un-zipping the package.
> > >
> > > When I "Update the driver" for the board currently under an un-signed
> > > driver, I got the message code 52 - driver unsigned... what? or why? So I
> > > restarted the machine and tried again with the help of F8. The board shows
> > > error code 18 and recommends that I reinstall. So I do so only to be told
> > > that my driver is up-to-date. But the board is still banged out. And this
> > > is while having the signature checking turned off.
> > >
> > > What should I do next? Uninstall and delete the software? Remove the board
> > > and clean the registry? Recompile my driver with a new version number, update
> > > my inf file, resign the driver, inf2cat, and resign the cat file, rezip,
> > > redeploy? Can I uninstall the Driver Store so I can get my work done?
> > >
> > > Are my customers going to run into this in the field? Are they going to
> > > have something go wrong, then be unable to load a perfectly good version of
> > > my driver until I build a new one, exactly the same, except for the version
> > > number?
> > >
> > > I need a little bit more knowledge about what is going on here, so that I
> > > can quit freaking Win7 out with my driver testing.
> > > --
> > John Bond continues in his trials:
> >
> > Okay, so I chose to uninstall and checked the box to uninstall the software.
> > Then I scanned for new hardware. Then I reinstalled the software for which
> > "signtool verify /v /pa SwrxDriver.sys" said all was good and happy , which
> > happens to be the latest. After it was complete, I got error code 1, device
> > is not configured correctly. (Positive attitude time Awesome!
> >
> > So I uninstalled the driver, shut down and unistalled that board (DP3209).
> > Then I installed an NGX800 and restarted Win 7 RC Ultimate 64-bit. Went to
> > Computer Manager/Device Manager and check on the state of my NGX800, device
> > status reads Code 52, Windows cannot verify the digital signature... however
> > in the next window, signtool verify /v /pa SwrxDriver.sys yeilds "files
> > successfully Verified: 1". And then fc SwrxDriver.sys
> > c:\Windows\System32\drivers\SwrxDriver.sys says "FC: no differences
> > encountered"
> >
> > Stay tuned to this Bat-channel while I try recompiling the exact same code
> > with a new version number using the same signing process...
>
> The new driver, 5.1.101.514, received error code 52 as well. Now I am
> restarting the machine with F8 to disable the signature check. OK, got error
> 18, which tells me to reinstall. No way, been there, done that. I will
> uninstall the board and software. Then reboot without any supported boards
> installed. Shutdown install the DP3209, restart with F8... Okay, before I
> could install anything PNP seems to have beat me to it. And the install
> failed, thanks Win 7 PNP, I wanted to try that myself... X-(
>
> Do I have to reinstall Win 7 on this hard drive, or should I try using XP
> 64-bit?

John Bond continues:
Attempting to load the same signed driver, I used system restore to go back
to when there were no test drivers. Once that was done attempting to load a
driver for the board got the result that no driver could be found (assume
Driver Store blocked it silently again...)

So then I reloaded Win 7 from scratch (formating the drive). The system
then posted the bright red panel telling me that this driver was NOT signed
and should NOT be loaded but allowed me to click a button to load it. When
it was done installing it, I got error code 31, the driver is not signed and
cannot be loaded. So I check with "signtool verify /v /pa xxx" and it said
the driver was signed. I used the signtool from WDK 7.0.0.

BUT I realized on my development system that the signtool was from Vista and
had not allowed me to put in the OS Win7 symbol...

So now I am upgrading my WDK to 7100.0.0 to see if the new signtool, with
the added Win 7 option will do the trick. Wish me luck.

I hope you realize that 7100 is a 'downgrade' for 7.0.0 a.k.a. 7600.16385.0.
Did you build in the Win7 environment? Are you sure your certificates are
valid for this purpose?

"John Bond" <> wrote in message
news:8DDC1D23-27F6-4A1C-B5C3-...
>> > "John Bond" wrote:
>> >
>> > > My frustrations have multiplied. I finally got the driver signing to
>> > > work,
>> > > so now I have a signed SwrxDriver.sys and a signed driver package. I
>> > > have
>> > > verified the signature on my development machine before zipping it
>> > > up, and
>> > > verified the signatures on the target machine after un-zipping the
>> > > package.
>> > >
>> > > When I "Update the driver" for the board currently under an un-signed
>> > > driver, I got the message code 52 - driver unsigned... what? or why?
>> > > So I
>> > > restarted the machine and tried again with the help of F8. The board
>> > > shows
>> > > error code 18 and recommends that I reinstall. So I do so only to be
>> > > told
>> > > that my driver is up-to-date. But the board is still banged out.
>> > > And this
>> > > is while having the signature checking turned off.
>> > >
>> > > What should I do next? Uninstall and delete the software? Remove
>> > > the board
>> > > and clean the registry? Recompile my driver with a new version
>> > > number, update
>> > > my inf file, resign the driver, inf2cat, and resign the cat file,
>> > > rezip,
>> > > redeploy? Can I uninstall the Driver Store so I can get my work done?
>> > >
>> > > Are my customers going to run into this in the field? Are they going
>> > > to
>> > > have something go wrong, then be unable to load a perfectly good
>> > > version of
>> > > my driver until I build a new one, exactly the same, except for the
>> > > version
>> > > number?
>> > >
>> > > I need a little bit more knowledge about what is going on here, so
>> > > that I
>> > > can quit freaking Win7 out with my driver testing.
>> > > --
>> > John Bond continues in his trials:
>> >
>> > Okay, so I chose to uninstall and checked the box to uninstall the
>> > software.
>> > Then I scanned for new hardware. Then I reinstalled the software for
>> > which
>> > "signtool verify /v /pa SwrxDriver.sys" said all was good and happy ,
>> > which
>> > happens to be the latest. After it was complete, I got error code 1,
>> > device
>> > is not configured correctly. (Positive attitude time Awesome!
>> >
>> > So I uninstalled the driver, shut down and unistalled that board
>> > (DP3209).
>> > Then I installed an NGX800 and restarted Win 7 RC Ultimate 64-bit.
>> > Went to
>> > Computer Manager/Device Manager and check on the state of my NGX800,
>> > device
>> > status reads Code 52, Windows cannot verify the digital signature...
>> > however
>> > in the next window, signtool verify /v /pa SwrxDriver.sys yeilds "files
>> > successfully Verified: 1". And then fc SwrxDriver.sys
>> > c:\Windows\System32\drivers\SwrxDriver.sys says "FC: no differences
>> > encountered"
>> >
>> > Stay tuned to this Bat-channel while I try recompiling the exact same
>> > code
>> > with a new version number using the same signing process...
>>
>> The new driver, 5.1.101.514, received error code 52 as well. Now I am
>> restarting the machine with F8 to disable the signature check. OK, got
>> error
>> 18, which tells me to reinstall. No way, been there, done that. I will
>> uninstall the board and software. Then reboot without any supported
>> boards
>> installed. Shutdown install the DP3209, restart with F8... Okay, before
>> I
>> could install anything PNP seems to have beat me to it. And the install
>> failed, thanks Win 7 PNP, I wanted to try that myself... X-(
>>
>> Do I have to reinstall Win 7 on this hard drive, or should I try using XP
>> 64-bit?
>
> John Bond continues:
> Attempting to load the same signed driver, I used system restore to go
> back
> to when there were no test drivers. Once that was done attempting to load
> a
> driver for the board got the result that no driver could be found (assume
> Driver Store blocked it silently again...)
>
> So then I reloaded Win 7 from scratch (formating the drive). The system
> then posted the bright red panel telling me that this driver was NOT
> signed
> and should NOT be loaded but allowed me to click a button to load it.
> When
> it was done installing it, I got error code 31, the driver is not signed
> and
> cannot be loaded. So I check with "signtool verify /v /pa xxx" and it
> said
> the driver was signed. I used the signtool from WDK 7.0.0.
>
> BUT I realized on my development system that the signtool was from Vista
> and
> had not allowed me to put in the OS Win7 symbol...
>
> So now I am upgrading my WDK to 7100.0.0 to see if the new signtool, with
> the added Win 7 option will do the trick. Wish me luck.
>
>

John Bond <> wrote:
>
>My frustrations have multiplied. I finally got the driver signing to work,
>so now I have a signed SwrxDriver.sys and a signed driver package. I have
>verified the signature on my development machine before zipping it up, and
>verified the signatures on the target machine after un-zipping the package.

....including the cross-certificate?
--
Tim Roberts,
Providenza & Boekelheide, Inc.

> > > "John Bond" wrote:
> > >
> > > > My frustrations have multiplied. I finally got the driver signing to work,
> > > > so now I have a signed SwrxDriver.sys and a signed driver package. I have
> > > > verified the signature on my development machine before zipping it up, and
> > > > verified the signatures on the target machine after un-zipping the package.
> > > >
> > > > When I "Update the driver" for the board currently under an un-signed
> > > > driver, I got the message code 52 - driver unsigned... what? or why? So I
> > > > restarted the machine and tried again with the help of F8. The board shows
> > > > error code 18 and recommends that I reinstall. So I do so only to be told
> > > > that my driver is up-to-date. But the board is still banged out. And this
> > > > is while having the signature checking turned off.
> > > >
> > > > What should I do next? Uninstall and delete the software? Remove the board
> > > > and clean the registry? Recompile my driver with a new version number, update
> > > > my inf file, resign the driver, inf2cat, and resign the cat file, rezip,
> > > > redeploy? Can I uninstall the Driver Store so I can get my work done?
> > > >
> > > > Are my customers going to run into this in the field? Are they going to
> > > > have something go wrong, then be unable to load a perfectly good version of
> > > > my driver until I build a new one, exactly the same, except for the version
> > > > number?
> > > >
> > > > I need a little bit more knowledge about what is going on here, so that I
> > > > can quit freaking Win7 out with my driver testing.
> > > > --
> > > John Bond continues in his trials:
> > >
> > > Okay, so I chose to uninstall and checked the box to uninstall the software.
> > > Then I scanned for new hardware. Then I reinstalled the software for which
> > > "signtool verify /v /pa SwrxDriver.sys" said all was good and happy , which
> > > happens to be the latest. After it was complete, I got error code 1, device
> > > is not configured correctly. (Positive attitude time Awesome!
> > >
> > > So I uninstalled the driver, shut down and unistalled that board (DP3209).
> > > Then I installed an NGX800 and restarted Win 7 RC Ultimate 64-bit. Went to
> > > Computer Manager/Device Manager and check on the state of my NGX800, device
> > > status reads Code 52, Windows cannot verify the digital signature... however
> > > in the next window, signtool verify /v /pa SwrxDriver.sys yeilds "files
> > > successfully Verified: 1". And then fc SwrxDriver.sys
> > > c:\Windows\System32\drivers\SwrxDriver.sys says "FC: no differences
> > > encountered"
> > >
> > > Stay tuned to this Bat-channel while I try recompiling the exact same code
> > > with a new version number using the same signing process...
> >
> > The new driver, 5.1.101.514, received error code 52 as well. Now I am
> > restarting the machine with F8 to disable the signature check. OK, got error
> > 18, which tells me to reinstall. No way, been there, done that. I will
> > uninstall the board and software. Then reboot without any supported boards
> > installed. Shutdown install the DP3209, restart with F8... Okay, before I
> > could install anything PNP seems to have beat me to it. And the install
> > failed, thanks Win 7 PNP, I wanted to try that myself... X-(
> >
> > Do I have to reinstall Win 7 on this hard drive, or should I try using XP
> > 64-bit?
>
> John Bond continues:
> Attempting to load the same signed driver, I used system restore to go back
> to when there were no test drivers. Once that was done attempting to load a
> driver for the board got the result that no driver could be found (assume
> Driver Store blocked it silently again...)
>
> So then I reloaded Win 7 from scratch (formating the drive). The system
> then posted the bright red panel telling me that this driver was NOT signed
> and should NOT be loaded but allowed me to click a button to load it. When
> it was done installing it, I got error code 31, the driver is not signed and
> cannot be loaded. So I check with "signtool verify /v /pa xxx" and it said
> the driver was signed. I used the signtool from WDK 7.0.0.
>
> BUT I realized on my development system that the signtool was from Vista and
> had not allowed me to put in the OS Win7 symbol...
>
> So now I am upgrading my WDK to 7100.0.0 to see if the new signtool, with
> the added Win 7 option will do the trick. Wish me luck.
>
John Bond finishes finding the root cause:

I still used WDK 6001.18002 to build the driver, but started using SignTool
and Inf2Cat from WDK 7100.0.0 to actually sign the files and to make my .cat
file work on Win7. All is well now.

The moral of the story: Use the latest Inf2Cat and SignTool or else. I owe
an appology to someone who told me that a week ago...