none
Microsoft Signed Driver on Win10 Can't Start RRS feed

  • Question

  • Description of technical issues:            The filesystem filter driver developed by our company has signed EV code, and then it has been implemented in Microsoft Partner Center (https://partner.microsoft.com/zh-cn/dashboard/hardware/Search).            New hardware submission, Microsoft signed through. In the client machine win10 system, it can not run, and the "certificate has been reported to the issuer directly revoked" error is reported.            Note: After Microsoft hardware signature, the special product ID displayed on the website is 14319568203333741, the shared product ID is 1152921504607621050, and the submitted ID is 1152921504627891626.            The driver screenshot of Microsoft's signature is as follows:

    Problem-prone environments (software/hardware):            Win10, the specific version is: 10.0.17134.1.            Problem Reproduction Steps:            Every time the client environment starts the driver, it will appear.            Preliminary analysis:            EV certificate manufacturer technicians analysis is a cat file after Microsoft's signature has passed, showing non-driver cross, so it can not run, as shown in the following figure:

    Supplementary notes (error screenshots):

    Friday, December 28, 2018 12:54 AM

All replies

  • Hi ,

    Since the problem is more related to driver, I'll help you to move this thread to the Windows Hardware WDK and Driver Development Forum. You could get more professional support there.

    Thank you for your patience.

    Best regards,

    Roy

     


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, December 28, 2018 6:04 AM
  • If you have Microsoft's signature on your driver, then it shouldn't matter whether you have your own signature or not.  Are you modifying the certificate chain after you get the package back from Microsoft?

    It is possible you need to open a Microsoft support ticket about this.  If Windows thinks your corporate certificate has been revoked, that's a problem you need to resolve.


    Tim Roberts | Driver MVP Emeritus | Providenza & Boekelheide, Inc.

    Sunday, December 30, 2018 8:25 AM