Help Desk Blogger

Your USB headset or DAC went silent after an update, and Device Manager says “This device cannot start (Code 10)”. That is USB audio Code 10, and October's patch did not remove it. Start with what costs nothing: unplug the device and use a different USB port. Then, in Device Manager, right-click it, choose Disable device, and enable it again. If sound returns, you are done. If not, the order below stops you wasting an evening on the wrong fix.

Does KB5127648 fix USB audio Code 10?

No, KB5127648 does not fix it: Microsoft still lists the USB Audio Class 1.0 fault as mitigated, not fixed, and the October notes repair other things, such as Dolby Digital crashes in older games.

Microsoft's support page says KB5127648 arrived on 13 October 2026 for 24H2, 25H2 and 26H2, with builds ending in 9711. Press Windows+R, type winver and read your build: if it ends in 9711 or later, you already have the patch, so “install the latest update” is not step one.

On 24H2 Home or Pro, October was the version's last update, so nothing later is coming. Our guide to the 24H2 end of support and the one-restart move covers the way out.

According to Techdows, reading Microsoft's known-issues list on 14 October, some USB Audio Class 1.0 devices fail to start or play no sound, and Device Manager reports Code 10. It began with the 8 September update (KB5124008), per GridinSoft's 15 September report. Our rundown of the four faults in that September update covers the others.

The September emergency patch does not help either. KB5129195 (14 September, builds 26100.9457 and 26200.9457) repairs only eight-channel and 3D audio failures on class 1.0 devices that still work in stereo, Redmond Magazine reported on 16 September. So two faults share one complaint, and the cures differ: surround dead but stereo fine, or the device will not start at all.

October's notes do mention audio, which is where people get misled. KB5127648 fixes AC-3 (Dolby Digital) decode crashes in older apps and games, game mouse stutter, Hello fingerprint sign-in after a cold boot and Always On VPN, per Techdows and Windows Report on 14 October. None of that is Code 10. Four numbers decide whether waiting is worth it: how long the fault has been open, what the first fix costs, how many October repairs touch it, and how many patches have cured it.

The cost cell is the one to act on: free checks should always run before the ones that remove security patches. Here is where I part company with the usual advice: “just install the latest update” is outdated for this fault, because the latest update is the one that skips it. And Microsoft's “mitigated” is, I think, a fix of sorts, or rather a workaround with a kinder label, when your DAC is silent.

How do I fix “This device cannot start (Code 10)”?

Work through the checks in order: swap the port and toggle the device, confirm your build, switch to stereo if only surround is dead, and uninstall only after those fail.

A hwbusters headline reports that Microsoft's only advice for the surround variant is to drop to stereo.

Stop at the first row that brings sound back. If the toggle fails, the generic next step is Roll Back Driver on the Driver tab in the device's Properties. That is standard troubleshooting, not a Microsoft-confirmed cure, so treat it as a free experiment.

Should I uninstall the update to get sound back?

Only as a last resort: October's update is cumulative, so removing it may not undo a fault that began in September, and it takes the latest security fixes off your PC with it.

The route, if you must: Settings, Windows Update, Update history, Uninstall updates (Techdows, 14 October). Pausing updates is milder, and Windows allows up to 35 days. Do the sum, though: the fault began on 8 September, so a pause started today ends on 20 November, 73 days in, with no fix date from Microsoft. That is my arithmetic, not a Microsoft figure, and it says waiting out the fault is not a plan.

Whether removing October's update would bring your device back is unknowable from the public notes, and my view is not to trade security patches for a coin toss before the free checks fail.

• Do not apply a Remote Desktop mitigation to an audio fault: the 0xC000000D sign-in error after KB5124010 is a separate issue, and its mitigation switches Administrator protection off.
• Do not read an expiry notice as the cause. Office 2021 support also ended on 13 October, which has nothing to do with sound.
• Do not stack fixes: change one thing, test the sound, then the next.

The decision: keep the update and work around the fault, or remove it. Keep it. This week, replug the device in another port, toggle it in Device Manager, set a stereo format if only surround is dead, and run winver so you know your build when a real fix lands.

"Word opened fine this morning, so is Office 2021 really dead, and do I have to pay for a new one?" Start with the one check that tells you whether this affects you at all. Open Word, click File, then Account, and read the product name under Product Information. If it ends in 2021, the Office 2021 end of support date of 13 October 2026 is yours, and it has now passed. If it says Microsoft 365, you are on a subscription and nothing has changed for you.

Still here? Then check what has actually stopped. Nothing on your screen changes. Everything underneath it does.

What Office 2021 end of support changes on your PC

The change is invisible: Office 2021 apps still open and save your files, but Microsoft stopped every security fix and every form of technical help for them on 13 October 2026, and it is not selling an extension.

Microsoft's own End of support for Office 2021 notice, updated in June 2026, is blunt: there is "no extension and no extended security updates." That is the sharp difference from Windows 10, where Microsoft does sell extra patches, as our guide to checking your Windows 10 ESU enrolment through October 2027 explains. Here there is no lifeline to buy. Staying means staying unpatched.

In practice the danger arrives by email. A booby-trapped Word attachment built around a flaw found next spring will work against your copy for good, because no patch is coming.

But the notice also says your apps "may continue to function," so panic-buying makes no sense. I'd push back on the usual advice to upgrade immediately: work out which exit fits, then take it within weeks.

It is the second Microsoft deadline in a fortnight, after the Windows 11 24H2 cutoff and its one-restart fix, and the pattern repeats: the software runs while the risk grows.

Four numbers from Office Watch's June 2026 rundown decide which exit is cheapest. They are US list prices; no verified UK price was available at writing, so check Microsoft's UK store before paying.

The support date on the replacement matters more than its price. Buying Office 2024 does not end this question, it postpones it to the end of the decade, when the same choice returns.

Should I buy Office 2024 or Microsoft 365?

For a single PC, a one-time Office 2024 licence costs less than Microsoft 365 over its support life, even in the Outlook tier, and the subscription earns its price mainly in households sharing three or more PCs.

The table lines up the two paid routes, cost first. Staying put with the free browser apps is the third route, and it sits in the final row.

The right-hand column says it plainly: the subscription pays only when shared. My view, against Microsoft's own pitch, is that a one-PC home renting Microsoft 365 just to keep Word patched is overpaying.

Can I still use Office 2021 after end of support?

Yes, you can keep using Office 2021 for as long as it runs, but it is only a sensible choice on a home PC where you rarely open attachments from strangers and already have a plan to move.

The quiet winner for many readers is the free browser versions of Word, Excel and PowerPoint, patched by Microsoft on its own servers. They lack some desktop features, which rarely matters for letters and a household budget.

Waiting sounds clever and mostly isn't. Office Watch calls a new one-time Office "likely but not confirmed," so you would be betting on an unannounced product while unpatched. Patches misfire too, as the Windows 11 September update faults showed, but a buggy fix beats no fix, or at least it does once the follow-up lands.

• On a shared family PC, anyone's careless click hits your unpatched copy.
• On a work or school laptop, Microsoft says follow your IT department.
• If a reinstall fails to activate, no Microsoft support line will help.
• Holding out for the next one-time Office means waiting unpatched.

Pay or stay? For most single-PC homes the answer is pay once or go free, not subscribe. Tonight, open File, then Account in Word, and if the name ends in 2021, pick your exit before the weekend: browser apps for light use, Office 2024 for one PC, Microsoft 365 only for a shared household.

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.

Related: Office 2021 end of support landed the same day, so check whether your copy is still patched