Tuesday, December 2nd 2025

Microsoft Breaks File Explorer Dark Mode With Latest Non-Security Update

Microsoft has released the KB5070311 non-security preview update for Windows 11, offering enhanced support for dark mode enthusiasts. However, this update introduces an issue with File Explorer's dark mode, causing parts of the app to occasionally flash. The problem results in the application window briefly displaying a blank white screen before loading files and folders. Actions that can trigger this include launching or switching from the Home and Gallery sections, opening new tabs, toggling the Details pane visibility, and requesting additional information during file copy operations. While this is not a critical security issue, it may produce inconvenience to users accustomed to dark mode.

Although Microsoft hasn't yet resolved this issue and has listed it in the "known issues" section, we've managed to recreate what the bug looks like before it returns to normal. It usually lasts for only a second, but it's enough to be annoying, especially if you're using dark mode. The company is working on a fix, which will be included in a future non-security update package. So, those who prefer dark mode will need to endure the inconvenience of flashing white squares a bit longer. It also raises questions about what causes this behavior within File Explorer. With recent issues that Microsoft is actively addressing, it might be due to conflicts between Win32 UI elements and modern WinUI/XAML overlays.
Just a few days ago, Microsoft acknowledged performance issues with File Explorer on Windows 11, which is concerning for such a crucial application within an operating system. To address this, Microsoft is considering preloading File Explorer in the background to enable quicker access when users open the application. Some visual adjustments, like turning off transparency and animation effects, can make File Explorer appear to launch faster, but the underlying problem persists. The older Windows 10 File Explorer used Win32 UI elements. However, Windows 11 overlays this legacy core with modern WinUI/XAML, and these added UI elements are now making the entire application slower, and prone to bugs like we have with dark mode today.
Sources: Windows Central, Microsoft
Add your own comment

67 Comments on Microsoft Breaks File Explorer Dark Mode With Latest Non-Security Update

#26
remixedcat
every time there is something new to add to the pile


can't go a week without ms breaking something!
Posted on Reply
#27
FoulOnWhite
Their feet must look like Swiss cheese the amount of times they’ve shot themselves in them

Mines fine, enterprise ftw :) Edit just spotted it in updates. NOT installing that
Posted on Reply
#28
lemonadesoda
I think more and more people are noticing how poorly managed W11 development is. Previously it was a bit of "not sure I like it, and I guess I'm just used to the old way, but if W11 is a much newer and more secure code base, then ok, I'll go with it". But you can't say that anymore. Now everyone can see W11 is full stack of mismanaged stick-on code amendments and there is nothing solid about it at all anymore.

W11 has jumped the shark: W11 needs to be sun-setted and W12 needs a complete overhaul, start the code base fresh, from scratch.

But I don't think MS has the competence to do it. Despite it being bigger than it ever was, and despite it having more resources than it ever had, at any point in the past, it needs new leadership.
Posted on Reply
#29
Raiden85
Microsoft needs another XP SP2 moment. Everyone needs to stop everything they are doing, stop adding worthless features, and make the entire software team concentrate for at least the next few months on just fixing bugs, fixing security issues, and improving performance.

I don't care how much this sets them back elsewhere or how much this would cost them, it has to be done at this point.
Posted on Reply
#30
r00tcz
In every update, Microsoft keeps "upgrading" old win32 components with something that's far worse.
Old controls were all written by people that understood what they were doing, so it was all in C++, code was profiled, optimized and tested. While there were some quirks, it was nothing horrendous and it all mostly worked.
But now, in the name of forced change and redesign pushed for marketing reasons, all these core components are being replaced by bloated managed C# code with million of dependencies and libraries that have to be loaded every time you need to simply select a file or open file explorer. And all this new code is clearly written by new generation of lazy AI coders that don't care about performance or stability. Design and UX is the most important, then comes the basic functionality. Optimizations? Profiling? Bugfixing? Hahahaha... good joke! Our customers can do that for us.
Posted on Reply
#32
notoperable
M$ is too busy adding yet another background service of dubious description not mentioning use, which usually ends up as another autologger, telemetry or data mining service on top of recall copilot slimy used car sellers emulator

Calling M$ weaponized incompetence as amateur hour is a compliment nowdays.

It's not even funny anymore. I hoped since the time when Steve aka monkey boy had one line of coke too much during his famous euphoric dance shouting demo that Windows finally manages to fuck it self into obsolescence, only the arrival of big data and LLMs postponed it, but I got the feeling we are almost there
Posted on Reply
#33
wNotyarD
r00tczDesign and UX is the most important, then comes the basic functionality. Optimizations? Profiling? Bugfixing? Hahahaha... good joke! Our customers can do that for us.
Not UX though, because usability and consistency is part of User eXperience.
Posted on Reply
#34
notoperable
wNotyarDNot UX though, because usability and consistency is part of User eXperience.
In terms of UX, M$ managed to flip the scale of UX, only company that has a negative axis in UX.
The anti-UX or -Ux 😂
DeathtoGnomesBest Comedy Event.
There is a need for a new category of software engineering snafu, because Amateur Hour is a compliment
Posted on Reply
#35
wNotyarD
notoperableIn terms of UX, M$ managed to flip the scale of UX, only company that has a negative axis in UX.
The anti-UX or -Ux 😂


