Microsoft's latest optional preview update for Windows 11 aimed to bring a more consistent dark mode to File Explorer. Instead, it left users with an intermittently blinding white flash — a bug Microsoft has already acknowledged.

The Update That Promised to Smooth Dark Edges

On December 1, Microsoft rolled out KB5070311, an optional non-security preview for Windows 11 versions 24H2 and 25H2. The update (builds 26100.7309 and 26200.7309) finally extended the dark theme to many legacy File Explorer surfaces: copy/move dialogs, progress bars, confirmation prompts, and the “More details” expansion during file transfers. For anyone who works in dim lighting or simply prefers dark interfaces, this was a welcome upgrade.

The official release notes even called out “a more consistent dark mode experience” as a headline feature. But the execution fell short. Within hours, users reported a distracting flash — a split-second burst of bright white — when launching File Explorer or navigating between folders in dark mode.

A Bright White Intruder in Dark Mode

Microsoft’s support article for KB5070311 now lists the problem as a known issue. The behavior is specific: the white flash appears when opening File Explorer (including views like Home or Gallery), creating a new tab, toggling the Details pane, or clicking “More details” during copy operations. The flash is brief but noticeable, and on OLED or HDR displays it can be startlingly bright.

“It’s like a tiny lightning bolt inside my screen,” one user wrote on a community forum. Independent testing by technology publications confirmed the repro steps: the main content area flashes white while the navigation pane and ribbon remain dark, pointing to a painting glitch rather than a wholesale theme failure.

Why Does It Flash? A Timing Glitch in the Paint Pipeline

File Explorer isn’t a modern app from the ground up. It mixes sleek WinUI/XAML surfaces with decades-old Win32 code. When Microsoft extended dark resources into these legacy paths, the initialization order changed. During the first few milliseconds of window creation, the system sometimes draws a default background — historically white — before the dark theme and file list are fully painted.

On most monitors, you might not notice a single misplaced frame. But on fast refresh panels, OLEDs with near-instant response times, or HDR displays that amplify luminance spikes, that default frame becomes a visible flash. The effect is highly environment dependent: driver versions, GPU load, and display type all play a role. That’s why some machines never see it, while others reproduce it every time.

Who Gets Hurt Most

For home users, the flash is an annoyance at best and a pain point at worst. If you use your PC in a dark room, sudden luminance spikes can be genuinely uncomfortable. For photosensitive individuals, it’s an accessibility issue that shouldn’t exist in an update meant to improve visual comfort.

Power users and enthusiasts who tinker with themes may find the regression frustrating but manageable — they often run test machines first. But for IT administrators, the problem is larger. KB5070311 is an optional preview, so many organizations wouldn’t deploy it broadly anyway. But those that did as a pilot now face helpdesk tickets describing “my computer flashes white” and must guide users through rollbacks or theme switches.

How to Dodge the Flash (Until Microsoft Ships a Fix)

There’s no official workaround that lets you keep the dark mode improvements without the flash. You have three practical options:

1. Switch to Light Theme (temporary)

Go to Settings > Personalization > Colors and select Light. The flash disappears because the legacy paint path never tries to apply a dark theme in the first place. This is immediately effective but defeats the purpose of the update.

2. Uninstall the Update

If you installed KB5070311 manually, you can remove it:
- Open Settings > Windows Update > Update history > Uninstall updates.
- Locate KB5070311 (the cumulative update, not the servicing stack update) and uninstall.
- Restart your PC.

For advanced users or IT pros, you can use DISM in an elevated command prompt:

DISM /online /get-packages | findstr KB5070311
DISM /online /Remove-Package /PackageName:Package_for_KB5070311~...

Replace the package name with the exact string from the first command. Note: the accompanying Servicing Stack Update (KB5071142) may not be removable and is generally harmless on its own.

3. Avoid the Update Entirely

If you haven’t installed it yet, simply skip this optional preview. In managed environments, IT admins should decline KB5070311 in WSUS or SCCM for production rings and only allow it in a tightly controlled pilot group with representative hardware.

A few community-developed utilities claim to suppress the flash by hooking into Explorer’s paint process, but injecting code into explorer.exe carries security risks and is not recommended for work devices.

When Will Microsoft Fix It?

Microsoft says engineers are working on a resolution, but no specific timeline has been given. Given that this is a preview update, the fix could arrive in several forms: an out-of-band patch before the next Patch Tuesday, inclusion in the next mandatory cumulative update, or even a server-side enablement tweak if the painting behavior can be adjusted remotely. Past cosmetic regressions have sometimes been resolved within weeks, but there’s no guarantee.

Until the support page for KB5070311 is updated to say the issue is resolved, assume the white flash is still present. You can monitor that page (or check Windows Update history) for confirmation.

The Bigger Picture

KB5070311 was a step in the right direction. A unified dark mode across Windows has been a community wish for years, and this update finally shaded many of the jarring bright dialogs that broke the immersion. But the white flash highlights how fragile the intersection of legacy code and modern theming can be. It also underscores the need for more thorough testing across diverse hardware — especially OLED and HDR displays — before pushing visual changes broadly.

In the long run, a dark File Explorer that doesn’t blind you is a valuable improvement. For now, the safest path is to wait for the fix or to roll back if you’re affected.