Microsoft rolls out driver rollback

Microsoft said on May 12 it is introducing Cloud-Initiated Driver Recovery, a Windows Update capability that can remotely roll back problematic drivers already delivered to Windows devices. The feature lets Microsoft initiate a recovery action from the cloud when a driver is found to have quality issues, replacing it with a previously known-good version or another approved version available through Windows Update. (techcommunity.microsoft.com) The company said the process does not require action from end users or hardware partners. Microsoft described the feature in a post aimed at partners that publish drivers through the Hardware Dev Center portal. ### How does the rollback actually happen? Microsoft said the new process starts when a driver previously published through Windows Update is later identified as having quality problems during the company’s Driver Shiproom evaluation. (techcommunity.microsoft.com) In that case, Microsoft can create a recovery request from the Hardware Dev Center Driver Shiproom and target the affected driver and shipping labels. The Windows Update pipeline then sends a rollback instruction to affected devices, Microsoft said. The system first confirms that an approved replacement driver is available and then uninstalls the rejected driver. Devices that do not have a Driver Shiproom-approved replacement available will not attempt Cloud-Initiated Driver Recovery, according to Microsoft. (techcommunity.microsoft.com) ### What changes for PC makers and driver publishers? Microsoft said “no action is required” from partners when the cloud-initiated recovery process is used. The company said the capability is Microsoft-managed end to end and uses the existing Windows Update infrastructure rather than a new client agent or separate partner tool. (techcommunity.microsoft.com) Existing shiproom communication channels will carry notices to partners when a driver is rejected during flighting or gradual rollout, Microsoft said. That matters because Microsoft’s driver release process already uses approval windows and deferrals around major Windows update periods for drivers that need Microsoft approval. (techcommunity.microsoft.com) ### Why is Microsoft adding another recovery tool now? Microsoft said in November 2025 that it was building a broader set of Windows recovery features for large-scale outages and device failures. In that post, the company described quick machine recovery as a way to detect, diagnose and remediate boot-critical issues from the Windows Recovery Environment, and said preview management for that capability was coming through Windows Autopatch for managed devices. (techcommunity.microsoft.com) The May 12 driver rollback announcement extends that recovery approach to drivers delivered through Windows Update. Microsoft did not tie the new feature in the post to a specific outage, but it said the older remediation path often depended on a hardware partner submitting an updated driver or on users manually uninstalling the bad driver, leaving devices on a low-quality driver for an extended period. (techcommunity.microsoft.com) ### How does this fit with Microsoft’s existing update controls? Microsoft already uses safeguard holds and Known Issue Rollback in other parts of Windows servicing. Safeguard holds block feature updates from reaching devices with known compatibility or quality risks, while Known Issue Rollback is designed to reverse a targeted problematic change inside a Windows update without removing the full update. (techcommunity.microsoft.com) Intune’s driver update policies also give organizations a separate approval surface for driver and firmware updates, with automatic or manual approval workflows, Microsoft says. Those policies require managed devices, internet access to Microsoft endpoints and telemetry settings that allow reporting, according to Microsoft Learn documentation. (techcommunity.microsoft.com) ### Which systems and channels are involved next? Microsoft said the Cloud-Initiated Driver Recovery post is intended for partners that publish drivers through the Hardware Dev Center portal. The company said partners will receive notifications through existing shiproom channels as drivers are rejected during flighting or gradual rollout, and the rollback itself will continue to use the Windows Update pipeline. (learn.microsoft.com) Microsoft’s Windows release health hub and driver documentation remain the public places where IT administrators track known issues, safeguards and driver servicing guidance. The company’s May 12 post did not give a separate public timetable for broader availability beyond the rollout announcement to partners. (learn.microsoft.com) (techcommunity.microsoft.com) (learn.microsoft.com)