Windows 11 24H2 Stopped Getting Updates on October 13. Here Is Your Move

Microsoft ended support for Windows 11 version 24H2 on October 13, 2026 — for Home and Pro editions. If your PC runs 24H2 Home or Pro and you do nothing, it will no longer receive monthly security updates, bug fixes, or technical support. In plain terms: every new vulnerability discovered from here on stays open on your machine forever.

This is not a scare tactic, it's the servicing calendar working as designed. Windows versions get roughly two years of support for Home and Pro. 24H2's time is up.

Windows 11 24H2 end of support: check whether you're affected

First, find out what you're running. Press Windows key + R, type winver, and press Enter. If the dialog says 24H2, check your edition under Settings → System → About. Home and Pro are the editions affected now. Enterprise and Education editions of 24H2 keep getting updates until October 12, 2027, so managed work PCs are fine for another year.

If you're on 25H2, 26H1, or 26H2, you're on a different servicing clock and this deadline doesn't apply to you. If you're somehow still on Windows 10 without extended security updates, you have bigger problems — that ship sailed much earlier.

Your move: back up, then take the feature update

The fix is straightforward and free. Before anything else, back up your files and make sure you can find your BitLocker recovery key (check your Microsoft account's device page — it's usually saved there). Then open Settings → Windows Update and install whatever feature update is offered. 25H2 is the confirmed path off 24H2.

Don't overthink which version to land on. The right version is any supported one. Staying on an expired build because you heard a rumor about a buggy update is the classic false economy — the known risk of running unpatched (every future exploit works on you permanently) dwarfs the transient risk of a feature update with issues.

What the last 24H2 update actually delivered

October's cumulative update, KB5127648, was the final one for 24H2 Home/Pro — and the first cumulative for the new 26H2 branch. It restored File Explorer's ability to preview files downloaded from the web (reversing an earlier security change that had blocked quick PDF previews), fixed a broad set of Bluetooth reliability problems including LE Audio and microphone handling issues, added Emoji 17.0, and added accessibility options like remapping the Copilot hardware key and an "open apps maximized" setting.

It's a decent final package, and a reminder of what you're giving up by staying put: not just security patches, but the steady drip of usability fixes. The Bluetooth fixes alone are worth the update for anyone who's fought flaky audio.

A note for work PCs and patient updaters

If your PC is managed by an employer, check with IT before forcing anything — Enterprise and Education editions of 24H2 are supported until October 12, 2027, and many organizations deliberately stay one version behind for stability. That's a legitimate strategy when someone is paid to manage the risk. On a personal PC, nobody is managing it but you, which is exactly why the deadline matters more, not less.

One more practical tip: after the feature update completes, give the machine a day before judging it. Post-update indexing and background optimization make everything feel slower for a few hours, and a surprising number of "the update broke my PC" complaints resolve themselves by morning.

Don't sit this one out

End-of-support deadlines are the rare computer maintenance task with a real deadline and a real consequence. An unpatched PC isn't just your problem — it's a foothold for malware that spreads, a botnet node, a credential theft waiting to happen. The update takes under an hour, most of it unattended.

If you've been putting off bigger maintenance, make a day of it: update Windows, then back up your 2FA codes while you're in the backup mindset, and check whether your other software is current too. Future you, dealing with zero ransomware incidents, says thanks.