Microsoft confirms Windows 11’s File Explorer is sluggish, and preloading isn’t the only fix coming
May 6, 2026
Microsoft has recently intensified its public relations efforts, shining a spotlight on the quality enhancements of Windows 11. Following an eagerly awaited update from Marcus Ash, the Windows Insider lead, the tech giant announced a series of performance and reliability fixes that have been highly sought after by power users. However, when Tali Roth, Microsoft’s Head of Product for Windows Shell, took to X to celebrate these updates, it reignited a long-standing debate regarding the preloading of File Explorer.
Many users expressed dissatisfaction with the improved startup times of File Explorer, arguing that Microsoft’s approach of preloading the application is an inelegant solution that unnecessarily consumes system resources instead of addressing the underlying code. In response, Roth provided insight into Microsoft’s multi-faceted strategy for tackling the historically sluggish File Explorer.
Why some users hate File Explorer preloading
For those who fondly recall the File Explorer experience in Windows 10 or earlier versions, the transition to Windows 11 has often felt like a step back in terms of speed. This sluggishness can be attributed to Microsoft layering modern UI frameworks, such as XAML and WinUI 3, atop the legacy Win32 foundation. To mitigate the slow launch times, Microsoft introduced background preloading, which pre-caches the application in memory before user interaction, theoretically allowing for instant access.
While this method effectively accelerates the initial launch, critics contend that it is a brute-force solution. Testing has revealed that this preloading feature consumes an additional ~35MB of RAM. Although this may seem negligible for modern systems, the frustration lies in the fact that preloading only addresses the initial launch. Once File Explorer is open, users may still experience delays when navigating folders, rendering thumbnails, or accessing context menus.
This dissatisfaction has prompted many power users to explore third-party alternatives, such as File Pilot, which demonstrates that efficient file management can be achieved without aggressive background caching.
Microsoft says it’s an “AND” approach
In light of the criticism surrounding preloading, Tali Roth clarified that Microsoft’s strategy is not about choosing one method over another. “As with many things, the answer is an AND,” Roth stated on X. She emphasized that Microsoft takes a holistic view of startup performance, employing a variety of techniques to ensure responsiveness in the areas users access most frequently. Preloading key components of File Explorer is just one aspect of a broader strategy.
Roth also confirmed that genuine optimization of File Explorer is concurrently underway. She outlined several foundational engineering initiatives that the Windows Shell team is pursuing, including:
Targeted optimizations to the launch sequence: Enhancements to the load order and critical paths within the File Explorer code.
Removing bloat: Eliminating unnecessary processes and visual animations that contribute to perceived latency.
Deep foundational fixes: Addressing issues beyond launch speed, such as reducing unnecessary disk reads and minimizing application hangs.
These architectural improvements aim to rectify the in-app sluggishness that preloading cannot resolve. For instance, reducing unnecessary disk reads can significantly enhance the speed at which folders populate upon access.
What to expect next?
Microsoft’s transparency in this matter is commendable, indicating that the company is acutely aware of the performance implications of its hybrid framework and is not merely relying on system RAM to mask the problem. As Roth noted, these foundational optimizations will be rolled out incrementally over the coming months.
Recent Insider builds have already showcased some of these enhancements, including the elimination of blinding white flashes in File Explorer’s dark mode and a more efficient navigation experience. Furthermore, the long-standing Windows 95-era Properties dialog is set to receive a modern WinUI 3 upgrade.
If Microsoft can successfully integrate intelligent preloading with streamlined, optimized code, Windows 11 may soon boast a File Explorer that surpasses its predecessor, Windows 10. The ongoing debate remains: is preloading a valid optimization technique, or should Microsoft focus solely on refining the code? Feedback from users is encouraged in the comments section.
Microsoft confirms Windows 11’s File Explorer is sluggish, and preloading isn’t the only fix coming
Microsoft has recently intensified its public relations efforts, shining a spotlight on the quality enhancements of Windows 11. Following an eagerly awaited update from Marcus Ash, the Windows Insider lead, the tech giant announced a series of performance and reliability fixes that have been highly sought after by power users. However, when Tali Roth, Microsoft’s Head of Product for Windows Shell, took to X to celebrate these updates, it reignited a long-standing debate regarding the preloading of File Explorer.
Many users expressed dissatisfaction with the improved startup times of File Explorer, arguing that Microsoft’s approach of preloading the application is an inelegant solution that unnecessarily consumes system resources instead of addressing the underlying code. In response, Roth provided insight into Microsoft’s multi-faceted strategy for tackling the historically sluggish File Explorer.
Why some users hate File Explorer preloading
For those who fondly recall the File Explorer experience in Windows 10 or earlier versions, the transition to Windows 11 has often felt like a step back in terms of speed. This sluggishness can be attributed to Microsoft layering modern UI frameworks, such as XAML and WinUI 3, atop the legacy Win32 foundation. To mitigate the slow launch times, Microsoft introduced background preloading, which pre-caches the application in memory before user interaction, theoretically allowing for instant access.
While this method effectively accelerates the initial launch, critics contend that it is a brute-force solution. Testing has revealed that this preloading feature consumes an additional ~35MB of RAM. Although this may seem negligible for modern systems, the frustration lies in the fact that preloading only addresses the initial launch. Once File Explorer is open, users may still experience delays when navigating folders, rendering thumbnails, or accessing context menus.
This dissatisfaction has prompted many power users to explore third-party alternatives, such as File Pilot, which demonstrates that efficient file management can be achieved without aggressive background caching.
Microsoft says it’s an “AND” approach
In light of the criticism surrounding preloading, Tali Roth clarified that Microsoft’s strategy is not about choosing one method over another. “As with many things, the answer is an AND,” Roth stated on X. She emphasized that Microsoft takes a holistic view of startup performance, employing a variety of techniques to ensure responsiveness in the areas users access most frequently. Preloading key components of File Explorer is just one aspect of a broader strategy.
Roth also confirmed that genuine optimization of File Explorer is concurrently underway. She outlined several foundational engineering initiatives that the Windows Shell team is pursuing, including:
These architectural improvements aim to rectify the in-app sluggishness that preloading cannot resolve. For instance, reducing unnecessary disk reads can significantly enhance the speed at which folders populate upon access.
What to expect next?
Microsoft’s transparency in this matter is commendable, indicating that the company is acutely aware of the performance implications of its hybrid framework and is not merely relying on system RAM to mask the problem. As Roth noted, these foundational optimizations will be rolled out incrementally over the coming months.
Recent Insider builds have already showcased some of these enhancements, including the elimination of blinding white flashes in File Explorer’s dark mode and a more efficient navigation experience. Furthermore, the long-standing Windows 95-era Properties dialog is set to receive a modern WinUI 3 upgrade.
If Microsoft can successfully integrate intelligent preloading with streamlined, optimized code, Windows 11 may soon boast a File Explorer that surpasses its predecessor, Windows 10. The ongoing debate remains: is preloading a valid optimization technique, or should Microsoft focus solely on refining the code? Feedback from users is encouraged in the comments section.