unable to submit windows drivers for attestation using partner center

Attestation submission requires several prerequisites and a correct package structure. The following checklist covers the main reasons attestation submissions fail in Partner Center and how to fix them.

1. Verify EV code signing and Partner Center registration
   • An extended validation (EV) code signing certificate must be associated with the Hardware Dev Center dashboard account before any attestation submission is possible.
   • Ensure registration in the Microsoft Windows Hardware Developer Program is complete and the EV certificate is correctly linked to the account.
2. Confirm attestation is supported for the driver scenario
   • Attestation signing is only supported on Windows 10 Desktop and later.
   • It supports Windows Desktop kernel-mode and user-mode drivers; it does not provide proper PE levels for ELAM or Windows Hello PE binaries. Those must be submitted as .hlkx packages with HLK/HCK logs.
   • Attestation-signed drivers are not Windows Certified and cannot be published to Windows Update for retail audiences. Use attestation only for testing scenarios or specific CoDev/Test Registry Key / Surface SSRK options.
3. Check driver folder naming and paths Attestation signing has strict requirements:
   • Driver folder names must:
     • Contain no special characters.
     • Be shorter than 40 characters.
     • Not use UNC file share paths.
   • Violating these rules can cause the Partner Center submission to fail or be rejected.
4. Create a valid CAB package structure Many attestation submission failures are caused by incorrect CAB layout:
   • All driver files must be inside subdirectories within the CAB, not at the root.
   • Each driver should have its own subdirectory containing its INF and related binaries.
   • If Partner Center reports errors such as:
     • “There are files at the root of the cabinet.”
     • “No .inf files found in driver directory/directories: XYZ.” then the CAB structure is wrong and must be rebuilt.
5. Sign the CAB with the EV certificate before submission
   • The CAB file must be signed with the EV certificate using the process recommended by the certificate provider.
   • Example SignTool command:

          SignTool sign /s MY /n "Company Name" /fd sha256 \
            /tr http://sha256timestamp.ws.symantec.com/sha256/timestamp \
            /td sha256 /v "C:\Echo\Disk1\Echo.cab"
     

   • After signing, submit this EV-signed CAB in Partner Center.
6. Submit via Partner Center hardware dashboard In the Partner Center hardware dashboard:
   • Sign in and select Submit new hardware.
   • In Packages and signing properties, provide a product name.
   • Leave test-signing options unchecked for attestation.
   • Under Requested Signatures, select the appropriate attestation signing options.
   • Submit and wait for processing (typically within five business days, depending on manual review).
7. Validate the signed driver after successful submission Once Partner Center completes attestation signing and the package is downloaded:
   • Extract the driver files.
   • Use SignTool to verify signatures, for example:

          SignTool verify Echo.sys
          SignTool verify /pa /ph /v /d Echo.sys
     

   • Optionally, check Enhanced Key Usages (EKUs) via the file’s Properties → Digital Signatures → Details → View Certificate → Details → Enhanced Key Usage.
8. If submission errors persist
   • Review any specific error messages on the submission page (e.g., file missing, package fails to open, Zip64 issues) and follow the documented remediation steps.
   • For issues not covered by these rules, use Support for Partner Center dashboard to open a technical support case.

References:

• Attestation sign Windows drivers
• Partner Center for Windows Hardware
• Driver signing options and best practices
• Create a new hardware submission
• Driver Signing Policy