Windows 11 KB5129195: What the Emergency Update Fixes

Microsoft's September 2026 Patch Tuesday update broke more than it fixed for a lot of Windows 11 users, so the company rushed out KB5129195 as an emergency patch just a week later. Here's what it fixes, what it still leaves broken, and how to get your PC stable again.

Does KB5129195 Fix the Windows 11 September 2026 Update Problems?

KB5129195 fixes most of the major bugs from the September 2026 Patch Tuesday update, including explorer.exe crashes on managed PCs and several stability issues Microsoft confirmed on September 12, 2026. It does not fix the AMD GPU driver timeout and black screen problem. If you have an AMD graphics card, you need a separate workaround.

Microsoft released KB5129195 on September 15, 2026, three days after admitting the original update, KB5124008, had broken multiple features. KB5124008 shipped on September 8 as a large cumulative update for both Windows 11 24H2 (build 26100.9445) and 25H2 (build 26200.9445). Microsoft called it one of the biggest updates of the year. It changed so many files, the company later said it needed more data to root-cause every report coming in from users.

What Broke in the September 2026 Update?

The September update caused explorer.exe crashes on enterprise PCs, AMD GPU driver timeouts leading to black screens, and at least one other confirmed issue Microsoft did not fully detail in its public notes. A fourth report was still under investigation as of this writing.

Here is what got reported, in order of how many people it hit:

• Explorer.exe crashes and black screens. File Explorer failed to start or crashed right after sign-in, leaving the desktop and taskbar blank. This mostly affected PCs using profile management software like Citrix UPM, FSLogix, Horizon, or ProfileUnity ProfileDisks, so it hit businesses and remote-desktop setups harder than home PCs.
• AMD GPU driver timeouts. Systems with AMD Radeon graphics cards saw driver timeouts within seconds of a normal session, sometimes freezing the whole PC or dropping the display signal entirely. Opening AMD's Adrenalin software made it worse for some users.
• General instability reports. Microsoft's Jason Parker confirmed the company was collecting memory dumps from affected users to trace the remaining causes.

If your PC has been randomly losing its taskbar, freezing on an AMD card, or acting unstable since around September 8 or 9, 2026, you are looking at this update.

What Does KB5129195 Fix, Specifically?

KB5129195 targets the explorer.exe crash and the confirmed stability bugs from KB5124008. Microsoft shipped it as an out-of-band emergency update instead of waiting for the next scheduled Patch Tuesday, which tells you how serious the explorer.exe problem was for enterprise customers.

What it does not touch: the AMD GPU driver timeout. Microsoft's own release notes for KB5129195 state the AMD issue stays open. If your black screens are tied to an AMD card, installing KB5129195 alone will not solve your problem.

How Do You Check Which Build You're Running?

Open Settings, go to System, then About, and look at the OS Build number. If you see 26100.9445 or 26200.9445 without a higher number after it, you have the broken September update and have not yet installed the fix.

• Windows key + I to open Settings
• Click System, then About near the bottom of the left sidebar
• Find "OS Build" under Windows specifications
• Compare the number against the builds above

After installing KB5129195, the build number moves higher than 9445. Check Windows Update history to confirm the KB number installed if you want to be certain.

Should You Install KB5129195 Right Away?

Install KB5129195 as soon as it shows up in Windows Update if you are on a managed PC, a remote desktop environment, or you have already seen explorer.exe crash. If you have not had any problems and you are not on an AMD system, there is little reason to rush, but there is also no reason to hold off. This update fixes bugs and does not add new features, so it carries less risk than a normal feature update.

To install it manually:

1. Open Settings > Windows Update
2. Click "Check for updates"
3. If KB5129195 does not appear automatically, go to the Microsoft Update Catalog and search "KB5129195"
4. Download the package matching your Windows 11 version (24H2 or 25H2) and your system architecture (x64 or ARM64)
5. Run the installer and restart when prompted

Home users on standard consumer PCs saw fewer explorer.exe reports than enterprise environments, so if you have never noticed a crash, KB5129195 is still worth installing for the other stability fixes it bundles in. It is not an emergency for you the way it is for IT departments managing FSLogix or Citrix deployments.

What Do You Do If You Have an AMD GPU and Black Screens?

Since KB5129195 does not fix the AMD driver timeout, you need a workaround until Microsoft or AMD ships a real patch. Two things have worked for affected users:

• Turn off Hardware-Accelerated GPU Scheduling. Go to Settings > System > Display > Graphics > Default graphics settings, and switch Hardware-Accelerated GPU Scheduling to Off. Restart your PC.
• Roll back your AMD driver. If you installed the newest Adrenalin driver around the same time as the Windows update, uninstall it through Settings > Apps, then reinstall the previous stable version from AMD's driver archive instead of the latest release.

Also set your GPU's power mode to High Performance instead of Balanced or Energy Saving, under the same Graphics settings page. Some users found the timeout only happened under the power-saving profile.

If neither workaround helps, wait for AMD or Microsoft to confirm a fix. Since KB5129195 explicitly excludes this bug, a second patch addressing it specifically is likely coming, though no date has been announced.

What About the Explorer.exe Crash Before You Install the Fix?

If you are stuck with a black screen and no taskbar before you get KB5129195 installed, restart explorer.exe manually to get your desktop back temporarily.

1. Press Ctrl + Shift + Esc to open Task Manager directly (this works even without a visible desktop)
2. Click "More details" if you see the simplified view
3. Find "Windows Explorer" in the Processes tab
4. Right-click it and select "Restart"

This brings back your desktop and taskbar for the current session, but the crash will likely happen again at your next sign-in until KB5129195 is installed. Treat it as a stopgap, not a fix.

Why Did One Update Cause This Many Problems?

Microsoft packed an unusually large number of changes into the September 8 update, and this scale is exactly what made the fallout wider than normal. The company itself said the update was extensive enough it needed additional data from affected users before it fully understood every failure.

A cumulative update this size touches hundreds or thousands of files across the operating system. Each change interacts with different hardware configurations, driver versions, and enterprise management tools in ways Microsoft's internal testing does not fully replicate before release. The timing made things worse too. Microsoft had recently urged users not to delay installing updates because of security concerns, then had to walk this guidance back within days once reports started coming in.

This is not the first time a large Patch Tuesday release has caused this kind of disruption, and it will not be the last. To reduce your exposure to problems like this going forward, wait a week or two after a major cumulative update before installing it on machines you cannot afford to have break, unless the update addresses an active security threat.