Microsoft on December 1 shipped an optional Windows 11 preview that stomps out two persistent bugs—a taskbar-crashing notification glitch and a micro-stutter that plagued gamers launching titles on high-end monitors. But installing KB5070311 (builds 26200.7309 and 26100.7309) comes with an abrupt aesthetic trade-off: File Explorer now flashes white in dark mode, and the sign-in screen hides its password icon.
The fixes: what Microsoft actually fixed
The update, documented in Microsoft’s KB5070311 release notes and corroborated by independent testing, addresses a handful of issues that have dogged some Windows 11 users for weeks.
Explorer.exe stops crashing after certain notifications
The most disruptive bug caused explorer.exe—the shell process responsible for the taskbar, Start menu, and system tray—to hang or crash. Microsoft’s notes state the fix targets a condition where “explorer.exe might stop responding (leading to the taskbar becoming unresponsive) after certain notifications.” The company declined to explain the root cause, but community reproductions noted that incoming alerts or even stale notifications sitting in the Action Center could trigger the failure. With Windows Latest reporting personal experience of a disappearing taskbar even without a fresh notification, the pattern suggests a race condition tied to notification processing. With KB5070311 installed, the shell should remain stable.
Launch-time stutter on very high-resolution monitors smoothed
Gamers and professionals using 4K, ultrawide, or high-refresh displays had reported a subtle but annoying hitch whenever an application or game queried the full list of supported display modes. Microsoft describes the improvement: “Performance has been improved when apps query monitors for their full list of supported modes.” The exact change isn’t detailed, but the behavior points to a blocking or inefficient enumeration path that could stall the calling process for a fraction of a second. After the update, mode queries are snappier, eliminating the stutter at app launch or when switching display settings. Importantly, in-game frame rates remain unaffected—the fix purely addresses the initial bump.
More fixes packed into the preview
Beyond the headliners, KB5070311 resolves several other nuisances:
- A brightness slider bug that reset brightness on some all-in-one PCs.
- A false-positive “Unsupported graphics card detected” warning that appeared even when a fully supported GPU was present.
- Search indexer and SMB network search glitches.
These quality-of-life improvements round out a substantial non-security preview, but two newly acknowledged regressions steal some of the spotlight.
The trade-offs: brand-new bugs you’ll notice immediately
Microsoft’s KB page and multiple tech outlets have confirmed that the same update introduces two visible glitches.
File Explorer’s white flash in dark mode
Users who rely on dark mode—a widespread preference—will see File Explorer flicker bright white when opening the app, switching tabs, or navigating between folders. Windows Central, BleepingComputer, and PureInfoTech all reproduced the behavior, and Microsoft lists it as a known issue. For dark-environment workers, the flash is jarring; in extreme cases, it can be disorienting. Microsoft says it’s working on a fix, but no timeline is offered.
The invisible sign-in icon
On the lock or sign-in screen, the icon that lets you toggle between password, PIN, or other credential types may vanish entirely. It still functions—you can hover your mouse over the blank area and click—but the missing visual cue is a regression for accessibility and shared-device usability. The workaround is to hover and click blindly until the control reappears, hardly ideal for a security-sensitive surface.
These fresh issues make KB5070311 a classic mixed bag: you gain core stability at the cost of cosmetic polish.
What it means for you
Who you are dictates whether you jump on this preview or hold steady.
Home users and casual PC owners
If your taskbar has been crashing unexpectedly or you’ve grown annoyed by game-launch stutter on your high-spec monitor, KB5070311 likely solves your problems. The fix for explorer.exe stability is the biggest draw. The dark mode flash and hidden sign-in icon are nuisances but not workflow-killers for most people. As always, back up your data before installing, and be ready to uninstall the update if the glitches bother you more than the original bugs.
Gamers and enthusiasts
The stutter fix is targeted, but gamers should double-check that other recent performance regressions are also addressed. Earlier in the fall, some NVIDIA users saw frame drops after Windows 11 updates; vendor hotfix drivers and this OS patch combine to mitigate those issues. Community reports are mixed, so test your favorite titles after updating. Tools like CapFrameX can help you compare frame time consistency before and after.
IT administrators and enterprise fleets
KB5070311 is a preview, not a Patch Tuesday mandatory update. The File Explorer flash and invisible sign-in icon could trigger help-desk tickets, and the flash may even pose accessibility concerns. Deploy in staging, confirm that your provisioning images don’t clash (especially after the XAML registration race documented in KB5072911), and wait for the December 9 Patch Tuesday rollup unless a specific, high-impact symptom forces your hand. If you must roll back, note that the combined LCU/SSU package cannot be uninstalled with wusa.exe; you’ll need DISM.
How we got here
Windows servicing in 2025 has been unusually eventful. Microsoft’s push to modularize shell components into updatable XAML/AppX packages accelerated feature delivery but also introduced fragile registration steps. The explorer.exe notification crash and the display enumeration stutter are symptoms of that architecture—race conditions between shell processes, notification handling, and display subsystems that varied by hardware and usage patterns.
The earlier provisioning regression (KB5072911) highlighted how a startup race could crash the shell entirely on first logon; KB5070311 chips away at another variant of that fragility. The “unsupported GPU” false positive and brightness slider reset are reminders that even routine quality fixes carry unexpected side effects when servicing touches dozens of subsystems.
Microsoft’s communication around these bugs has been sparse: root causes aren’t published, only symptom descriptions and assurances that the fix is in place. Administrators are left to infer the technical details from behavioral testing and community reports.
What to do now
Your immediate actions depend on your risk tolerance.
Install now if:
- You’re actively hitting the taskbar crash or launch stutter.
- You don’t rely on dark mode in File Explorer (or can tolerate a brief flash).
- You’re willing to roll back if the regressions are too annoying.
Wait for December 9 Patch Tuesday if:
- Your system is stable now and the known issues would disrupt your workflow.
- You manage devices for others and cannot risk introducing visual bugs.
- You prefer the broader validation that Patch Tuesday updates undergo.
How to check your build: Go to Settings → System → About; if you see OS build 26200.7309 or 26100.7309, KB5070311 is present.
How to uninstall the LCU if needed:
1. Open an elevated Command Prompt or PowerShell.
2. Run DISM /online /get-packages | findstr KB5070311 to identify the package name.
3. Execute DISM /online /remove-package /packagename:<PackageName> and reboot.
Do not use wusa.exe—the combined SSU/LCU package prevents standard uninstall.
For gamers testing performance: Use CapFrameX or MSI Afterburner to measure frame times. If you still see stuttering or fps drops, check for a GPU vendor hotfix; NVIDIA’s recent hotfix driver, for instance, specifically addressed Windows 11 performance regressions.
Outlook
The December 9 Patch Tuesday cumulative update will almost certainly include the fixes from KB5070311 alongside a remedy for the dark mode flash and login icon regression. Microsoft has acknowledged both issues, and the next automatic update is the standard channel for mass deployment. Until then, the preview serves as an opt-in patch for the impatient. The broader lesson for Windows users: modular updates deliver fast fixes but occasionally swap one rough edge for another. This cycle, that trade-off is on full display.