One October Patch, Six Broken Things

On October 13, 2026 — Patch Tuesday — Microsoft rolled out KB5127648 to every supported Windows 11 release: 24H2, 25H2, and 26H2. If you checked your build number after installing, you'd see 26100.9711, 26200.9711, or 26300.9711 depending on your version.

Because it's a cumulative update, Windows didn't ask. It waited for a restart, applied the patch, and moved on. Somewhere between ten days and two weeks later, the complaints tend to sound the same: "my Wi-Fi keeps asking for my password," "my screen goes black after I sign in," "Xbox won't let me log in."

Try Screen Recorder — free, no sign-up, and it runs entirely in your browser.

Here's the frustrating part. Each of those bugs has been reported separately — a Wi-Fi story here, a Smart App Control story there — but nobody has put them on one page. So you're left wondering whether your specific symptom is the update, your hardware, or bad luck.

This is that page. Every confirmed KB5127648 breakage, how to verify the update is your culprit, and the fix for each one.

Is It the Update? How to Check If KB5127648 Broke Your PC

Before you touch a single setting, spend ninety seconds confirming the patch is actually installed. Two ways to check:

Update history: Go to Settings > Windows Update > Update history. Look for "2026-10 Cumulative Update for Windows 11 Version 24H2 (KB5127648)" (or 25H2/26H2, matching your version). If it's listed as installed, you have it.
Build number: Press Win+R, type winver, and hit Enter. After the patch, 24H2 shows build 26100.9711, 25H2 shows 26200.9711, and 26H2 shows 26300.9711.

Then run the timing test, which is almost embarrassingly reliable: if your PC worked fine and then broke within a day of a restart — especially an restart you didn't choose — the odds strongly favor the update over coincidence.

Here's the full symptom list confirmed against KB5127648 so far:

Wi-Fi on secure networks keeps prompting for credentials or refuses to connect (WPA2-Enterprise / 802.1X PEAP networks — campus and office Wi-Fi)
VPN connections still broken, even though this update was supposed to fix them
Smart App Control stuck off or greyed out in Windows Security — Microsoft has confirmed this one
Xbox Live sign-in error 0x87DD0005
Black screen after signing in on Windows 11 26H2 machines
USB audio devices glitching or cutting out
Remote Desktop connection problems
The update itself failing to install with error 0x800f0845

If your problem is on that list and KB5127648 shows in your update history, you've found your culprit. Now fix it.

Fix 1: Wi-Fi Keeps Asking for Credentials or Won't Connect

This is the big one for students and office workers. KB5127648 breaks authentication on WPA2-Enterprise networks — the kind where you sign in with a username and password through 802.1X/PEAP instead of a shared Wi-Fi password.

That's why the campus library Wi-Fi suddenly loops on a credentials prompt while your home network, which uses a plain pre-shared key, keeps working fine. It's not your laptop's radio. It's the authentication handshake the update broke.

Quick attempts first (2 minutes)

Before anything involving the registry, try the simple resets:

Forget and rejoin the network. Settings > Network & internet > Wi-Fi > your network > Forget, then reconnect and re-enter your credentials fresh.
Reboot the Wi-Fi adapter. Settings > Network & internet > Advanced network settings > Network reset, or just toggle Wi-Fi off and on. Faster than it sounds.
Check "Remember credentials." If the sign-in prompt has a remember-me checkbox, make sure it's ticked before submitting.

If the network reconnects, you're done. If Windows rejects correct credentials or keeps prompting anyway, you've hit the confirmed bug — and you need the registry workaround.

The actual fix: Microsoft's registry workaround

Microsoft has documented a manual fix, and it's a targeted registry edit that forces Windows to rebuild the broken authentication entry for the affected network profile. Neowin's write-up walks through it step by step, and the official version lives in the known-issues section of Microsoft's KB5127648 page.

The edit itself takes about five minutes: open Registry Editor as administrator, navigate to the network profile's 802.1X settings, apply the change Microsoft specifies, and restart. Standard registry rules apply — follow the documented steps exactly, and don't improvise edits elsewhere in the registry.

Once you're reconnected, verify the fix actually restored your throughput rather than just the connection — a quick check with a free bandwidth calculator tells you whether you're back to full speed or limping.

The VPN footnote

On October 21, Microsoft admitted KB5127648 also failed to fix a known VPN bug it was supposed to address, and published a workaround. If your VPN died and stayed dead after this patch, that's not your imagination either — check the same known-issues section for the VPN-specific steps.

Fix 2: Smart App Control Greyed Out or Stuck Off

This one is quieter than dead Wi-Fi, and arguably nastier. Bleeping Computer reported that Microsoft confirmed KB5127648 can leave Smart App Control turned off — meaning a security feature you thought was guarding your PC silently switched itself off during a routine update.

Check if you're affected

Open Windows Security > App & browser control > Smart App Control settings. If the toggle shows Off — or the options are greyed out entirely — and you never turned it off yourself, the update likely did it for you.

Why you can't just flip it back on

Here's the design decision that makes this painful: Smart App Control can only be switched on while it's in evaluation mode on a fresh Windows setup. Once it's off, Windows greys out the on-switch permanently — and the only supported way back is resetting or reinstalling Windows 11.

That's why "smart app control evaluation mode greyed out" is suddenly a surging search: people are opening the setting, discovering it's dead, and finding no toggle to revive it.

What to actually do