There is a need for a new category of software engineering snafu, because Amateur Hour is a compliment
MS has been operating on amateur hour for so long it's Amateur Year already.
Posted on Reply
#36
r00tcz
wNotyarDNot UX though, because usability and consistency is part of User eXperience.
I think they nailed it, but just changed the meaning: Unusable/Underwhelming/Useless eXperience = U3X :)
If Win11 is U3X, Win12 will be U^3X . I expect only the worst (+ AI slop invading everywhere).
Posted on Reply
#37
tony359
Solution is simple

IF window is white
THEN draw a black window

That’s how they fix things these days no?
Posted on Reply
#38
_roman_
Who said, "Windows 10 is the last windows you need?" Or is this a wrong quote?
Posted on Reply
#39
notoperable
_roman_Who said, "Windows 10 is the last windows you need?" Or is this a wrong quote?
Nobody actually needs Windows for anything aside of making a bad impression

Everything, literally everything is doable on modern unix derivatives, actually much more
Then Windows was or will be capable of since its a for profit and not for user product.
Posted on Reply
#40
Tek-Check
remixedcatevery time there is something new to add to the pile
can't go a week without ms breaking something!
What else could possibly go wrong...
Posted on Reply
#41
notoperable
I'm pleased with their continued commitment to dig their own grave, good riddance
Posted on Reply
#42
trparky
How is this even possible? How is the GUI code that attached to the stuff underneath it?
Posted on Reply
#43
notoperable
trparkyHow is this even possible? How is the GUI code that attached to the stuff underneath it?
Its not, it's just bad everywhere and riddled with event handling bugs
Posted on Reply
#44
GeoffreyA
r00tczIn every update, Microsoft keeps "upgrading" old win32 components with something that's far worse.
Old controls were all written by people that understood what they were doing, so it was all in C++, code was profiled, optimized and tested. While there were some quirks, it was nothing horrendous and it all mostly worked.
But now, in the name of forced change and redesign pushed for marketing reasons, all these core components are being replaced by bloated managed C# code with million of dependencies and libraries that have to be loaded every time you need to simply select a file or open file explorer. And all this new code is clearly written by new generation of lazy AI coders that don't care about performance or stability. Design and UX is the most important, then comes the basic functionality. Optimizations? Profiling? Bugfixing? Hahahaha... good joke! Our customers can do that for us.
You summed it up.
Posted on Reply
#45
tony359
I don’t mean to turn this into a flame - I’m genuinely curious.

What’s Apple approach with macOS?
Posted on Reply
#46
trparky
tony359I don’t mean to turn this into a flame - I’m genuinely curious.

What’s Apple approach with macOS?
Apple tends to use a scorched-earth strategy with its products, often cutting off legacy support rather than maintaining it. Microsoft, on the other hand, is known for preserving legacy compatibility—though that approach can be a double-edged sword, as reflected in how bloated and buggy Windows has become in recent years.
Posted on Reply
#47
tony359
Of course, it must be ‘simple’ to program for Apple machines. It’s your own SW, your own HW (now even the CPU and GPU), no support to anything older than 7 years.

I’d imagine you can have all combinations of SUPPORTED HW in a single room. With windows, it’s an infinite amount, also including an infinite amount of driver and fw versions.

That said, do apple do a better job in terms of writing their own code, besides the simplicity of their own ecosystem?
Posted on Reply
#48
Wirko
r00tczIn every update, Microsoft keeps "upgrading" old win32 components with something that's far worse.
Old controls were all written by people that understood what they were doing, so it was all in C++, code was profiled, optimized and tested. While there were some quirks, it was nothing horrendous and it all mostly worked.
But now, in the name of forced change and redesign pushed for marketing reasons, all these core components are being replaced by bloated managed C# code with million of dependencies and libraries that have to be loaded every time you need to simply select a file or open file explorer. And all this new code is clearly written by new generation of lazy AI coders that don't care about performance or stability. Design and UX is the most important, then comes the basic functionality. Optimizations? Profiling? Bugfixing? Hahahaha... good joke! Our customers can do that for us.
Alright alright alright, but don't blame managed C# code. It's perfectly good and fast enough for building a file manager.

I use a program called REW (Room EQ Wizard) for audio analysis. The program does quite complex real-time 2D graphing with 128k point Fourier analysis on 192 kHz audio in the background. All written and maintained by one guy. It comes bundled with Java 8 runtime because it's written in Java, no less! And I run it on a Core 2 Duo T7500 notebook with Windows 7 32-bit, pinned to one core, no more! Single process, 48 threads. Guess what - all UI actions run as smooth as if they were native Win32/C++.

Another example is Paint.NET, an image editor written primarily in C# (but unspecified parts are in C++, and it's not open source). Some actions take time of course but the UI is really smooth.
Posted on Reply
#49
maxli86
Here we go again, Windows 10 all the way for me.
Posted on Reply
#50
trparky
At some point, if the stupidity continues, I'm jumping ship to the Mac.
Posted on Reply
Add your own comment
Nov 21st, 2026 13:42 PST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts