Wednesday, July 1st 2026
Microsoft Improves File Explorer Launch Speed in Windows 11
Microsoft released its optional Windows 11 June update a few days ago, featuring package KB5095093. In this release, Microsoft has finally delivered significant performance improvements to its File Explorer application. One of the biggest complaints from Windows enthusiasts was the slow launch speed and poor performance of File Explorer, which is a core Windows application that reflects the state of operating system development and advancement. The performance had degraded over time to the point where Microsoft even started preloading File Explorer to improve launch speeds. However, the KB5095093 update goes a step further by actually addressing the core issues without relying on background preloading tricks to seemingly boost performance.
For example, the Home tab area has received a structural makeover that changes how files are indexed in the Home tab, resulting in a much faster initial launch. Since the Home tab can display connected cloud storage drives, information from pinned folders, and constantly pulls data from the file system, it was the biggest obstacle in delivering a performant File Explorer application. What is currently an optional update for June 2026 will become part of the mandatory update for July 2026, bringing this performance improvement to every Windows 11 PC.Other changes include new quick actions such as "Open file location" and "Ask Copilot" when hovering over a file, improved responsiveness when mounting disk images, and support for backslashes and quotation marks in the address bar. The overall reliability of the address bar has been significantly improved, enhancing the overall user experience.
Source:
Microsoft
For example, the Home tab area has received a structural makeover that changes how files are indexed in the Home tab, resulting in a much faster initial launch. Since the Home tab can display connected cloud storage drives, information from pinned folders, and constantly pulls data from the file system, it was the biggest obstacle in delivering a performant File Explorer application. What is currently an optional update for June 2026 will become part of the mandatory update for July 2026, bringing this performance improvement to every Windows 11 PC.Other changes include new quick actions such as "Open file location" and "Ask Copilot" when hovering over a file, improved responsiveness when mounting disk images, and support for backslashes and quotation marks in the address bar. The overall reliability of the address bar has been significantly improved, enhancing the overall user experience.

76 Comments on Microsoft Improves File Explorer Launch Speed in Windows 11
As for NanaZip, I don't use it. But, being a WinUI 3 application, it demonstrates the performance issues with the framework. In contrast, 7-Zip, which I do use, runs as fast as any '90s-era Win32 program: instant, no delays.
Regarding the GPU, my Arc B580 hasn't got any power setting in Intel's software, and the one in Windows doesn't do anything. PCIe power savings, on the other hand, is key to enable low idle power for Arc, along with ASPM L1. I'll check if changing that makes a difference performance-wise but it has never been the case—in games, at any rate.
I think my system isn't much different really. Probably recording at 30FPS caused it skip those frames. I can't easily compare the compression window tho because I'm using 7Up. There's an app interface window for it somewhere but I've not seen it in years. 7Up embeds in the context menu. Selecting any of the 1st three options creates the compressed file immediately from whatever is selected - done. The 4th option lets me select a destination or control the compression. And there's also the "New..." option - it, as well as any compressed file allows drag & drop, file deletion, etc. So in that way it's: create new, open it like a folder, and put or remove whatever.
Most (NOT all!) linux distrors are faster at generating thumbnail previews for massive folders. Two seconds flat for 200, ten to twenty MB JPegs in Bazzite - 3.15 seconds in Win11 for the same folder. Nautilus ("Files") in Fedora Workstation took 4.2 seconds. Generic symbol icons were practically instant in all three though. My thumb's stopwatch action isn't that fast anyway... :p
___Same here - which is why I turned it off. Seems to increase the 0.1% lows in FPS tests too. ;)
BTW, anyone seeing a delay on launching Win10's Calc (which uses UWP)?
It's maybe 1 second or so here, but that's quite noticeable compared to classic calc.exe.
You can also switch to Performance Power plan.
The new one is 18.4MB on disk:
[INDENT=2]19280319[/INDENT]
[INDENT=2]19,280,319 bytes ÷ 1,048,576 = 18.4 MB[/INDENT]
Loads instantly, uses only about 35MB in memory (and yes, 25MB in Win10):
We need to go all the back to Win7 if we want it lower than that.
I can run 1,780 instances of the current version (on a wimpy 32gig system) before I even need to worry about it. What?!?
And functionally, kicks Classic's butt all down the street - and back!
Unless you're running a Pentium 1.0 system with 16MB RAM or something... What are we even doing here???
- It has way more features (programmer mode, graphing, currency converter, unit converter, date calculation, etc. etc.)
- Much nicer and cleaner interface (according to most users)
- It can handle much larger numbers and higher decimal precision, and
- It gets regular updates from the Microsoft Store - if you use that.
So the extra memory isn't all wasted, it actually delivers more functionality. The trade-off is that it costs more RAM to get all those features and it's pretty much like that with all the little goodies people are calling "bloat". If people don't need or want the extra feature sets there's always the open source stuff - customization isn't a problem - usually. :pAgain tho, certainly... If MS can optimize for a better experience (faster, smaller, whatever) they'll get no flack from me. 🐸
We can make an argument for anything. However, practical wisdom must prevail.Do you mean making Windows open source? Or do you mean a literal Linux distro? The first option, I agree. That would all sorts of good for the world. The second option, they've already done that. It's an abomination I will not link too, but do trust that it's out there, as shown in comment earlier in this thread.
(At most, you will only get a dead OneDrive icon if you use a local account. That's one thing where MacOS is better: you can easily choose to remove the iCloud icon from the Finder, when MS makes it harder.)
I knew that the data security angle was going to appear :D. Billions of people are using cloud storage. Even if it's not 100% perfect, it won't change the fact that a lot of people value convenience over absolute security. Some just settle with not putting anything really sensitive there. The mere fact of being on social media is potentially a risk; using a service that requires a phone number is also a risk (turns out SMS based 2FA can easily be hacked, yet banks across the world still use sms 2FA). Once you get into that kind of talk, the rabbit hole is deep; hackers are trying very hard to make anything secure not so secure. IMHO It's a bit like asking for a phone without the ability to receive SMS, because SMS are being exploited for malicious intent.
If even Linux contributors choose to enable that convenience, then we can be sure that microsoft isn't going to block that functionality.
No doubt, the new Calculator is more functional. But here's the catch: all that can be done in classic Win32, which the higher frameworks are calling in any case.
Regarding the improved precision, if we look at the Calculator project on Github, what has happened is that the GUI was rewritten in C# and UWP. The actual calculation classes—the CalculatorManager, CalcEngine, and RatPack—a lot of the code descends from the old Calculator. RatPack in particular, carrying dates from the '90s. With allowance, we have the old calculation code wrapped in a modern GUI. So, if they haven't changed the interfaces, it should be copy and paste into the old one and recompile.
From RatPack (9x era):
From CalcEngine (Vista/7 era):
Microslop, MS bad, etc , etc
Except the GUI, everything would be perfectly doable quickly on a 4.77MHz 8088 with 512KB of RAM.
(Just to be clear: the fact that the backend that enables said functionality is still present even if you don't use cloud storage doesn't look like an issue to me.)
From what I know about Explorer, the program itself is designed to access the internet if it needs to (even if it doesn't need to, according to some post that I've read elsewhere). I have a memory of me typing a URL in Explorer in the XP era, and I saw the page loading. (But that's been deactivated a long time ago)
Where are your examples of them talking nonsense?
Some of us know how to find workarounds, but that’s not the point, because a huge percentage of users don’t know how, and M$ uses that against them. And if you think that’s right, we just don’t.