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>
>
>
>
> — 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>
></http:></http:></http:></http:>