Windows serial driver - regarding

Hi all,

I have used the 16550 part of UART device where i updated the driver by taking the driver from wdk source , installed the driver and got code error 52 , it ask for restart and did.

Driver were loaded with yellow bang ,again i uninstalled the driver /scan the driver where it loaded the inbox driver.

Then loaded the compiled driver of wdk and it is loaded.

After restart the machine all the com port were loaded with the compiled driver in yellow bang of code status 52 in "device status " tab.

There are 6 com port driver has been shown with yellow bang.

could anyone suggested me.

Regards,
Prabhakar V

Hi all,

I have used win 7 64 bit OS.

Regards,
Prabhakar V

On Mon, Sep 25, 2017 at 2:32 PM, xxxxx@gmail.com
wrote:

> Hi all,
>
> I have used the 16550 part of UART device where i updated the driver by
> taking the driver from wdk source , installed the driver and got code error
> 52 , it ask for restart and did.
>
> Driver were loaded with yellow bang ,again i uninstalled the driver /scan
> the driver where it loaded the inbox driver.
>
> Then loaded the compiled driver of wdk and it is loaded.
>
> After restart the machine all the com port were loaded with the compiled
> driver in yellow bang of code status 52 in "device status " tab.
>
> There are 6 com port driver has been shown with yellow bang.
>
> could anyone suggested me.
>
>
> Regards,
> Prabhakar V
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

Why not use the in box serial driver? The wdk is a straight copy of it. One less piece of software for you to write. Sounds like all you may need to write is an inf

Bent from my phone


From: xxxxx@lists.osr.com on behalf of xxxxx@gmail.com
Sent: Monday, September 25, 2017 3:11:47 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Windows serial driver - regarding

Hi all,

I have used win 7 64 bit OS.

Regards,
Prabhakar V

On Mon, Sep 25, 2017 at 2:32 PM, xxxxx@gmail.commailto:xxxxx > wrote:
Hi all,

I have used the 16550 part of UART device where i updated the driver by taking the driver from wdk source , installed the driver and got code error 52 , it ask for restart and did.

Driver were loaded with yellow bang ,again i uninstalled the driver /scan the driver where it loaded the inbox driver.

Then loaded the compiled driver of wdk and it is loaded.

After restart the machine all the com port were loaded with the compiled driver in yellow bang of code status 52 in "device status " tab.

There are 6 com port driver has been shown with yellow bang.

could anyone suggested me.

Regards,
Prabhakar V


NTDEV is sponsored by OSR

Visit the list online at: http:>

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:>

To unsubscribe, visit the List Server section of OSR Online at http:>

— NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers! Details at To unsubscribe, visit the List Server section of OSR Online at</http:></http:></http:></mailto:xxxxx>

xxxxx@gmail.com wrote:

I have used the 16550 part of UART device where i updated the driver by taking the driver from wdk source , installed the driver and got code error 52 , it ask for restart and did.

Driver were loaded with yellow bang ,again i uninstalled the driver /scan the driver where it loaded the inbox driver.

Then loaded the compiled driver of wdk and it is loaded.

After restart the machine all the com port were loaded with the compiled driver in yellow bang of code status 52 in "device status " tab.

As Google would have told you, Device Manager code 52 is “cannot verify
the digital signature”.  Did you sign these drivers?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

>>As Google would have told you, Device Manager code 52 is "cannot verify

>the digital signature". Did you sign these drivers?
Yes its sounds like need to sign the drivers.

But why when we do bcdedit for testsigning on for windows 10 to be testmode
where we can load the driver without getting any error in restart also.

But in windows 7 x64 bit machine , why it get into error of code 52 after
restart also but OS in test mode (bcdedit for testsigning on) ?

Regards,
Prabhakar V

On Mon, Sep 25, 2017 at 8:41 PM, xxxxx@probo.com wrote:

