MADRID, 12 Nov. (Portaltic/EP) –
Microsoft has pointed out that, in future updates published for Windows Server 2025 y Windows 11 (24H2), the versions will share the same KB update numbersbut will differentiate the deployments with “different sites and release notes links”, in order to avoid possible update failuressuch as the recent bug that caused computers running Windows Server 2022 to involuntarily upgrade to version 2025.
The American technology company has specific operating system versions such as Windows Server or Enterprise, focused on computers and systems framed in the business and work sector. In this sense, Microsoft released an update last October with which mistakenly caused PCs running Windows Server 2022 to be upgraded directly to Windows Server 2025, without prior notice.
Specifically, Microsoft has explained in its notifications page about Windows Server feature update Windows Server 2025 was released on November 1 as KB5044284. However, this was the same KB registration number used for updating Windows 11 October security patches, 24H2 version.
Therefore, these client and server Windows updates shared registration numbers, which led to Computers that used Windows Server 2019 and 2022 versions will end up installing the latest version 2025 involuntarilyby allowing the update thinking it was a security patch.
This accidental update may lead to problems for companies such as, for example, the programs they use are not compatible with the version of Windows Server 2025. In addition, as specified by Microsoft, the latest version of this system was released as a optional update in Windows Update.
After identifying this failure, identified mainly in Teams using third-party products to manage updating clients and serversMicrosoft has detailed that will make some changes to the way updates are classified and deployed, in order to avoid future similar errors.
Thus, the technology company has shared that, from now on, future updates published for Windows Server 2025 and Windows 11, version 24H2 “they will share the same KB numbers, but will have different sites and release notes links.”
Following this line, Microsoft has also developed that it is working with third-party providers to “simplify recommended procedures.” Specifically, will allow you to “control the visibility of the upgrade offer banner” –which is used by organizations that want to run an in-place update- establishing the target version on ‘hold’ (retain) within the ‘Select target feature update version’ group policy.
