Windows 10 driver install fails in normal mode

Pyokkimies, Esa-Pekka 1 Reputation point
2022-04-13T07:51:13.527+00:00

We have a problem when trying to install our driver in windows 10. The install works in test mode
but not in normal mode. We have the same driver working in windows 8.1.

The error message in normal mode is as follows:

     dvi: {_SCAN_FILE_QUEUE} 19:40:42.952
     flq:      ScanQ flags=22
     flq:           SPQ_SCAN_FILE_VALIDITY
     flq:           SPQ_SCAN_PRUNE_COPY_QUEUE
     flq:      ScanQ number of copy nodes=1
     sig:      {_VERIFY_FILE_SIGNATURE} 19:40:42.952
     sig:           Key      = sgravpn.sys
     sig:           FilePath = C:\WINDOWS\system32\DRIVERS\sgravpn.sys
     sig:           Catalog  = C:\WINDOWS\System32\DriverStore\FileRepository\sgravpn.inf_amd64_03847105839352eb\sgravpn.cat
!    sig:           Verifying file against catalog 'sgravpn.cat' failed.
!    sig:           Error 2: The system cannot find the file specified.
     sig:      {_VERIFY_FILE_SIGNATURE exit(0x00000002)} 19:40:42.952
     flq:      ScanQ action=2 DoPruning=32
     flq:      ScanQ end Validity flags=22 CopyNodes=1
     dvi: {_SCAN_FILE_QUEUE - exit(0x00000000)} 19:40:42.967

Using signtool to verify the driver against the catalog file shows no issues:

S:\Src\...\released_drivers\win10\x64\interceptor>signtool verify /v /pa /c sgravpn.cat sgravpn.sys

Verifying: sgravpn.sys
File is signed in catalog: S:\Src\...\released_drivers\win10\x64\interceptor\sgravpn.cat
Hash of file (sha1): 9CAFD2FF6286F899694F5061AB6E729553E57396

Signing Certificate Chain:
    Issued to: Microsoft Root Certificate Authority 2010
    Issued by: Microsoft Root Certificate Authority 2010
    Expires:   Sun Jun 24 00:04:01 2035
    SHA1 hash: 3B1EFD3A66EA28B16697394703A72CA340A05BD5

        Issued to: Microsoft Windows PCA 2010
        Issued by: Microsoft Root Certificate Authority 2010
        Expires:   Sun Jul 06 22:50:23 2025
        SHA1 hash: C01386A907496404F276C3C1853ABF4A5274AF88

            Issued to: Microsoft Windows Hardware Compatibility Publisher
            Issued by: Microsoft Windows PCA 2010
            Expires:   Thu Sep 15 20:08:08 2022
            SHA1 hash: 02D830D94EF0A229921DCBABE77FE0710FDB400A

The signature is timestamped: Thu Feb 10 14:35:26 2022
Timestamp Verified by:
    Issued to: Microsoft Root Certificate Authority 2010
    Issued by: Microsoft Root Certificate Authority 2010
    Expires:   Sun Jun 24 00:04:01 2035
    SHA1 hash: 3B1EFD3A66EA28B16697394703A72CA340A05BD5

        Issued to: Microsoft Time-Stamp PCA 2010
        Issued by: Microsoft Root Certificate Authority 2010
        Expires:   Mon Sep 30 20:32:25 2030
        SHA1 hash: 36056A5662DCADECF82CC14C8B80EC5E0BCC59A6

            Issued to: Microsoft Time-Stamp Service
            Issued by: Microsoft Time-Stamp PCA 2010
            Expires:   Tue Feb 28 21:05:15 2023
            SHA1 hash: F32C1EFE217933C7C8536693EB2437BE73E95793

Successfully verified: sgravpn.sys

Number of files successfully Verified: 1
Number of warnings: 0
Number of errors: 0

We have gone through the certification process a couple of times but the result is the same.
This is blocking the release of our windows 10 driver.
Any ideas?

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,818 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,636 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,711 Reputation points
    2022-04-20T03:02:39.95+00:00

    Hi @Pyokkimies, Esa-Pekka

    As the driver works in test mode this is to blame the certification process for the driver in question.

    To submit a driver package for certification, you must sign the package with a certificate that you obtain from a trusted certification authority like VeriSign.Check if you have proceeded with this step.

    You will also need a cross-certificate, which is provided by Microsoft before releasing the driver to the public. Here is a link for a detailed description of the process that you must follow.

    Signing a Driver for Public Release https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/signing-a-driver-for-public-release

    Hope this resolves your Query!!

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

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

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.