Microsoft introduces group policy to prevent Windows Update issues like KB5044284

Major Server Upgrade Issue with Microsoft’s KB5044284 Update

Recently, a significant problem occurred involving Microsoft’s Windows 11 update, KB5044284, which was mistakenly distributed to Windows Server 2019 and Server 2022. This oversight has drawn criticism from third-party Application Management Manufacturers (AMMs), particularly from Heimdal, which attributed the error to Microsoft.

On the same day the issue arose, Microsoft confirmed that the latest server version had indeed been provided as an optional update for both Windows Server 2022 and Windows Server 2019. Although no immediate clarification was given, it is widely believed that the misclassification of this client operating system update as a server update contributed to the confusion and subsequent problems.

Microsoft’s Official Response

In a recent update on its Windows health dashboard, Microsoft provided clarity on the situation. They affirmed that feature updates should be regarded as “optional”rather than “recommended.”The company detailed two scenarios that were identified:

Microsoft states:

• Automatic Upgrades: Certain devices unintentionally upgraded to Windows Server 2025 (KB5044284) in environments utilizing third-party products to manage updates. Users are advised to review their update management tools to ensure they are configured to avoid deploying feature updates automatically. This issue has since been mitigated.
• Banner Notification: An upgrade to Windows Server 2025 was presented via a notification banner on the device’s Windows Update settings page. This banner was aimed at organizations wishing to perform an in-place upgrade, and Microsoft has resolved this scenario as well.

The feature update for Windows Server 2025 is classified as an Optional installation under DeploymentAction=OptionalInstallation. It is vital for patch management tools to interpret feature update metadata in this manner.

Future Preventative Measures

To avert similar mishaps moving forward, Microsoft has outlined its ongoing initiatives. The tech giant is collaborating with third-party AMMs to establish best practices and recommends the introduction of a new group policy “hold”setting that allows organizations to specify the target Feature Update version.

Next Steps: Microsoft is actively working with third-party providers to enhance update processes. By setting the target version to “hold” in the Group Policy titled “Select the target Feature Update version,” organizations can manage the visibility of the feature update offer banner. More information regarding this group policy will be available shortly in updated documentation.

For further information regarding the situation, you can reference the specific issue on Microsoft’s official Windows health dashboard.

For additional insights and resources, visit Neowin.