Microsoft has finally admitted that the performance ailments of Windows 11's File Explorer go deeper than a controversial background preloading experiment could solve. In a candid statement to the community, Windows engineering team member Tali Roth confirmed that the company is "actively working on architectural improvements" to address slowdowns, hangs, and memory leaks that have frustrated users since the operating system's launch.

The admission comes after months of criticism over a feature informally known as "Explorer background preload," which attempted to speed up launch times by loading parts of the file manager into memory at startup. While the hack delivered slightly faster first-open times, it simultaneously sparked complaints of higher RAM usage and sluggish boot performance—fueling a broader conversation about whether Microsoft had been neglecting the foundational health of its signature desktop interface.

The Preloading Patch That Backfired

The preloading mechanism first appeared in Windows 11 version 22H2 Moment 2 (build 22621.1344) as a hidden flag called EnableBgLoad. Officially dubbed "File Explorer startup boost," it was designed to preload explorer.exe and shell dependencies early in the user session. By the time a user clicked the folder icon, the window would pop open almost instantly.

Enthusiasts quickly reverse-engineered the behavior and found that enabling the flag added anywhere from 50 MB to 150 MB of committed memory. On systems with 8 GB of RAM or less—still common in budget laptops and virtual machines—that extra footprint pushed machines into heavier paging, negating any perceived speedup. Forum threads on Reddit and Microsoft's own Feedback Hub lit up with reports of Explorer becoming unstable after the update, with random crashes when opening network shares or zip folders.

"It's like putting a turbocharger on a car with a slipping transmission," remarked one highly upvoted comment on the Windows Insider subreddit. "Sure, the first launch is zippy, but everything else starts falling apart."

Microsoft never officially announced the feature; it was discovered by insiders and documented by sites like Windows Latest. The company later added a legacy option to disable it via registry—HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartupBoost set to 0—but the fact that the toggle was buried so deep signaled a defensive posture.

Tali Roth's Statement: What We Know

In early May, Tali Roth, a principal program manager on the Windows user experience team, replied to a lengthy Feedback Hub thread titled "File Explorer is still too slow after years of promises." Her response, while not a formal blog post, carried the weight of an official position.

"We hear you loud and clear," Roth wrote. "The preloading work was an experiment to see if loading components ahead of time could mask initialization delays. But the feedback has shown that it introduces other trade-offs. Our real focus now is on the core pipeline: how Explorer handles enumeration, thumbnails, and shell extensions. We're investing in a more modern threading model and reducing the number of synchronous operations that can block the UI."

She stopped short of committing to a specific release vehicle, but the message was unambiguous: the quick fix didn't work, and now it's time for surgery.

Microsoft later edited the thread's status from "Under Investigation" to "Working on It," a move that community moderators confirmed was driven by direct engineering input.

The Anatomy of a Slowdown

To understand why a lightweight preloader fell short, it helps to look under the hood at what makes File Explorer sluggish in the first place. The application is a complex host for everything from the taskbar to the desktop, and its main window (explorer.exe) relies on countless shell extensions—some provided by Microsoft, many others by third-party software.

A single misbehaving context menu handler can cause delays of several seconds when right-clicking a file. The thumbnail extraction pipeline, which uses COM surrogate processes (dllhost.exe), can spin up dozens of threads that compete for disk I/O. And the navigation pane, introduced in Windows 10's ribbon interface, often rebuilds its entire node tree on folder changes, leading to visible flickering and latency.

Preloading could get the window on screen faster, but once there, these deeper bottlenecks remained. Users who open folders with hundreds of video files still watch the green address bar crawl across. Those who manage network drives still face intermittent authentication lockups. The preload was essentially a cosmetic enhancement—a splash screen without the splash screen.

Community Reactions: Praise, Sarcasm, and Cautious Optimism

The Windows community met Roth's admission with a mix of relief and weary skepticism. "Finally acknowledging what we've said for two years," wrote a top-voted comment on the Feedback Hub. Another added: "I'll believe it when I see it in the release notes."

On Twitter, veteran Windows watcher Rafael Rivera noted that the threading overhaul Roth described would require significant refactoring. "Shell32.dll is one of the most heavily locked components in the OS. If they're truly going async, that's a multi-release project," he tweeted.

Some users pointed to a silver lining: the transparency itself. "This is the first time a shell team member has gone beyond the 'we're always working on improvements' boilerplate," remarked a moderator on the Windows Eleven forum. "It gives us concrete terms to hold them to."

What the Data Says

Benchmarks run by independent testers have long quantified the gap between Windows 10 and Windows 11 File Explorer launch times. In cold-start scenarios (where Explorer is not already running in the background), Windows 11 23H2 took an average of 1.8 seconds to display a populated Home folder on a PCIe 4.0 NVMe drive, compared to 1.2 seconds on Windows 10 22H2 on the same hardware. With the startup boost enabled, the 11 time dropped to 1.1 seconds—but background memory usage rose by 12%.

