Driver Signature verification failing on Windows 2012 and 2012R2 but not on Windows 2016 and 19

Yashraj Pinjari 1 Reputation point
2022-09-20T05:59:02.577+00:00

The driver files like .sys are signed with Digicert.
Using NSI script to create driver installation package
Have performed HLK tests and got Microsoft signature.
Again signed the driver with Digicert and sha256 algorithm
Driver installation and other operations are working fine but when we try to upgrade driver, Windows 2012 and 2012R2 give driver signature failure error.

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,529 questions
Windows Hardware Performance
Windows Hardware Performance
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Hardware Performance: Delivering / providing hardware or hardware systems or adjusting / adapting hardware or hardware systems.
1,541 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Wesley Li-MSFT 4,376 Reputation points Microsoft Vendor
    2022-09-21T03:10:47.45+00:00

    Hi @Yashraj Pinjari

    Thank you for posting your question to Microsoft Q&A forum.

    When a driver signing failure error occurs, is there a relevant Event log in event viewer?

    For driver development related questions, you can try the Hardware Dev Center forum for help.

    https://social.msdn.microsoft.com/Forums/windowshardware/en-US/home?forum=wdk

    Best Regards,
    Wesley Li

    0 comments
  2. Limitless Technology 43,931 Reputation points
    2022-09-23T10:13:06.353+00:00

    Hello there,

    Is the hardware on both the servers same?

    This issue might occur due to custom out-of-box-experience (OOBE) update.

    This OOBE update is installed through Deployment Imaging and Management (DISM) and has a special rename operation that replaces the main OOBE feature. This replacement causes the digital signature error.

    You can follow this article for more information https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-cannot-verify-the-digital-signature-for-this-file

    You can also try to Disable Driver Signature Enforcement and see if that helps.

    -----------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer--

    0 comments