Help Desk Blogger

Your PC says 24H2. Windows Update says you're up to date. And somewhere you read that something ends on 13 October, which is next Tuesday. That date is the 24H2 end of support deadline for Home and Pro editions, and for most machines the fix is one restart, not a reinstall. Here is the check order, fastest first.

How do I check if my PC is on 24H2?

Press the Windows key and R, type winver, press Enter, and read the build number: if it starts 26100 you are on 24H2, and the security clock on your PC runs out next Tuesday.

Only the first five digits matter. Microsoft's release health page lists the newest 24H2 build as 26100.9550, from 22 September, so anything beginning 26100 is 24H2 however recently it was patched. That's the trap: a fully patched 24H2 machine looks healthy right up to the day the updates stop.

Next, the edition, named in the same box. On Home or Pro, 13 October 2026 is the last Patch Tuesday that reaches you. Enterprise and Education editions of 24H2 get fixes until 12 October 2027, per the same Microsoft page, so a work laptop has another year while the personal Pro machine beside it does not. Edition decides urgency, not age.

Then Windows Update. In Settings, check that updates aren't paused and that the toggle for getting the latest updates early is on. Nothing breaks on the day. Well, nothing you'd notice: the PC boots, apps open, and every flaw found after that Tuesday stays open on your machine.

If last month's patch made you pause, see our guide to Windows 11 September update problems and what KB5129195 fixes: none is a reason to stay on 24H2. An older Windows 10 machine has more room, because Windows 10 extended security updates now run to October 2027, if enrolment went through.

Four numbers decide whether this is a five-minute job or a weekend one. The date comes from Microsoft's Windows 11 release information page and the single restart from TechRepublic's 2 October report; feature updates are free, and the last figure is our own arithmetic on Microsoft's end dates.

The restart figure is the one people doubt. Newer versions reach a 24H2 PC as an enablement package, a small update that switches on features already on your drive. Files, apps and settings stay put.

Should I skip 25H2 and go straight to 26H2?

Yes for almost every home PC on 24H2: 26H2 installs the same way as 25H2, with one restart, but its Home and Pro support runs a full year longer.

The usual advice is to take whatever Windows Update offers. This month that advice is out of date: TechRepublic's August and October reports say Microsoft's automatic route for home PCs leads to 25H2, while 26H2 arrives gradually. Accept the default and you get the shorter of the two.

Read down the right-hand column and the choice makes itself. Only timing and 23H2 push back, and timing has a manual fix: if Windows Update hasn't offered 26H2, Microsoft's Installation Assistant installs it now.

What can block the 24H2 end of support fix?

Three known compatibility problems can hold a PC back from 26H2, and an older 23H2 install cannot take the quick route at all, so check both before you assume Windows Update is broken.

Microsoft blocks the upgrade where it knows something will break, a safeguard hold. As of 3 October, TechRepublic counted three, covering USB audio devices, Credential Guard and virtual desktop setups. If you record through a USB audio interface, that first one is about you.

Here's where I part company with the forums, which treat forcing past a hold as the obvious move. My view: if your income runs through that interface, take 25H2 now and let 26H2 follow once the hold lifts. A dead recording setup costs more than a second restart next year. That's opinion, and Microsoft hasn't said when the holds clear.

The other dead end is 23H2. Its Home and Pro editions are already out of support, and its latest build is 22631.7584, so a reading starting 22631 means the enablement package won't apply. You need the full feature update, and free space on an ageing drive starts to matter. If it's tight, our look at whether to buy RAM and SSD upgrades now or wait in 2026 covers what a replacement costs.

• A pause that runs past 13 October holds you on an unsupported build until it expires.
• A held PC looks like one not yet offered; Microsoft's release health page tells them apart.
• Work PCs follow your IT team's schedule; ask first.
• Back up anyway: one restart is normal, not promised.

So here's the job: open winver tonight, and if the build starts 26100, install 26H2 from Windows Update before next Tuesday's final 24H2 patch.

"The home phone has had no dial tone since the broadband engineer came, and Mum's alarm box keeps blinking." That is the landline switch off arriving early. Providers are moving every UK line from copper to Digital Voice, and kit built for copper can fail quietly. Check in this order: the plug, the power, then the provider.

Start at the wall. A BT-style plug or small RJ11 jack means the device leans on copper and is at risk. A wider RJ45 plug means it already uses broadband. A power lead alone usually means a built-in SIM, which the change leaves alone. HomeCareGuardian's August 2026 telecare guide uses the same test.

Why does the landline switch off break working kit?

Digital Voice carries your calls as internet data through the router, so anything that expects the old copper line's signal or its power, such as older burglar alarms and telecare units, can lose its connection without any warning light.

Copper carried a small current of its own, which is why a corded phone worked through a storm. Digital Voice sends the call as data through the router, and the router needs mains power. Uswitch's explainer, updated August 2026, lists burglar alarms, CCTV, card terminals and telecare among affected kit, and confirms full fibre is not needed: ordinary broadband, SOGEA included, carries the calls. So the router is now your phone socket, and its power matters more than its speed (our comparison of Wi-Fi 7 and Wi-Fi 6E home routers covers speed).

The weak link is paperwork, not technology. Providers are meant to find vulnerable customers before moving them, and they miss some, as Ofcom's December 2025 penalty on Virgin Media and an August 2025 Which? survey of telecare firms show. The time figure below is our own count of days to the cutoff.

If you are shopping for a parent, act on the Which? finding: get the seller to confirm in writing that the alarm works on Digital Voice or has its own SIM. The same habit applies to any connected gadget, as our look at what works and what still breaks in Matter smart homes found.

