Microsoft can now remotely roll back problematic Windows drivers

Today, Microsoft announced a new capability to swiftly resolve problematic driver issues on Windows devices. The new Cloud-Initiated Driver Recovery feature can automatically roll back problematic drivers on affected PCs without requiring users or hardware partners to take action. This new capability will be supported for drivers distributed through Windows Update.

Until now, when a driver distributed through Windows Update causes problems, the hardware partner must submit an updated driver to Microsoft. In some cases, users may need to manually uninstall the problematic driver. This process can leave affected PCs running a low-quality driver for an extended period.

With the new Cloud-Initiated Driver Recovery feature, when Microsoft identifies a driver with quality issues during its Driver Shiproom evaluation process, it can now trigger a recovery action from the cloud and replace that driver with a previously working version. The recovery action is delivered through the existing Windows Update pipeline, so it does not require a new client agent installation on Windows or additional partner software.

Here's how this new feature works:

• The recovery process works by first identifying a previously published driver that has quality issues.
• Microsoft then creates a recovery request targeting the specific driver and its associated shipping labels.
• Windows Update delivers the rollback instruction to affected devices, checks whether an approved replacement driver is available, and then uninstalls the rejected driver.
• The replacement will be either the previously installed version or the next best approved version available through Windows Update.
• If an approved Driver Shiproom driver cannot be found, Cloud-Initiated Driver Recovery will not be attempted on that device.

Hardware partners will continue to receive notifications through existing shiproom communication channels when a driver is rejected during flighting or gradual rollout.

Microsoft is planning to manually validate and test Cloud-Initiated Driver Recovery on selected shipping labels between May and August 2026. The feature is targeted to be automatically included when a driver is rejected during flighting or gradual rollout starting in September 2026.