> xxxxx@gmail.com wrote:
> > I have used the 16550 part of UART device where i updated the driver by
> taking the driver from wdk source , installed the driver and got code error
> 52 , it ask for restart and did.
> >
> > Driver were loaded with yellow bang ,again i uninstalled the driver
> /scan the driver where it loaded the inbox driver.
> >
> > Then loaded the compiled driver of wdk and it is loaded.
> >
> > After restart the machine all the com port were loaded with the compiled
> driver in yellow bang of code status 52 in "device status " tab.
>
> As Google would have told you, Device Manager code 52 is “cannot verify
> the digital signature”. Did you sign these drivers?
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

If your signature is accepted by Windows 10 but not Windows 7, you probably don’t have SHA-2 algorithm support; see https://technet.microsoft.com/en-us/library/security/3033929

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: 27 September 2017 15:16
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Windows serial driver - regarding

>>As Google would have told you, Device Manager code 52 is “cannot verify
>>the digital signature”. Did you sign these drivers?
Yes its sounds like need to sign the drivers.

But why when we do bcdedit for testsigning on for windows 10 to be testmode where we can load the driver without getting any error in restart also.

But in windows 7 x64 bit machine , why it get into error of code 52 after restart also but OS in test mode (bcdedit for testsigning on) ?

Regards,
Prabhakar V

On Mon, Sep 25, 2017 at 8:41 PM, xxxxx@probo.commailto:xxxxx > wrote:
xxxxx@gmail.commailto:xxxxx wrote:
> I have used the 16550 part of UART device where i updated the driver by taking the driver from wdk source , installed the driver and got code error 52 , it ask for restart and did.
>
> Driver were loaded with yellow bang ,again i uninstalled the driver /scan the driver where it loaded the inbox driver.
>
> Then loaded the compiled driver of wdk and it is loaded.
>
> After restart the machine all the com port were loaded with the compiled driver in yellow bang of code status 52 in "device status " tab.

As Google would have told you, Device Manager code 52 is “cannot verify
the digital signature”. Did you sign these drivers?


Tim Roberts, xxxxx@probo.commailto:xxxxx
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

Visit the list online at: http:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:

To unsubscribe, visit the List Server section of OSR Online at http:

— NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers! Details at To unsubscribe, visit the List Server section of OSR Online at</http:></http:></http:></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>

Hi all,

I have signed my driver on win7 x64 bit of Embedded system where im doing
restart/shutdown , not able to see the driver status in device manager with
code 52.

I have used our utility to get the signed driver.

i have load this same driver on win 7 x64 bit professional , where i loaded
the driver it accepted and didnt get the driver status with code 52 and
when i restart the machine it shows the yellow bang of code error 52.

Sometime it asked restart the machine ,after restart the driver doesnt load
properly and get into code 52.

But i have not faced this issue in Windows Embedded x64 bit OS.

I have used the : this to genrate the cat file.
C:\WinDDK\7600.16385.1\bin\selfsign>Inf2cat.exe
/driver:C:\WinDDK\7600.16385.1\s
rc\serial\serial\objfre_win7_amd64\amd64
/os:2000,XP_X86,XP_X64,Server2003_X86,S
erver2003_X64,Vista_X86,Vista_X64,7_X64,7_X86,Server2008_X64,Server2008_X86

i have used my signingprogramexecutable.exe to sign my .sys, .cat file.

whether i have missed anything ?

Again i need to use the signtool and then call our
signingprogramexecutable.exe to sign the driver.

Please help on this.

Regards,
Prabhakar V

On Wed, Sep 27, 2017 at 7:59 PM, xxxxx@becrypt.com
wrote:

