Intune Driver update – Device not reporting correct status

Microsoft Intune Driver Update Management streamlines how IT admins deploy and monitor Windows driver updates. However, some devices may report incorrect compliance status even after successfully installing the driver. In this guide, we explain why devices get stuck in the “offering” state, how to confirm installation, and the steps to force a full telemetry sync to ensure accurate reporting in Intune.

Issue: Intune Driver Updates Reporting Incorrect Status

We deployed driver updates to devices managed by Microsoft Intune, but many endpoints remain stuck in the “Offering” state for an extended period. The compliance status does not change even after 2–3 weeks, creating confusion for IT admins monitoring update progress.

Interestingly, this issue occurs only with driver updates scheduled for a future date, while immediate deployments report status correctly.

Observation: Driver Installed but Incorrect Status Reported

The driver update was successfully installed on the affected devices, as confirmed through Device Management. Despite this, the Intune compliance report continued to show an incorrect status, leaving the devices marked as non‑compliant.

This mismatch highlights a reporting issue where the installation state on the endpoint does not synchronize properly with Microsoft Intune, resulting in inaccurate compliance visibility for admins.

Solution: Force Full Telemetry Sync in Intune

As advised by Microsoft, we resolved the reporting mismatch by running a command to force a full telemetry sync on the impacted devices. This ensures that the device’s actual driver installation status is correctly reported back to Microsoft Intune.

• The full telemetry sync may take up to 48 hours to complete.
• The command does not generate any output when executed.

Command to run on affected devices:

compattelrunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun ent

Summary and Best Practices

This issue highlights a common challenge in Intune Driver Update Management: devices may successfully install drivers but fail to report the correct compliance status due to delayed telemetry synchronization. Running a full telemetry sync ensures that Intune reflects the actual installation state, though admins should allow up to 48 hours for reporting to update.

To minimize similar issues in the future, consider these best practices:

• Monitor telemetry syncs regularly to ensure accurate compliance reporting.
• Schedule driver updates carefully, avoiding unnecessary delays that may cause devices to remain in the “Offering” state.
• Leverage Intune reporting tools to cross‑check installation status against Device Management.
• Communicate with end users proactively, providing clear instructions for remediation if compliance status appears incorrect.
• Submit feedback to Microsoft when recurring reporting mismatches occur, as these may indicate service‑level improvements needed.

Related Posts

• Autopilot Device Preparation Error 80180003
• BitLocker : The encryption method of the OS volume doesn’t match the BitLocker policy
• Intune Bulk Enrollment with Provisional Package failed with Error 0xCAA2000C