Copper line vs Digital Voice: what changes at home

Digital Voice keeps your number and your handset but moves the dependency from the copper line to your router, so plug type, power and the telecare rules decide whether each device keeps working after the cutoff.

Left column: the question. Middle: how each network handles it. Right: what to do. Rows run from cost to risk.

All ticks and you are done. One cross, usually the power-cut row, means a router battery pack or a mobile kept charged, both far cheaper than a panic engineer visit in the final week.

What happens to my phone in a power cut on Digital Voice?

Your home phone stops working once the router loses power, unless the router has battery backup, and Ofcom only requires providers to offer enough backup for a short spell of emergency calls, not a night without electricity.

The GOV.UK Telecare National Action Plan, published February 2025, says analogue telecare units typically run 12 to 24 hours on their own battery, and alarms without one fail in a power cut outright. But on Digital Voice that battery only counts while the router is alive, so a unit good for a day goes deaf when the hub does. That is our reading of the two rules together, and it puts the backup question on the router.

The plan's Charter says providers will not migrate a telecare user until "a compatible and functioning telecare solution" is confirmed. My view: sound on paper, but only if the provider knows the alarm exists. Tell them yourself (or, more accurately, get whoever pays the bill to), and if brushed off, call Ofcom on 0300 123 3333. Then check any reassuring letter, as you would when verifying Windows 10 ESU enrolment.

• A burglar alarm that dials out over the phone line: ask the installer for an IP or SIM communicator.
• A router on a timer plug or an extension lead that gets switched off at night.
• Sheltered or social housing: the landlord usually owns the alarm, so ask them for the upgrade date.

This weekend, do the plug test on every device, then phone your provider with two questions: your migration date, and whether a telecare alarm is flagged on your account. If the second answer is no, the job is yours.

Remote Desktop will not connect. Silence from the USB audio interface. A black screen for two seconds, then back, while you read email rather than game. If any of that started after your machine updated this month, you are looking at the Windows 11 September update problems, and the check order matters more than the cause: work out which of the four faults you have, then apply the fix that matches.

Which Windows 11 September Update Problems Are Actually Fixed?

Microsoft's Windows release health dashboard lists the September faults separately, and the 14 September out-of-band update, an emergency fix shipped outside Patch Tuesday, closes the Remote Desktop and Hyper-V folder share failures while leaving the USB audio one only mitigated.

The damage came from KB5124008 on 24H2 and 25H2, and KB5124012 on 26H1, both pushed on 8 September 2026. Before you touch anything, press Windows and R, type winver, and read the build number. That alone tells you which side of the fix you are on. It reached Windows 10 22H2 on extended security too, so confirm your Windows 10 ESU coverage is live: an unenrolled PC gets none of this.

And this is where the usual advice falls over. "Just install the update" is right for two of these faults and pure noise for the fourth, because the graphics fault sits outside the update's scope. Microsoft's KB5129194 notes, published 14 September 2026, date the break and list two elevation-of-privilege fixes the package carries: CVE-2026-62721 in the User-Mode Power Service and CVE-2026-85921 in Secure Kernel Mode. Four numbers decide what you do next.

The exposure window is the part of that grid people misread. A PC that has taken no update since August was never touched, so the question to ask a relative on the phone is not what broke but when Windows last restarted. And if Remote Desktop connects but crawls after the fix, that is a network question, which our Wi-Fi 7 versus Wi-Fi 6E comparison covers.

Patch Forward Or Roll Back And Pause?

Patch forward if your symptoms are remote logins or missing Linux guest folders, and roll back only if your screen is freezing, because those two routes repair different faults and one of them costs you September's security fixes.

Packaging matters, because KB5129195 is not one update for everybody. Pureinfotech's roundup of the out-of-band wave lists one package per version: KB5129195 covers 24H2 and 25H2, 26H1 takes KB5129194, 23H2 takes KB5129242, and Windows 10 22H2 under ESU takes KB5129236. Find your version, then read the build row below.

The deadline row is the one people skip. Microsoft's support page on pausing updates puts the ceiling at 35 days from the day you set it, and when it expires Windows resumes on its own. The arithmetic in that row is ours, not Microsoft's: a pause set on 19 September 2026 dies on 24 October 2026. Write it down, or the update you removed returns overnight.

Does KB5129195 Fix The AMD GPU Black Screen?

No: Windows Latest reported on 15 September 2026 that KB5129195 does not fix the AMD Radeon black screens and freezes, and that neither Microsoft nor AMD has formally acknowledged them yet.

The reports cluster on a specific set of cards: RX 6600, RX 7700 XT, RX 7800 XT, RX 7900 GRE, RX 7900 XTX and RX 9070 XT, with driver timeouts away from any game. If your card is not on that list, your freeze is probably something else. Check where RAM and SSD prices sit in 2026 before you call it a hardware fault.

My view, and it is only that: an unacknowledged bug has no timetable, so waiting is not a plan. No dashboard row to refresh, no date for your manager. Uninstall, pause, and let the bug's owners catch up.

• A rollback removes September's security fixes too, so treat it as a bridge.
• Pausing hides the problem, and it expires on a date you will forget.
• Silence from a USB interface after patching is the mitigation's known limit, so use onboard audio for now.

So the decision is binary, and you can make it tonight: patch forward, or uninstall and pause with the resume date written down. Open winver, match your symptom to the grid, and do that one thing. If the worst of it is a Remote Desktop login, you are one reboot from done.

Related: Windows 11 24H2 end of support and the one-restart move to 26H2