> If your signature is accepted by Windows 10 but not Windows 7, you
> probably don’t have SHA-2 algorithm support; see
> https://technet.microsoft.com/en-us/library/security/3033929
>
>
>
> From: xxxxx@lists.osr.com [mailto:bounce-638728-159614@
> lists.osr.com] *On Behalf Of *xxxxx@gmail.com
> Sent: 27 September 2017 15:16
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Windows serial driver - regarding
>
>
>
> >>As Google would have told you, Device Manager code 52 is “cannot verify
>
> >>the digital signature”. Did you sign these drivers?
>
> Yes its sounds like need to sign the drivers.
>
>
>
> But why when we do bcdedit for testsigning on for windows 10 to be
> testmode where we can load the driver without getting any error in restart
> also.
>
>
>
> But in windows 7 x64 bit machine , why it get into error of code 52 after
> restart also but OS in test mode (bcdedit for testsigning on) ?
>
>
>
> Regards,
>
> Prabhakar V
>
>
>
> On Mon, Sep 25, 2017 at 8:41 PM, xxxxx@probo.com
> wrote:
>
> xxxxx@gmail.com wrote:
> > I have used the 16550 part of UART device where i updated the driver by
> taking the driver from wdk source , installed the driver and got code error
> 52 , it ask for restart and did.
> >
> > Driver were loaded with yellow bang ,again i uninstalled the driver
> /scan the driver where it loaded the inbox driver.
> >
> > Then loaded the compiled driver of wdk and it is loaded.
> >
> > After restart the machine all the com port were loaded with the compiled
> driver in yellow bang of code status 52 in "device status " tab.
>
> As Google would have told you, Device Manager code 52 is “cannot verify
> the digital signature”. Did you sign these drivers?
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
>
>
>
> — NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars
> on crash dump analysis, WDF, Windows internals and software drivers!
> Details at To unsubscribe, visit the List Server section of OSR Online at
>
>
> ------------------------------
> This email message has been delivered safely and archived online by
> Mimecast.
> For more information please visit http://www.mimecast.com
> ------------------------------
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:></http:></http:>

On Oct 13, 2017, at 6:43 AM, xxxxx@gmail.com wrote:
>
> I have signed my driver on win7 x64 bit of Embedded system where im doing restart/shutdown , not able to see the driver status in device manager with code 52.
>
> I have used our utility to get the signed driver.

Why?

> i have load this same driver on win 7 x64 bit professional , where i loaded the driver it accepted and didnt get the driver status with code 52 and when i restart the machine it shows the yellow bang of code error 52.
>
> Sometime it asked restart the machine ,after restart the driver doesnt load properly and get into code 52.
>
> But i have not faced this issue in Windows Embedded x64 bit OS.

You are contradicting yourself here. Where does the driver work? Where does it not work?

> i have used my signingprogramexecutable.exe to sign my .sys, .cat file.

Why would you do that? You need to use “signtool sign /kp /ac” to sign your programs. None of us have any idea what “signingprogramexecutable.exe” does, but it seems quite clear that it is screwing up your certificate chain. Remember that the kernel-mode signing rules are different from the user-mode signing rules. Show us the exact commands you are executing.

As a check, do this:
signtool verify /v /kp xxxx.cat

If you do not see “Microsoft Code Verification Root” in the certificate chain, then your signing process is incorrect and the operating systems will not load it.

And, by the way, when you are generating the CAT file for an “amd64” build, it is silly to include 2000 or any of the _X86 operating systems in the inf2cat list, since the package obviously cannot be loaded there.

Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Prabhakar V wrote:

I have verified that signtool verify /v /kp xxxx.cat
http:</http:> for .cat / .sys file. ( Please find that attachment
where it is fine only).

inf2cat.exe /driver:“C:\toaster” /os:7_X64 /verbose

I have generated the .cat file for 7_X64 bit only.

Still when i load the statbus i.e toaster driver getting code 52.

Is your Windows 7 system SP1?  Does it have all updates applied?  You
are using an SHA2 certificate.  (An EV certificate, to be exact.)  The
original release of Windows 7 did not support SHA2 certificates.  There
was an update of Windows 7 SP1 that added this ability.

https://support.microsoft.com/en-us/help/2921916/the-untrusted-publisher-dialog-box-appears-when-you-install-a-driver-i
https://support.microsoft.com/en-us/help/3033929/microsoft-security-advisory-availability-of-sha-2-code-signing-support


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Prabhakar V wrote:

