What kind of driver execption doc should I create in the Hardware Submition for getting a WHQL sign.

Question

Guidance on what constitutes as an exception and producing the justification document can be found here: https://go.microsoft.com/fwlink/?linkid=2348723. But I cannt get the specifify example doc and the structure of submitting files.

Answer 1

For now, DriverExceptionDocGenerator tool is not available. So how can I make sure my DriverException.json is correct.

Answer 2

For now, DriverExceptionDocGenerator tool is not available. So how can I make sure my DriverException.json is correct.

Answer 3

For a WHQL-signed legacy printer driver submission, the required “driver exception” justification document is a JSON file named DriverException.json that follows the Microsoft schema and is placed in a specific location in the submission package.

Key points for the exception/justification document:

1. File type and name
   • The justification must be a JSON file.
   • The expected file name is DriverException.json.
   • The JSON must comply with the Microsoft-defined schema. The recommended way to ensure this is to use the DriverExceptionDocGenerator tool when it becomes available.
2. When the document is required
   • Required for every printer driver submission, including:
     1. New printer drivers
     2. Driver updates
     3. Security updates
     4. Architecture additions (for example, ARM64)
   • Submissions without a justification JSON are automatically blocked and rejected during manual review.
3. What the document must justify (exceptions) From 15 January 2026, printer driver submissions are only signed/published if they fall into specific exception categories. The JSON must clearly justify that the submission meets one of these allowed categories. a) New printer drivers must show that at least one of the following is true:
   • Device cannot support Mopria, or
   • Device is a Fax device, or
   • Submission is adding an ARM64 version, or
   • Target OS is Windows 10 22H2 or earlier, or
   • Target OS is Windows Server 2022 or earlier.
   b) Driver updates must show all of the following:
   • No new HWIDs are added.
   • No new functionality is added.
   • The submission includes the submission ID of the existing driver it is replacing/updating.
   • And at least one of:
     • It is a security update, or
     • Device is a Fax device, or
     • It adds an ARM64 version, or
     • It targets Windows 10 22H2 or earlier, or
     • It targets Windows Server 2022 or earlier.
   If the JSON indicates a DriverUpdate, it must include PreviousSubmissionId. Missing this field causes immediate rejection, and adding new HWIDs in a DriverUpdate submission also causes automatic rejection.
4. Placement of DriverException.json in the submission
   • WHQL submissions (HLK-based)
     • Place the JSON under the /Supplemental folder in the HLK package:

              HLKPackage/
                HLKFiles/...
                Supplemental/
                  DriverException.json
                  AdditionalDocumentation.pdf (optional)
       

   • Attestation submissions
     • Place the JSON directly inside the driver folder in the submission root:

              DriverSubmission/
                DriverFiles/...
                  DriverException.json
                  SupportingDocument.docx (optional)
       

5. Using DriverExceptionDocGenerator
   • The tool will:
     • Run interactively (prompt-driven) or non-interactively (via parameters).
     • Produce a JSON document aligned to the Microsoft schema.
     • Validate required fields and formatting.
   • It should be used for all printer driver submissions to reduce rejection risk.

In summary, for WHQL signing of a legacy printer driver, create a DriverException.json that:

• Conforms to the Microsoft schema (preferably generated/validated by DriverExceptionDocGenerator),
• Explicitly documents which 2026 exception criteria the submission meets (new driver vs. driver update rules),
• Includes PreviousSubmissionId for updates, and
• Is placed in /Supplemental (WHQL/HLK) or the driver folder (attestation) as shown above.

---

References:

• Legacy Printer Driver Submission Process
• Create a new hardware submission