Security & Infrastructure Tools
Microsoft fixes Windows Autopatch bug installing restricted drivers
Microsoft fixed a Windows Autopatch bug in the EU that caused restricted driver updates to install on some Windows 11 devices (versions 23H2, 24H2, 25H2) despite IT policies, potentially causing reboots or failures. The fix is service-side and requires no action from customers. The article also notes a recent Windows Server 2019/2022 upgrade-to-2025 issue and new Office installation problems on Windows 365 after a service update.

Microsoft fixes Windows Autopatch bug deploying restricted drivers
OverviewA Windows Autopatch issue has been resolved that caused driver updates, restricted by IT-admin policies, to be deployed on a limited set of Autopatch-managed devices in the European Union. The problem affected only a small portion of client Windows installations and occurred despite configurations intended to prevent such deployments. Microsoft implemented a service-side fix, meaning no action was required from affected customers.
Details of the incident
- Scope: The bug appeared on a subset of Autopatch-managed devices within the European Union region.
- Affected platforms: Client Windows versions, specifically Windows 11 25H2, Windows 11 24H2, and Windows 11 23H2.
- Symptoms: Affected devices received and installed recommended driver updates without user approval, contrary to driver deployment policies configured by IT administrators. Some devices experienced unexpected reboots or more severe system issues depending on the drivers involved.
- Server-side remediation: Microsoft states that the issue has been resolved through a service-side fix and that no client-side updates or user actions are required to recover normal operation.
Context and related actions
- Prior fixes and acknowledgments: In the months leading up to this incident, Microsoft addressed other Windows update-related problems. For example, in April 2026, the company resolved issues tied to Windows Server upgrades moving systems unexpectedly to Windows Server 2025. These events underscore ongoing challenges with automatic or policy-driven updates across Windows environments.
- Public notices and emphasis: The issue was first identified and discussed within a service alert circulated by industry observers and community members, including well-known IT administration figures, highlighting the risk of policy-contradicting updates during Autopatch operations.
- Additional service behavior changes: Around the same broader period, Microsoft noted that some customers experienced difficulties installing Office on Windows 365 devices as a consequence of a recent service update, signaling that multiple product areas were undergoing updates that affected deployment behavior.
Timeline and notable dates (absolute)
- September 2024: Microsoft publicly acknowledged a related issue where Windows Server upgrades occurred in ways that could violate licensing expectations, based on widespread reports from server administrators.
- April 2026: Microsoft resolved a separate known issue related to Windows Server automatic upgrades that could unexpectedly move systems to Windows Server 2025.
- May 12–14, 2026: The Autonomous Validation Summit took place, highlighting advances in autonomous, context-aware validation and its role in identifying exploitable gaps and confirming remediation controls.
- May 13, 2026: Public reporting and updates on the Windows Autopatch driver deployment issue were published, confirming the service-side fix and the absence of required customer action.
Impact assessment for administrators
- Immediate effect: No ongoing remediation steps are required for affected organizations; the driver deployment problem has been addressed on the service side.
- Policy verification: IT departments may wish to review driver deployment policies to ensure alignment with policy configurations and to monitor for any future anomalies in Autopatch behavior.
- Cross-product considerations: Organizations should remain mindful of related service updates that may influence deployment behaviors across other Microsoft products, including Office on Windows 365 devices.
What changed and what to watch for
- Change implemented: A server-side fix was deployed to stop restricted driver updates from bypassing administrator controls on EU Autopatch devices.
- What to monitor: If any unexpected driver installations or policy deviations reappear, administrators should verify policy configurations and review Autopatch rollout logs. While the current issue is resolved, ongoing updates to Windows and related services can introduce new behavioral changes that affect deployment and compliance.
SummaryMicrosoft has resolved a Windows Autopatch bug that could cause restricted driver updates to install on EU-managed devices despite administrative policies. The resolution was implemented on the service side, with no client-side action required. This follows a period of multiple update-related challenges across Windows and related services, underscoring the importance of monitoring Autopatch and policy configurations as part of routine IT operations. The broader context includes ongoing updates and validations discussed around the Autonomous Validation Summit, as well as separate incidents affecting Windows Server upgrades and Office deployments on Windows 365 devices.


