Microsoft is pushing Windows 11 24H2 users to 25H2 while April update is breaking machines

Microsoft's October 13, 2026, end-of-support deadline for Windows 11 24H2 Home and Pro editions is driving an automatic upgrade push to 25H2 that has now expanded to all unmanaged consumer devices. The company confirmed the wider rollout via its Windows release health dashboard, with the notice reading that devices not managed by IT departments will receive 25H2 automatically, with only limited control over when it installs.

The technical case for the move is sound. Windows 11 25H2 is an enablement package under 200KB, built on the same core codebase as 24H2. Most of its features were already pre-staged on 24H2 systems through monthly cumulative updates, so the actual upgrade is closer to a feature unlock than a full OS install. Microsoft's machine learning-based rollout system assesses hardware readiness before pushing the update, and for most clean, well-maintained systems the transition should be quiet.

The problem with the timing

The rollout is landing at the worst possible moment. KB5083769, Microsoft's April 14 Patch Tuesday update for Windows 11 24H2 and 25H2, is still causing critical boot failures on a subset of HP and Dell machines. Affected users describe a consistent pattern: the update installs, the machine restarts, the screen fills with pixelated graphics, and the system drops into a BSOD it cannot recover from without manual intervention. As of writing, Microsoft has not released an out-of-band fix for the death loop issue.

That means some users are being nudged toward a version upgrade on machines that are already struggling with April's update. Microsoft's safeguard hold system is designed to block the 25H2 rollout on devices flagged for compatibility issues, but the KB5083769 boot loop affects a specific hardware configuration rather than a broadly catalogued driver or software conflict, which makes automatic detection less reliable.

What users can do

Unmanaged Home and Pro users cannot permanently refuse the 25H2 upgrade. The Pause Updates option in Windows Settings will delay the installation, but once the pause window expires, the system will proceed on its own schedule. For users already experiencing issues with KB5083769, the priority should be resolving the April update problem before the 25H2 transition arrives.

Microsoft's recommended recovery path for affected machines starts with the Windows Recovery Environment. If System Restore fails, Startup Repair is the next option.

A full reset through Reset this PC is the nuclear option — data loss is likely, and it should only be attempted once everything else has failed. If the machine still boots, pause updates and sit tight while Microsoft works on a fix.

Enterprise and education devices are exempt for now. IT departments get more runway to test compatibility before the upgrade is pushed their way.

What changes with 25H2

For users not caught in the KB5083769 issue, 25H2 is a low-risk move. The upgrade activates features already present in 24H2, resets the support clock to October 2027 for Home and Pro editions, and keeps devices in line for ongoing security patches. Windows 11 24H2 loses all security updates, bug fixes, and time zone updates on October 13, 2026, leaving machines on that version exposed to unpatched vulnerabilities going forward.

Microsoft has not announced a fixed timeline for resolving the KB5083769 boot loop issue. Users affected by the April update can follow our earlier coverage linked below for recovery steps.