How to fix wu Submission issue?

Measure 26387215 is a systemic Plug and Play (PnP) installation quality measure. The submission is rejected because too many machines fail to install the driver successfully.

To fix the Windows Update (WU) submission issue, use the telemetry reports referenced in the rejection to identify and remediate the installation failures, then resubmit and re‑flight the driver:

1. Understand the failing measure (26387215)
   • Measure 26387215 is “Percent of machines where the driver install process completes successfully – Plug and Play Failures / Driver Installation Failures.”
   • It is calculated over a 30‑day sliding window as:
     • Successful installs = count of machines with successful PnP install events.
     • Total installs = count of machines that started the driver install process.
     • PNP Success Rate = Successful installs / Total installs.
   • Passing criteria: ≥ 95% of machines must install the driver successfully.
   • The driver is rejected because the current value of this measure is below 95%.
2. Open and read the Plug and Play extended flight report
   • Use the “driver flight report” bug mentioned in the rejection (search by Submission ID in Collaborate) and open the Plug and Play extended flight report.
   • In that report, review these sections:
     1. Title – confirm driver, version, and shipping label match the failing submission.
     2. Summary and Instructions – read the guidance on how the data was collected and how to interpret it.
     3. Driver Rejection Reason – this is the key section:
        • Note the failing measure ID (26387215) and the numerical passing criteria vs. the driver’s current value.
        • Review the top failures list: Problem Code, Status, and Machine Instances. This shows which PnP/installation errors are driving the failure.
     4. Measure Data – drill into the detailed rows:
        • For each failing metric (PnP failures, driver installation failures, post‑install PnP errors), review:
          • Problem Code / Install Error
          • Problem Code Description
          • Problem Status Description
          • INF Matching ID
          • Machines and Instances
        • Use this to identify:
          • Which INF(s) are problematic.
          • Which error codes are most common.
          • Whether failures are concentrated on specific hardware IDs or OS versions.
3. Correlate with cohort and reliability reports (if present)
   • If a Cohort Failure Report or Reliability measure failure report is linked for the same submission, open it to see whether failures are concentrated in specific cohorts:
     • In the Cohort Failure Report, look at each failing cohort’s:
       • Hardware ID, CHID, OS version.
       • Measure ID, result, passing criteria, status, and machine count.
     • In the Reliability measure failure report, check whether systemic reliability measures (stop errors or live kernel dumps) are also failing for the same cohorts.
   • Use this to decide whether to:
     • Restrict targeting (exclude problematic HW/OS cohorts) for the next flight, and/or
     • Fix bugs in the driver for those cohorts.
4. Diagnose and fix the driver issues indicated by the PnP errors
   • For each dominant Problem Code / Install Error from the Measure Data section:
     • Look up the code in the Device Manager Problem Codes documentation referenced in the measure description.
     • Investigate the corresponding driver INF, installation logic, and device‑class behavior.
   • Typical remediation actions (guided by the error codes and INF IDs in the report) include:
     • Correcting INF issues (e.g., incorrect HW IDs, missing dependencies, invalid directives).
     • Fixing driver bugs that cause PnP failures or post‑install PnP error codes.
     • Adjusting targeting so the driver is not offered to unsupported or unstable hardware/OS combinations.
5. Validate improvements and re‑submit
   • After implementing fixes or narrowing targeting:
     1. Create a new driver submission and flight it to a limited audience.
     2. Monitor the driver flight report and Plug and Play extended flight report for the new submission.
     3. Confirm that Measure 26387215 now meets the passing criteria (≥ 95% success rate) over the 30‑day window.
   • Once the measure passes and no other systemic or device‑class measures fail, the WU submission should progress beyond the “Systemic Measure Failure” rejection.

This process aligns with how systemic measures are used to evaluate driver quality: each measure’s current value is compared against its passing criteria, and any failing measure (such as 26387215) must be addressed via analysis of the flight and cohort reports before the driver can be approved for broader rollout.

References:

• Plug and Play extended flight report
• Percent of machines where the driver install process completes successfully
• Machines that reported a Plug and Play (PnP) error code within two days of installing a driver update
• Overview of the Microsoft driver measures
• Reliability measure failure report
• Cohort Failure Report