automatic upgrades

Winsage
April 16, 2025
Microsoft is addressing an issue where some Windows devices are prompted to upgrade to Windows 11 despite Intune policies preventing such upgrades, a problem attributed to a "latent code issue" since April 12. A targeted code fix is being deployed, and users are advised to pause Windows feature updates via Intune until the resolution is fully rolled out. Users who upgraded to Windows 11 inadvertently will need to manually revert to their previous version. Additionally, in November 2024, certain Windows Server 2019 and 2022 devices were upgraded to Windows Server 2025 without user consent, and Microsoft acknowledged the problem but did not provide guidance on reverting these upgrades. Microsoft has also resolved an issue with prompts for upgrading to Windows Server 2025, clarifying that notifications were intended only for those seeking in-place upgrades.
Winsage
April 15, 2025
On October 14, 2025, Microsoft will stop providing security updates for Windows 10 PCs unless users enroll in the Extended Security Updates program. Upgrading to Windows 11 on machines older than five years may result in an error message about CPU compatibility, as Microsoft will not change the requirement for a Trusted Platform Module (TPM) version 2.0. While automatic upgrades may be hindered, there are workarounds for most PCs designed for Windows 10. To upgrade, the computer must boot using UEFI, support Secure Boot, and have an enabled TPM (version 1.2 is acceptable). Users can check their system's BIOS mode and TPM status using the System Information utility and the Trusted Platform Module Management tool, respectively. If UEFI is not an option or if the PC lacks a TPM, an undocumented hack can be used to bypass compatibility checks. A new restriction with the Windows 11 version 24H2 update requires CPUs to support SSE4.2 and PopCnt instructions, making upgrades impossible for PCs built in 2008 or earlier. Most Intel CPUs from 2009 and AMD CPUs from 2013 should meet this requirement. Users can bypass CPU checks and accept any TPM version through a registry edit, which requires running the Setup program from the current Windows installation. The process involves creating a registry key and modifying its value. Alternatively, the Rufus utility can be used to create a bootable USB drive that circumvents compatibility checks, but it cannot bypass the restrictions for very old CPUs lacking support for SSE4.2 and PopCnt instructions.
Winsage
November 27, 2024
Windows 11 version 24H2 has faced significant criticism due to security and reliability issues, with users reporting numerous critical bugs. Compatibility problems have been noted with cache-less WD SSDs, Ubisoft games, Asus devices, fingerprint sensors, USB scanners, and devices using the eSCL scan protocol. Microsoft has confirmed that after upgrading to 24H2, USB devices supporting eSCL may become undetectable, disrupting communication with networked scanners, printers, fax machines, modems, and other devices reliant on this protocol. Since the rollout on October 1, 2024, users have reported that their eSCL-compatible devices are inoperative in various environments. Businesses are urging Microsoft for a fix, and the company is working on a solution but has not provided a timeline. To address these issues, Microsoft has placed a "compatibility hold" on PCs connected to eSCL devices, preventing automatic upgrades to 24H2, and has advised users to avoid manual installation of the update until resolved.
Winsage
November 13, 2024
Numerous businesses experienced an unexpected upgrade to Windows Server 2025 from Windows Server 2019 and 2022, which occurred automatically overnight. Microsoft attributed the issue to third-party patch management tools that may not have been properly configured, urging users to verify their settings. However, some industry insiders, including Heimdal Security, claimed the problem originated from a bug on Microsoft's side, affecting about 7% of their clients due to a procedural error. The upgrade was linked to cumulative update KB5044284, which was meant to be optional. Windows Server 2025 introduces advanced features for security, performance, and hybrid cloud capabilities. The situation is complicated by the absence of clear rollback procedures for affected organizations.
Winsage
November 11, 2024
Microsoft confirmed that several Windows Server 2019 and 2022 systems were unexpectedly upgraded to Windows Server 2025 due to third-party patch management tools managing updates. This was acknowledged in an update on the Windows release health dashboard on November 6, which indicated that Windows Server 2025 is now available as an optional update. Microsoft stated that some devices upgraded automatically to Windows Server 2025 (KB5044284) in environments using third-party products for update management. They advised users to check their update software configurations to prevent unauthorized feature updates. Reports from Windows administrators indicated that servers were upgraded without proper licensing. Microsoft attributed the issue to a procedural error regarding the update's classification. Approximately 7% of Heimdal's customers were upgraded before the company could block the update. Microsoft has not provided guidance for reverting the automatic upgrades beyond restoring from backups. KB5044284 is a cumulative update for Windows 11 24H2 and an optional update for Windows Server 2025. Microsoft also resolved an issue where administrators were prompted to upgrade to Windows Server 2025 via a banner, which led to confusion about licensing requirements.
Winsage
November 5, 2024
Microsoft is automatically upgrading Windows Server 2022 systems to Windows Server 2025 without prior notification, causing concerns among IT administrators. Users have reported that their managed server environments received the upgrade via WSUS, leading to operational challenges, especially in clustered environments. Some users prefer clean installations over in-place upgrades due to past difficulties. A specific update, KB5044284, may have triggered these unexpected upgrades by being misidentified as an operating system update. Discussions on Reddit indicate that the upgrade process appears inconsistent across different Windows versions, with some systems labeling it as a "feature" update.
Search