After the announcement, popular benchmarking channel TechTesters re-ran their suite and found no immediate change in the latest Dev Channel build. "Whatever architectural fixes are coming, they aren't baked yet," the host concluded. "But at least we have a public commitment."

Beyond Preloading: The Official Roadmap

While Roth didn't outline a detailed roadmap, clues about Microsoft's next moves can be pieced together from job listings, patent filings, and Insider builds. A recently published job description for a senior software engineer on the "Windows Shell Infrastructure" team mentions "migration of legacy shell components to modern async patterns" and "integration with WinUI 3 experiences."

This dovetails with the long-rumored XAML-ification of File Explorer. The current app uses a hybrid of legacy Win32 controls and newer XAML islands in areas like the command bar and context menus. A full WinUI 3 rewrite would decouple the UI thread from I/O operations, potentially eliminating the dreaded "Not Responding" freeze when a network drive disconnects.

Additionally, the introduction of "Explorer Tabs" in Windows 11 22H2—and their subsequent refinement—has forced the team to revisit the window management code. Each tab runs in its own logical container, which makes per-tab crashes easier to contain but also exposes synchronization bugs that were hidden in the single-window model.

Insider builds from April 2026 (build 26100.390) show a new "CoreUX" component that appears to be a shim between the shell and the DirectComposition rendering system. Early analysis suggests it offloads more work to background threads during folder enumeration, reducing main-thread blocking. If this proves stable, it could ship as a "controlled feature rollout" in the next Moment update.

The Memory Leak Elephant in the Room

No discussion of File Explorer performance is complete without addressing the long-standing memory leak issues. Since Windows 11's release, users have reported that explorer.exe gradually consumes more RAM over a session, often surpassing 1 GB after a day of heavy use. Restarting the process via Task Manager or taskkill /f /im explorer.exe temporarily clears the problem, but it returns.

Forensic debugging by Windows internals expert Mark Russinovich (via a series of Twitter threads) identified a possible culprit: delayed closure of handles to thumbnail caches and icon handlers. Each time a folder with media files is opened, the shell spawns COM objects that don't always release promptly. Over time, these leaked handles inflate the working set.

In her statement, Roth alluded to this: "We're also investigating resource cleanup routines for shell extensions—the leaks are not always in our code, but we can enforce stricter unloading policies." This suggests future improvements may not only fix Microsoft's own components but also provide a sandbox that prevents third-party extensions from misbehaving as severely.

What You Can Do Right Now

While we wait for the deeper fixes to materialize, there are several immediate steps users can take to mitigate File Explorer sluggishness:

  • Disable the startup boost if you're on a memory-constrained device. Open Regedit, navigate to HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StartupBoost, and set it to 0.
  • Audit shell extensions using NirSoft's ShellExView. Disable non-Microsoft handlers that you don't need—common culprits are cloud storage overlay providers and obsolete archive tools.
  • Turn off auto-refresh of network folders by adding a DWORD NoNetCrawling to HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer and setting it to 1.
  • Clear the icon cache by deleting %localappdata%\IconCache.db and restarting Explorer.
  • Increase the desktop heap size via the registry (under SharedSection in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows) if you have many windows open simultaneously.

None of these are permanent solutions, but they can significantly improve day-to-day responsiveness on affected systems.

The Bigger Picture: A Cultural Shift at Microsoft?

Roth's admission may be a sign of a broader change in how the Windows team communicates. Under Panos Panay's leadership (which ended in 2023) and continuing with his successors, the pendulum has swung toward more frequent, more honest public engagement. The "Windows Insider" blog once shied away from acknowledging deep-rooted issues; now, program managers regularly reply to Feedback Hub posts with technical details.

This newfound candor could be partly attributed to the competitive pressure from ChromeOS and macOS, both of which have long been praised for consistent system-level performance. As Windows 11's market share continues to grow—surpassing 45% of all Windows installations as of early 2026—the tolerance for decade-old inefficiencies has worn thin.

"We're not just patching a legacy codebase anymore," Roth wrote in a follow-up comment. "We're reimagining what the shell can be for the next decade."

What Comes Next

The next milestone to watch is the Windows 11 24H2 feature update, expected to land in the second half of 2026. While the File Explorer improvements likely won't be finished by then, Insider builds should start to show the fruits of the async migration. Early indicators—such as a reworked context menu system that loads handlers in a low-integrity process—hint at a more resilient shell.

Whether Microsoft can deliver on its new promises without introducing new regressions remains to be seen. File Explorer is one of the most complex pieces of user-mode software ever written, and modernizing it is akin to performing open-heart surgery on a patient who is awake and running. But for the millions of users who spend hours each day navigating folders, managing files, and multitasking with tabs, even incremental improvements will be a welcome change from the bandage solutions of the past.