If your computer updated to Windows 11 recently and something suddenly stopped working, you're not alone — and it's not your fault. Microsoft's latest update cycle has introduced several known issues affecting everyday users and businesses alike. We're writing this as a public service, because we've already been fielding calls about it and we want you to have the straight story.
Here's what's broken, what's fixed, and what you can do. No jargon.
What Happened?
Every second Tuesday of the month, Microsoft releases a batch of updates called Patch Tuesday. October 2026's release — which includes Windows 11 version 26H2 — is a record-breaker. It patches over 1,400 security vulnerabilities. But like many large updates, it also broke some things that were working fine before. Microsoft has officially acknowledged five separate issues. Two of them still don't have a permanent fix.
Issue 1: Remote Desktop Stopped Working
Who's affected: Anyone who connects to a work computer remotely — employees working from home, IT teams managing devices remotely, staff accessing office machines on the road.
What happens: Non-administrator users try to connect via Remote Desktop and get a cryptic error — 0xC000000D — and the connection fails. The screen says "The token that was passed to the function is invalid."
Why it happened: The October update quietly enabled a new Microsoft security feature called "Administrator Protection" by default in Windows security baselines. It's a legitimate security improvement — but it has a bug that breaks Remote Desktop connections for non-admin users, and Microsoft hasn't fixed it yet.
What you can do: This requires a Group Policy or Intune policy change to temporarily disable Administrator Protection. It's not a setting most users can change on their own — you'll need someone with IT admin access. If your IT is managed externally, flag this to them specifically and point them to Microsoft's release health page.
Issue 2: USB Headsets and Audio Devices Stopped Working
Who's affected: Anyone using a USB headset, USB audio adapter, or USB speakers — especially older or business-grade audio equipment.
What happens: The device shows up as an error in Device Manager (Code 10), produces no sound, or behaves erratically. The device itself is fine — the update broke driver compatibility.
Why it happened: A September update changed how Windows handles USB Audio Class 1.0 devices — the standard used by many business headsets and audio equipment.
What you can do: Try a different USB port. If your device has a 3.5mm option, use that temporarily. In some cases, uninstalling and reinstalling the audio driver in Device Manager helps. Don't buy a new headset until you've tried this — there's a good chance yours is completely fine. Microsoft has acknowledged the issue but hasn't shipped a permanent fix yet.
Issue 3: Some Business Computers Couldn't Log In At All
Who was affected: Businesses running Windows 11 26H2 on computers joined to a company domain — particularly those running older Windows Server infrastructure (Server 2019 or 2022).
What happened: Windows 11 26H2 silently activated a feature called "Machine Identity Isolation" — which only works correctly if your domain controllers are running Windows Server 2025. If your servers are running an older version (which most organizations are), computers couldn't authenticate to the domain. Users were completely locked out of their machines.
This is the kind of issue that looks catastrophic — half the office can't log in, nobody knows why. It was caused entirely by a Windows update silently enabling a feature that the underlying server infrastructure couldn't support.
Good news: Microsoft fixed this in the September 22 update (KB5124010). If you've applied updates since then, you're covered. If you've been avoiding updates and are experiencing this, that update is the cure.
Issue 4: Certain Apps Crashed Without Warning
Who was affected: Users of legacy or specialized applications that use AC-3 (Dolby Digital) audio decoding — found in some video editing, media playback, and conferencing tools.
What happened: Affected apps would close without warning after the September update. Microsoft resolved this with the October 13 Patch Tuesday update.
What you can do: Make sure your system has the October 13 or later update installed. Go to Settings → Windows Update → Check for updates.
Issue 5: Black Screens and Explorer Crashes on Startup
Who was affected: Organizations using Azure Virtual Desktop with FSLogix profile management — a common enterprise remote desktop configuration.
What happened: After updating, users would sign in and see a black screen. The desktop wouldn't load. Windows Explorer would crash in the background repeatedly. Users had to manually launch Explorer from Task Manager just to get a usable desktop.
What you can do: Install the October 13 update (KB5127648). This resolves the issue completely.
The Bottom Line
Two of these five issues are still active with no permanent fix — Remote Desktop failures and USB audio problems. If either is affecting you, workarounds exist, but they require IT knowledge to apply correctly.
This update cycle is also a good reminder: while keeping Windows updated is important for security, major version upgrades like 26H2 sometimes need a few weeks to stabilize. For businesses running critical systems, having IT evaluate major updates before they roll out company-wide can save a lot of disruption.
If any of these issues are affecting you — now you know what you're dealing with.