Driver windows update submission failed - Messaure ID 19554065 failed.

Arron Yen 0 Reputation points
2026-04-09T03:16:40.14+00:00

Hi,

We tried to submission a windows update but the submission result was failed.

The failed messages is below:Rejection Theme: Measure Failure Rejection Reason: Device Class Measure Failure Provide Measure ID(s): 19554065 ADO bugId: 61682867: Bug ID(s) and Partner ID(s): Link to documentation: Link to reliability report (if applicable): Details: [DriverAutoPilot][Rid79]: APP_FT_LaunchApproval_Activity: Biometric Engine Result: REJECTED. REASON: Measure ID 19554065 failed launch thresholds with Status:'fail' & Value: 88.056206088993 & Target: 90. Rejected. No data for measure ID 22162022.

We tried to re-submit but still got the same failed.

This failed only occured on the certain CHID and other CHIDs didn't encounter this error (WU submission pass for other CHIDs).

Have any ideas to fix this problem?

Thanks!

Microsoft Partner Center | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-04-09T03:16:51.5266667+00:00

    The failure is caused by a reliability measure not meeting the required launch threshold for that specific CHID. The report shows:

    • Measure ID 19554065 has Status fail, Value 88.0562, and Target 90.
    • This is evaluated as APP_FT_LaunchApproval_Activity: Biometric Engine Result: REJECTED.
    • The same driver passes for other CHIDs, so the failure is specific to the affected CHID’s in‑field reliability/telemetry.

    To proceed:

    1. Retrieve and review the Reliability Measure Failure Report
      • For a driver that fails a reliability measure, a bug is created and assigned.
      • That bug contains a RejectionReports.zip attachment.
      • Inside RejectionReports.zip, open ReliabilityMeasureReport.pdf.
      • This report provides detailed data for Measure ID 19554065 (and any related measures) at the time of flight completion and during release monitoring.
    2. Use the report to identify what must be improved
      • Focus on the section for Measure ID 19554065 and the affected device class/CHID.
      • Determine what scenario or failure type is driving the metric below the target (for example, crashes, hangs, or other biometric engine failures on that CHID).
      • Compare with CHIDs that passed to see what is different (hardware, firmware, configuration, or usage pattern).
    3. Address the underlying reliability issues
      • Based on the failure details in ReliabilityMeasureReport.pdf, update the driver, firmware, or configuration for that CHID to reduce the failure rate.
      • Validate internally (and, if possible, via controlled flighting) that the measure value for 19554065 improves to meet or exceed the target (≥ 90 in this case).
    4. Resubmit after reliability has improved
      • Once the underlying issues are mitigated and internal validation shows acceptable reliability, resubmit the driver for that CHID.
      • If the measure still fails after changes, re‑check the updated reliability report attached to the new bug.
    5. Engage Dashboard/Partner support if the report data looks incorrect
      • If the Reliability Measure Failure Report appears inconsistent with your own telemetry or you believe the measure is being evaluated incorrectly for that CHID, open a case with Partner Center dashboard technical support and reference the ADO bug ID and Measure ID 19554065 so they can investigate the backend data.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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