when i run signtool for verify i.e to check the “Microsoft Code
Verification Root” and used the hash of file is “sha1”.( It was there).

That is merely showing you the SHA1 hash of the file being signed, in
case you need to verify that it is the correct file.  Your certificate
is encoded with SHA2, as are all EV certificates:

DigiCert EV Code Signing CA (SHA2)

I have used win 7 x64 bit pro SPI.

Do you mean, for signing the file?  That is not important.  You can sign
the file on XP and it will work fine.  The issue is the machine where
you’re loading the driver.

I need to install this update in my macine to overcome this code:52
error ?

If your test machine does not have Win 7 SP1 with updates, then it does
not understand SHA2 certificates.  You’ll need the update. 
Alternatively, you could turn off the driver signing requirement by using
   bcdedit /set testsigning on
and restarting the machine.  That will get you through your testing. 
Remember, the driver files you submit to WHQL do not have to be signed. 
Only the cabinet containing the whole package of stuff needs to be signed.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Hi tim,

i have updated the https://www.microsoft.com/en-us/download/confirmation.
aspx?id=36325.

i have tried in other win7 x64 bit …driver were loading without issue…

But in this machine i cant load the driver ,got code:52…

Control Panel\System and Security\Windows Update\Change settings … here
also i ve given for updates " automatically ’ also given…

Control Panel\System and Security\Windows Update … checking for updates
also i ve clicked…" an error occured while checking for new updates for
your computer "

Regards,
prabhakar v

On Tue, Oct 17, 2017 at 12:28 AM, xxxxx@probo.com
wrote:

> Prabhakar V wrote:
> >
> > when i run signtool for verify i.e to check the “Microsoft Code
> > Verification Root” and used the hash of file is “sha1”.( It was there).
>
> That is merely showing you the SHA1 hash of the file being signed, in
> case you need to verify that it is the correct file. Your certificate
> is encoded with SHA2, as are all EV certificates:
>
> DigiCert EV Code Signing CA (SHA2)
>
>
> > I have used win 7 x64 bit pro SPI.
>
> Do you mean, for signing the file? That is not important. You can sign
> the file on XP and it will work fine. The issue is the machine where
> you’re loading the driver.
>
>
> > I need to install this update in my macine to overcome this code:52
> > error ?
>
> If your test machine does not have Win 7 SP1 with updates, then it does
> not understand SHA2 certificates. You’ll need the update.
> Alternatively, you could turn off the driver signing requirement by using
> bcdedit /set testsigning on
> and restarting the machine. That will get you through your testing.
> Remember, the driver files you submit to WHQL do not have to be signed.
> Only the cabinet containing the whole package of stuff needs to be signed.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

On Oct 16, 2017, at 12:41 PM, xxxxx@gmail.com wrote:
>
> i have updated the https://www.microsoft.com/en-us/download/confirmation.aspx?id=36325 https:.

Do you mean you have installed this on your test machine?

> i have tried in other win7 x64 bit …driver were loading without issue…
>
> But in this machine i cant load the driver ,got code:52…

How, exactly, are you loading the driver? Are you sure your correctly-signed driver package is getting copied over to the machine you are testing?

Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.</https:>

Hi tim,

Sry for the late reply…

>Do you mean you have installed this on your test machine?

Yes…

>How, exactly, are you loading the driver? Are you sure your
correctly-signed driver package is getting copied over to the machine you
are testing?

But this win7 x64 bit is newly installed… i have not installed any
updates… when we install our signed driver got code 52…

you have said that it has update of sha2… for that you should install
some updates to support and win7 should understand the sha2 alogorith to
load the driver…

Suppose when we give it to end customer it will fail with code 52

our signed driver has used used sha2 algorith…

What are the required and minimum updates should be need in win 7 x64 bit
OS to understand our signed driver…

Regards,
Prabhakar V

On Tue, Oct 17, 2017 at 1:21 PM, xxxxx@probo.com wrote:

