On December 1, 2025, Microsoft shipped an optional preview update that was supposed to make dark mode more consistent across Windows 11. Instead, KB5070311 introduced a jarring visual regression: open File Explorer and the window briefly erupts in a blinding white flash before snapping back to its expected dark theme. The company has acknowledged the bug and says a fix is in the works, but for now millions of users who rely on dark mode are left blinking at unpredictable bursts of light.

What actually broke—and where it strikes

The problem sits squarely inside File Explorer and only fires when Windows 11 is running in its dark color scheme. Microsoft’s official support note for KB5070311 lists five specific actions that reliably reproduce the flash:

  • Navigating into or out of Home or Gallery—including the moment Explorer first launches to its default Home view.
  • Opening a new Explorer tab.
  • Toggling the Details pane on or off.
  • Clicking the “More details” link while a file copy is in progress.

When any of those actions happen, File Explorer’s central content area paints itself stark white for a split second. Persistent chrome elements like the navigation pane and ribbon often stay dark, which makes the flash even more startling. The behavior has been confirmed on both Windows 11 24H2 and the newer 25H2 servicing branch, across builds 26200.7309 and 26100.7309 respectively.

Community reports paint a picture of inconsistency. Some users see the flash every time they open a folder; others encounter it sporadically. The variability points to the interplay between Windows’ drawing pipeline and a particular system’s graphics driver or display configuration—though Microsoft hasn’t tied the regression to any single driver or extension.

What it means for you—and why a flash isn’t just annoying

If you’re a home user or power user who lives in dark mode and opens Explorer dozens of times a day, the flash is a constant distraction. On a large, high-brightness monitor—especially OLED or HDR panels—the sudden white rectangle can feel almost physical, like a camera flash in a dark room.

For people with photosensitive conditions, the stakes are higher. Sudden, high-contrast flashes are a known trigger for photosensitive epilepsy and can also provoke migraines, dizziness, or eye strain in a broader population. While this remains a user-experience defect rather than a security vulnerability, its potential to cause discomfort or harm elevates it beyond a mere cosmetic glitch. IT administrators supporting employees who need dark themes for accessibility should treat the regression seriously.

From a business perspective, help desks are already fielding calls from confused users who assume their graphics card is failing or that a virus has taken hold. The intermittent nature of the bug makes troubleshooting especially frustrating: a technician might see a clean Explorer session while the user sees repeated flashes.

How we got here: a dark mode polish that misfired

The KB5070311 package was published as a December preview update—an optional, early glimpse of the fixes and changes that normally land on Patch Tuesday. Its headline goal was visual consistency: bringing File Explorer and several system dialogs more fully into the dark theme that Windows 11 has been refining for years.

But delivering dark mode is a famously tricky business. Operating systems paint windows in layers, and if a background brush is missing, an element is drawn out of order, or a timing gap opens between the application and the compositor, the user sees a raw light surface peeking through. Early testing by community members points toward a flaw in how Explorer initializes or repaints its content area under the new theming code—an unintended side-effect of the very consistency improvements KB5070311 was meant to deliver.

Microsoft released the preview on December 1, 2025, ahead of the regular cumulative update reportedly scheduled for December 9. By distributing the change first through an optional channel, the company creates space to catch regressions before they hit every Windows 11 PC. This time, that safety net worked: the bug was caught in preview. The question now is how quickly it will be fully extinguished.

What to do right now

Until Microsoft releases a patched version, you have four practical options—each with trade-offs.

1. Switch to Light Mode (quick but blunt)
Turning off dark mode side-steps the bug entirely because the flash only appears when Explorer expects a dark background.
- Go to Settings > Personalization > Colors.
- Under “Choose your mode,” select Light.

This eliminates the flash, but you lose the dark interface you likely chose for comfort, battery savings, or low-light environments.

2. Uninstall the KB5070311 preview
Rolling back removes the offending code along with the bug. Be aware you’re also removing any other fixes the package contained.
- Open Settings > Windows Update > Update history > Uninstall updates.
- Locate KB5070311 in the list, select it, and click Uninstall. Restart when prompted.
- If the entry doesn’t appear, you can force removal from an elevated command prompt:
wusa /uninstall /kb:5070311

3. Pause optional updates
If you haven’t installed KB5070311, simply don’t click “Download & install” when optional updates appear. Administrators can hold or decline the preview in WSUS, SCCM, or Intune until Microsoft confirms a fix.

4. Use a third-party file manager (temporary workaround)
Applications like Explorer++, Total Commander, or One Commander don’t follow the same paint path as File Explorer, so they’re unaffected. This is a niche workaround that introduces its own support and security considerations, but for users who cannot tolerate the flash and can’t change system theme, it’s a stopgap.

Bonus: try a graphics driver update
Anecdotal forum posts suggest that updating to the latest GPU driver reduces flash frequency on some machines. This isn’t a guaranteed fix—Microsoft hasn’t linked the bug to any driver—but if you’re already overdue for a driver refresh, it’s a low-risk experiment.

For IT administrators: contain the damage

Treat KB5070311 as what it is: an optional preview that belongs in a test ring, not on production desktops. If your organization already deployed it, prepare your help desk with a short script:

  • Identify the symptom: “Does File Explorer flash white for a moment when you open it or switch folders?”
  • Immediate fix: switch the user to Light mode or walk them through uninstalling KB5070311 via Settings.
  • Prevention: defer future optional updates until they’ve been validated against dark-mode, high-DPI, and multi-monitor configurations.

Document the rollback process and remind support staff that the flash is a known regression, not a hardware failure or malware.

Outlook: watch the December Patch Tuesday—but don’t assume

Microsoft’s support article says the company is working on a resolution and will update the page when more information is available. The next regular cumulative update is widely expected on December 9, 2025, but whether it will include a fix for the Explorer flash is unconfirmed. Given the visibility of the bug and its accessibility implications, it’s reasonable to hope for a fast-tracked repair—but until the support page actually changes, treat any predictions as speculation.

In the meantime, the safest path for stability-focused users and organizations is to leave the preview uninstalled, stick with Light mode if the flash is unbearable, and keep a close eye on Microsoft’s official release notes. Dark mode should be a respite, not a surprise light show.