Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

[Mayur P. <may...@gm...>]

Hello Jonathan,

We are using EV certificate for signing.

Thank you...

~Mayur

On Wed, Feb 28, 2018 at 10:20 PM, Carter, Jonathan <Jon...@id...>
wrote:

> Did you sign with an EV cert or a regular cert? You need EV for kernel
> mode drivers.
>
>
>
> *From:* Mayur Purandare [mailto:may...@gm...]
> *Sent:* Wednesday, February 28, 2018 12:56 AM
> *To:* lib...@li...
> *Subject:* Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on
> windows 10.
>
>
>
> Hello Jonathan,
>
>
>
> Thank you very much for the reply.
>
>
>
> I tried the way you suggested. However I am still getting the same error
> on windows 10.
>
>
>
> It is that I need it to be attested from Windows Hardware Developer
> Center?
>
>
>
> Can this driver be submitted to the Windows Hardware Developer Center as
> this is licenced under General Public License?
>
>
>
> Thanks..
>
>
>
> ~Mayur
>
>
>
> On Tue, Feb 27, 2018 at 11:08 PM, Carter, Jonathan <
> Jon...@id...> wrote:
>
> Here’s how I signed mine…
>
> First I made a CAT file for the INF because the one the wizard made was
> empty:
>
> -          Get Windows Driver Kit
>
> -          cd C:\Program Files (x86)\Windows Kits\10\bin\x86
>
> -          Inf2Cat /driver:C:\pathToYourINF /os:10_X64,10_X86,6_3_X64,6_3_
> X86,8_X64,8_X86,7_X64,7_X86
>
> -          This makes it valid for all windows versions
>
>
>
> Then I put that with my INF and signed the package.
>
> You should be able to right click it and install but you can also use
> DPINST
>
>
>
> Good luck
>
>
>
> *From:* Mayur Purandare [mailto:may...@gm...]
> *Sent:* Monday, February 26, 2018 11:21 PM
> *To:* Lib...@li...
> *Subject:* [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows
> 10.
>
>
>
> Hello,
>
>
>
> We are using libusb-win32 driver to communicate with our hardware.
>
>
>
> When we installed it on Windows 7, it showed a warning message for unknown
> published.
>
>
>
> To remove this warning we signed the driver with commercial certificate
> and the warning did not come thereafter.
>
>
>
> However, when we tried to deploy the same driver on Windows 10, it is
> showing the Error : "The windows cannot verify the digital signature for
> this device" code 52.
>
>
>
> Request you to please help on this.
>
>
>
> thank you..
>
>
>
>
>
> Regards
>
>
>
> Mayur
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
>