Launch of Windows Server 2025 Amid Controversies
This week marked the official launch of Windows Server 2025, alongside its companion, System Center 2025. Microsoft also released a comprehensive list of validated processors and confirmed that this version follows the Long-Term Servicing Channel (LTSC) model.
Installation Issues Reported by IT Administrators
However, the rollout has not proceeded without complications. Reports from IT professionals reveal that many systems are automatically upgrading from Windows Server 2022 to Windows Server 2025 without prior consent. This unexpected transition has led to significant concern and frustration within the IT community.
Root Cause: A Mistaken Update Classification
The underlying issue appears to involve KB5044284, which is the October Patch Tuesday update for Windows 11, rather than an update specific to the Server line. An employee from Heimdal, a cybersecurity firm, has provided insights into the situation through discussions on Reddit.
Andrei from Heimdal stated, “I sincerely apologize for the disruption this update has caused. Thanks to your reports, our team was able to identify the issue swiftly and block the update across all server policies to avert further automatic upgrades.”
He further explained, “On November 5th, we were alerted by a customer regarding unexpected upgrades linked to Windows Server 2025. By later that day, we identified that the Windows Update API mistakenly classified the Server 2025 upgrade under KB5044284.”
Our Analysis and Fix: Upon investigation, we discovered a mismatch in our patching repository, where the GUID for the Windows Server 2025 upgrade was incorrectly associated with the KB5044284 entry typically reserved for Windows 11 updates. This mislabeling originated from Microsoft’s side, complicating the update classification and its release speed. After confirming the KB’s reference with Microsoft’s database, we established that it pertains specifically to Windows 11, not Windows Server 2025.
Currently, around 7% of our client base has been impacted by this upgrade mishap. In response, we have acted swiftly to block KB5044284 across all server group policies.
Official Release Context
Significantly, Microsoft has not assigned a distinct KB article number for the Windows Server 2025 release, which is specifically designated as build 26100.1742.
Heimdal’s Role and Potential Implications
For those unfamiliar, Heimdal provides a robust Patch and Asset Management Module (AMM) that allows IT professionals to manage and deploy updates through Group Policy settings. At this stage, it remains unclear whether other similar AMMs are experiencing similar issues.
To stay updated on the developments regarding Windows Server 2025 and related systems, follow the source provided for ongoing insights.
Related Articles:
Microsoft Weekly: Update on Bugs in Windows 11 24H2 and Final Builds
9:01
Microsoft explains why TPM and Secure Boot are mandatory for Windows 11 in 2024-2025
11:43
AMD discourages Windows 10 installation on select Ryzen PCs despite Microsoft support
11:27
Leave a Reply