Don't panic about coverage. Smart App Control off doesn't mean defenseless. Microsoft Defender Antivirus and real-time protection keep running independently — check the Virus & threat protection page to confirm they're on.
Wait for Microsoft's fix before resetting anything. The company has confirmed the behavior, and a forced-off SAC state caused by an update bug is exactly the kind of thing a follow-up cumulative patch addresses. Resetting your PC to restore a single toggle is a disproportionate response while a fix is pending.
If you genuinely need SAC back — some users do, particularly on machines that handle untrusted downloads — Settings > System > Recovery > Reset this PC (keeping your files) is the supported path. Just do it knowing you're reinstalling the OS for one feature.

The remaining confirmed issues cluster around sign-in and hardware. None are as severe as the Wi-Fi break, but each has a fix path.

Reports cite KB5127648 — along with its sibling October patch KB5127694 — triggering Xbox Live sign-in error 0x87DD0005 on Windows 11. The error blocks the Xbox app and Game Bar from authenticating your account.

Work through it in order:

Restart the PC fully. Not sleep, not hibernate — an actual restart, since that completes pending update servicing.
Sign out and back into the Microsoft Store and Xbox app. A stale auth token after patching is a common trigger for this exact error code.
Check Xbox Live service status before assuming it's you. If the sign-in servers are degraded, 0x87DD0005 can appear on unpatched machines too.
Still stuck after both? This is the case where uninstalling the update (next section) is the cleanest move — it removes the trigger entirely.

Windows 11 26H2 machines have hit a black screen immediately after signing in post-update. The desktop never paints; you're staring at a void with a cursor.

Try this sequence:

Ctrl+Alt+Del and choose Task Manager. If it appears, go to File > Run new task, type explorer.exe, and hit Enter. If the desktop materializes, you've confirmed explorer crashed at sign-in — dedicated fix guides for this exact 26H2 bug are already circulating.
Force two full restarts in a row. Black-screen bugs tied to update servicing frequently clear once servicing fully completes on the second boot.
Unplug USB peripherals, especially docks and hubs, then reboot. They interfere with the sign-in chain more often than people expect.

USB audio cutting out and Remote Desktop issues

Microsoft lists both USB audio and Remote Desktop problems among the known issues for this cycle. The USB audio bug shows up as headsets and microphones dropping, crackling, or vanishing from the sound picker.

Conservative fixes that respect the fact this is an update bug: replug the device into a different port, roll back or reinstall the device driver in Device Manager, and test Remote Desktop connections after a full restart. If the glitch appeared the same week as the patch and driver work doesn't clear it, treat it as update-caused and move to the uninstall option.

The update fails to install with 0x800f0845

If KB5127648 repeatedly fails with error 0x800f0845, Windows is telling you the servicing stack itself is unhappy. Run the Windows Update troubleshooter under Settings > System > Troubleshoot > Other troubleshooters, restart, and retry. If it still fails, download the standalone package for KB5127648 from the Microsoft Update Catalog and install it manually — that bypasses the broken automatic delivery path.

Still Broken? Uninstall or Block KB5127648 (Before Microsoft Pushes It Back)

When a specific bug has no workaround yet — or the workaround is more surgery than you'll tolerate — removing the update is the honest fix. Two routes:

The Settings route: Settings > Windows Update > Update history > Uninstall updates, find KB5127648 in the list, click Uninstall, and restart.
The command route: open Command Prompt as administrator and run wusa /uninstall /kb:5127648, then restart. Same result, faster to document.

Be clear-eyed about the tradeoff: this is a security update. Uninstalling it removes October's security fixes, so it's a stopgap, not a permanent home. Treat it as buying time while Microsoft ships a corrected cumulative update.

Stop Windows from reinstalling it immediately

Windows Update will quietly re-offer a removed update on its next scan. Two defenses:

Pause updates under Settings > Windows Update > Pause updates — up to five weeks on Windows 11, which comfortably covers the gap until a fixed build arrives.
Watch the calendar. The next Patch Tuesday lands November 10, 2026, and that cumulative update will supersede October's — carrying both the security fixes and, presumably, the repairs for this mess. A date calculator makes it easy to count exactly how many days of pause protection you have left before that deadline.

The strategy most people land on: uninstall the patch, pause updates for a few weeks, check the KB5127648 known-issues page around November 10, and re-update once Microsoft marks the issues resolved. You keep the stopgap short and the security gap smaller.

FAQ

How do I know if the October 2026 Windows update caused my problem? Check Settings > Windows Update > Update history for KB5127648, or run winver — builds 26100.9711, 26200.9711, and 26300.9711 confirm it's installed. If your symptom started within a day of a restart and matches a known issue, the update is the likely cause.

Can I uninstall KB5127648? Yes. Go to Settings > Windows Update > Update history > Uninstall updates and remove it, or run wusa /uninstall /kb:5127648 from an administrator Command Prompt. It's a security update, so reapply it (or its November replacement) once your issue is fixed.

Why is Smart App Control greyed out after this update? Microsoft confirmed KB5127648 can switch Smart App Control off, and Windows only lets you re-enable it from evaluation mode on a fresh setup — so once it's off, the toggle greys out. A PC reset restores it; otherwise wait for a fix and keep Defender enabled.

Does KB5127648 break home Wi-Fi? The confirmed break affects WPA2-Enterprise networks using 802.1X/PEAP — typical campus and office Wi-Fi that asks for a username and password. Home networks using a shared Wi-Fi password aren't the target of this bug, though the same patch cycle has known VPN and Remote Desktop issues.

What is Xbox sign-in error 0x87DD0005? It's an Xbox Live authentication failure reported after the October 2026 patches, blocking sign-in to the Xbox app and Game Bar. A full restart plus signing out and back into the Microsoft Store clears it in most cases; otherwise uninstall the update.