Like it or not, Windows 11 25H2 is coming to your PC whether you asked for it or not. Microsoft has expanded its rollout of the Windows 11 2025 Update to cover every unmanaged Home and Pro device still running version 24H2, with no mechanism to permanently refuse the installation. The company confirmed the change via an update to its Windows release health dashboard, stating that “machine learning-based intelligent rollout has expanded to all devices running Home and Pro editions of Windows 11, version 24H2 that are not managed by IT departments.”
The stated reason is straightforward: Windows 11 version 24H2 reaches end of mainstream support on October 13, 2026, after which devices still on that version will stop receiving security patches, bug fixes, and time zone updates. Microsoft’s position is that it needs to move consumers off the platform before that deadline arrives. The technical delivery mechanism is also relatively painless by Windows upgrade standards: 25H2 ships as an enablement package well under 200KB, since the code was already pre-staged on 24H2 systems through monthly cumulative updates. There’s no multi-gigabyte download, and the upgrade activates with a single restart. BleepingComputer has confirmed the rollout is live, as have several users who received the update before Microsoft officially announced the expanded scope.
What users cannot do is refuse permanently. PCWorld notes that the Pause Updates option in Windows Settings will delay the inevitable, but once your pause window expires, the system will install the update on its own schedule. Enterprise and education devices managed by IT administrators are currently exempt, giving organizations more time to validate compatibility and test their environments before committing.
The timing is awkward, as always, for one reason in or another: 24H2 has had a rocky ride. Since March’s Patch Tuesday, Microsoft has issued multiple emergency out-of-band patches for both 24H2 and 25H2, including a fix for sign-in failures affecting Microsoft accounts across Teams and OneDrive, and a separate Bluetooth visibility patch. An earlier cumulative update had its rollout paused entirely after triggering installation errors on some systems. Forcing users onto 25H2 six months before 24H2 even goes out of support — when some of those issues are still fresh — is the kind of decision that tends to generate heat and a few choice words in the enthusiast community.
If you’re running a clean, updated 24H2 system with current drivers, the 25H2 transition should be fine. If you’re running anything unusual — heavily customized installs, niche peripheral drivers, or older hardware on the edge of compatibility — make sure you have a backup before this one lands.