NDIS network filtering driver signature issue

Question

NDIS network filtering driver signature issue: If the sys and cat files in the cab package are not signed by the EV certificate, submitting them to the Microsoft website for signature will succeed; If the sys and cat files are first signed by the EV certificate and then submitted to the Microsoft website for signature, an error will be reported in the Scanning step. The error log file content is as follows:

Scanning Notes

{"code":"4001","details":{"errorInfo":"BlockingDetectionFound"},"innerError":null}

Answer 1

Hello there,

The error you are encountering during the scanning step of the Microsoft website signature submission process indicates that a blocking detection has been found. This means that there is an issue with the files you are submitting, which is preventing the successful completion of the signature process.

Here are a few things to check and consider to resolve the NDIS network filtering driver signature issue:

Check the EV Certificate: Ensure that the EV (Extended Validation) certificate used for signing the sys and cat files is valid and has not expired. Also, confirm that the certificate is issued by a trusted Certificate Authority (CA).

Verify File Integrity: Double-check the integrity of the sys and cat files after signing them with the EV certificate. Ensure that the signing process did not alter the contents or introduce any errors.

Check Submission Process: Review the submission process you are following on the Microsoft website. Ensure that you are following the correct steps and providing all the required information accurately.

Contact Microsoft Support: If you are still encountering the blocking detection error after verifying the above points, consider reaching out to Microsoft Support for assistance. They may be able to provide more specific insights into the issue and guide you through the correct signature submission process.

Driver Compatibility and Requirements: Ensure that the NDIS network filtering driver meets all the compatibility and requirements for driver signing as per Microsoft guidelines. For example, it should be compatible with the target Windows version and follow the necessary security guidelines.

Check for Known Issues: Search for any known issues related to driver signing and EV certificates in Microsoft's developer documentation and forums. There might be specific considerations or workarounds that apply to your scenario.

Test on a Test System: Before submitting the driver for signature on a production system, consider testing the driver on a separate test system to ensure it works as expected and passes the signature submission process.

Driver signing and submission for Windows can be a complex process, and small mistakes can lead to signature issues. It's crucial to follow the necessary guidelines and thoroughly test the driver before submission. If you are unsure about any step in the process, seeking help from Microsoft Support or experienced developers might be beneficial.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

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