> On Oct 16, 2017, at 12:41 PM, xxxxx@gmail.com
> wrote:
>
>
> i have updated the https://www.microsoft.com/
> en-us/download/confirmation.aspx?id=36325.
>
>
> Do you mean you have installed this on your test machine?
>
>
> i have tried in other win7 x64 bit …driver were loading without issue…
>
> But in this machine i cant load the driver ,got code:52…
>
>
> How, exactly, are you loading the driver? Are you sure your
> correctly-signed driver package is getting copied over to the machine you
> are testing?
> —
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

Hi tim,

Its enough to download this security updated to understand the sha2 signed
file by installing this updates (
https://www.microsoft.com/en-us/download/details.aspx?id=46148) and load
the driver /didnt get code 52 error.

Regards,
Prabhakar V

On Fri, Oct 20, 2017 at 8:38 AM, Prabhakar V wrote:

> Hi tim,
>
> Sry for the late reply…
>
> >>Do you mean you have installed this on your test machine?
>
> Yes…
>
> >>How, exactly, are you loading the driver? Are you sure your
> correctly-signed driver package is getting copied over to the machine you
> are testing?
>
> But this win7 x64 bit is newly installed… i have not installed any
> updates… when we install our signed driver got code 52…
>
> you have said that it has update of sha2… for that you should install
> some updates to support and win7 should understand the sha2 alogorith to
> load the driver…
>
> Suppose when we give it to end customer it will fail with code 52
>
> our signed driver has used used sha2 algorith…
>
> What are the required and minimum updates should be need in win 7 x64 bit
> OS to understand our signed driver…
>
>
> Regards,
> Prabhakar V
>
>
> On Tue, Oct 17, 2017 at 1:21 PM, xxxxx@probo.com
> wrote:
>
>> On Oct 16, 2017, at 12:41 PM, xxxxx@gmail.com
>> wrote:
>>
>>
>> i have updated the https://www.microsoft.com/
>> en-us/download/confirmation.aspx?id=36325.
>>
>>
>> Do you mean you have installed this on your test machine?
>>
>>
>> i have tried in other win7 x64 bit …driver were loading without issue…
>>
>> But in this machine i cant load the driver ,got code:52…
>>
>>
>> How, exactly, are you loading the driver? Are you sure your
>> correctly-signed driver package is getting copied over to the machine you
>> are testing?
>> —
>> Tim Roberts, xxxxx@probo.com
>> Providenza & Boekelheide, Inc.
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> Visit the list online at: http:>> lists.cfm?list=ntdev>
>>
>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>> software drivers!
>> Details at http:
>>
>> To unsubscribe, visit the List Server section of OSR Online at <
>> http://www.osronline.com/page.cfm?name=ListServer&gt;
>>
>
></http:></http:>

> Its enough to download this security updated to understand the sha2 signed file by installing this

updates ( https://www.microsoft.com/en-us/download/details.aspx?id=46148) and load the driver
/didnt get code 52 error.

Yes, Win7 SP1 with KB3033929 installed is sufficient.


Gabe

xxxxx@gmail.com wrote:

>>How, exactly, are you loading the driver?  Are you sure your
correctly-signed driver package is getting copied over to the machine
you are testing?

But this  win7 x64 bit is newly installed… i have not installed any
updates… when we install our signed driver got code 52…

Right.  That’s what we told you would happen.

you have said that it has update of sha2… for that you should
install some updates to support and win7 should understand the sha2
alogorith to load the driver…

No.  Windows 7 with Service Pack 1 and the KB3033929 update will
understand SHA2.  If they have automatic updates turned on, then they
will have KB3033929.

Suppose when we give it to end customer it will fail with code 52 

our signed driver has used used sha2 algorith…

What are the required and minimum updates should be need in win 7 x64
bit OS to understand our signed driver…

We’ve said this over and over and over.  Windows 7 with Service Pack 1
and KB3033929.  Most corporate users have automatic updates turned on,
so this is not an issue.

The alternative, of course, is for you to go buy an SHA1 code-signing
certificate (if you can find one), and sign a package specially for
non-updated Windows 7 users.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.