Microsoft has addressed a significant issue within its Windows Autopatch service, which inadvertently deployed restricted driver updates to a select group of managed Windows devices without the necessary approval protocols. This glitch primarily affected systems operating on Windows 11 versions 25H2, 24H2, and 23H2, leading to unexpected restarts and stability concerns for some users.
Windows Autopatch is designed to streamline the update process by automatically managing and deploying updates for Windows and Microsoft 365 applications across organizational devices. By utilizing a phased approach with update “rings,” it aims to minimize risks associated with patch management, relieving IT teams from the burden of manual testing and rollout.
However, the recent incident saw restricted or optional driver updates being installed without the required administrative authorization. This oversight allowed updates to bypass established controls, resulting in various issues, including unanticipated system restarts and potential instability or failures, depending on the drivers involved.
Server-side fix resolves the Windows Autopatch deployment problem
In response to the situation, Microsoft implemented a server-side fix, ensuring that users and organizations would not need to take any additional steps or install patches themselves. The company reassured stakeholders that the impact was limited, affecting only a small subset of devices managed by Autopatch rather than the entire user base.
“A limited subset of devices managed by Windows Autopatch in the European Union (EU) region might have received unexpected driver updates from Windows Update, despite administrative policies configured to restrict driver deployment,” Microsoft clarified. “This issue has been fixed through a service-side update. No client-side updates or further action are required from customers.”
Additionally, Microsoft acknowledged that some users are experiencing difficulties when attempting to install Office on Windows 365 machines. This complication appears to stem from a configuration change linked to a recent service update, inadvertently affecting the installation process for Office on these cloud-based devices.
