Microsoft is addressing the issue of sluggish launch times for File Explorer, opting for a strategy that involves preloading the application in the background rather than streamlining its code or removing unnecessary features. This update has been introduced in a Windows Insider build for both the Dev and Beta Channels, coinciding with enhancements to the Xbox full-screen experience for PC and the introduction of a point-in-time restore feature aimed at recovering from failed updates.
Evolution of File Explorer
Over the years, File Explorer has evolved significantly. Originally, in 2018, Microsoft open-sourced the classic Windows File Manager, a compact tool that weighed in at just over 700 kB. This lightweight application was capable of handling file system activities both locally and over networks, and it first appeared with Windows 3.0, eventually being phased out with Windows NT 4.0. Although Windows Explorer had taken the lead since Windows 95, the transition to File Explorer saw an increase in utility, albeit accompanied by a notable increase in size and complexity.
As the application grew, so did its performance challenges. Instead of reversing this trend, Microsoft’s latest approach aims to preload File Explorer in the background. “This shouldn’t be visible to you, outside of File Explorer hopefully launching faster when you need to use it,” a Microsoft representative explained.
However, this solution raises questions about resource allocation. With the push for AI features on user devices, one must wonder if there are sufficient CPU cycles and memory available for this preloading process.
Experimental Changes and User Control
The preloading feature is currently in an experimental phase and is being rolled out gradually. Users have the option to disable this feature by navigating to “Enable window preloading for faster launch times” in the Folder Options under the View tab in File Explorer.
As Windows continues to expand, the tendency for applications to grow heavier is becoming increasingly evident. While preloading may provide a temporary fix, it seems to address the symptoms rather than the underlying issues affecting performance. Nevertheless, Microsoft’s acknowledgment of the problem is a step in the right direction, signaling a willingness to engage with user concerns.
