Microsoft’s File Explorer Performance Challenges
In recent discussions surrounding Microsoft’s ongoing efforts to enhance the performance of File Explorer, the tech giant has taken steps to preload the application at startup. However, recent findings from Windows Latest indicate that this strategy may be yielding diminishing returns. While preloading aims to improve accessibility, it has resulted in increased RAM usage without delivering significant performance gains.
Microsoft has openly recognized the performance challenges associated with File Explorer on Windows 11, a matter of concern given its integral role within the operating system. In an attempt to remedy these issues, the company has initiated background preloading of File Explorer, which is intended to facilitate quicker access for users.
Testing conducted by Windows Latest reveals that while preloading does offer some benefits, the improvements are not as pronounced as one might hope. In a virtual machine running the latest Windows 11 Insider Preview Build 26220.7271 (KB5070307) from the Dev and Beta channels, the standard launch of File Explorer consumes approximately 35 MB of RAM. In contrast, the preloaded version nearly doubles this figure, reaching 67.4 MB due to additional background processes. Unfortunately, for the end-user, this change is hardly perceptible, as File Explorer continues to exhibit sluggishness.
The differences in performance become evident only under specific conditions, such as when the speed of a video comparison is slowed to 0.25x. However, this scenario does not reflect real-world usage, where the impact of preloading remains minimal. Furthermore, no substantial enhancements have been made to the functionality of File Explorer itself. Tasks like loading the context menu continue to lag, offering no tangible improvements in user experience.
While preloading addresses a fraction of the performance concerns, it does not resolve the underlying issues. Some visual tweaks, such as disabling transparency and animation effects, can create the illusion of a faster launch, yet the core problems persist. In contrast, the previous iteration of File Explorer on Windows 10 utilized Win32 UI elements, which did not necessitate a performance boost. The transition to Windows 11, with its modern WinUI/XAML overlay, has introduced additional UI elements that inadvertently slow down the entire application.
