Microsoft is speeding up and decluttering File Explorer in Windows 11 – The Verge

Lead

Microsoft is testing changes in Windows 11 Dev preview builds that preload File Explorer to improve launch speed and reorganize the context menu to reduce clutter. The changes, reported by Tom Warren at The Verge, move rarely used actions into dedicated flyouts and separate cloud provider options. Preloading is intended to improve performance on constrained devices such as handhelds and tablets while remaining optional for users who prefer not to run background tasks. Microsoft plans a wide rollout of these updates to all Windows 11 users in early 2026.

Key Takeaways

• Feature status: Preloading and context-menu rework are currently available in Windows 11 Dev preview builds being tested with Insiders.
• Performance intent: Preloading is described by Microsoft as intended “to help improve File Explorer launch performance,” especially on lower-powered devices.
• User control: The preload behavior can be disabled so File Explorer does not run continuously in the background.
• Context menu changes: A new “manage file” flyout consolidates actions like compress to ZIP, copy as path, set as desktop background, and rotate left/right.
• Cloud separation: Cloud-related actions (including Send to My Phone) are moved into a separate cloud provider flyout for a cleaner main menu.
• Rollout timeline: Microsoft expects these tested changes to reach general Windows 11 users in early 2026.

Background

File Explorer has been a central part of the Windows desktop experience for decades, and its interface has accumulated features that some users find helpful and others find noisy. Over successive Windows releases, Microsoft has periodically adjusted Explorer’s look and behavior to balance discoverability and simplicity for both consumers and enterprise users. In recent years, complaints from users of low-powered Windows devices — such as handheld PCs and small tablets — have highlighted uneven launch performance compared with modern desktops.

Microsoft has precedent for using lightweight background tasks to speed app startup: earlier in the year the company deployed a scheduled task for Office apps that preloads components so Word and others open more quickly after boot. That work informed the current approach for File Explorer, where preloading is being trialed but offered as an opt-out to respect power and privacy preferences. The change also responds to long-standing feedback about a crowded right-click menu that can bury frequently used commands beneath less common options.

Main Event

The Dev preview builds now include a File Explorer preload component that activates around system startup to warm key processes and libraries. Microsoft’s notes indicate this is intended to make File Explorer appear to launch faster on systems where on-demand startup is slower; on modern high-spec machines the difference may be negligible. Insiders can toggle the preload behavior off if they prefer not to have the background task running continuously, preserving battery or memory for other work.

Concurrently, the context menu has been reorganized: actions that are used less often are grouped into submenus rather than listed inline. The newly introduced “manage file” flyout collects operations such as compressing files into ZIPs, copying file paths, setting images as the desktop background, and rotating images left or right. Separating these reduces immediate visual noise and aims to make commonly used commands easier to reach.

Cloud-related controls have been relocated to a distinct cloud provider flyout, which also contains device-transfer functions such as Send to My Phone. Moving cloud options out of the main menu both declutters the interface and makes it clearer which actions interact with third-party storage providers or cross-device services. Microsoft is validating these changes with Dev channel testers before broader deployment.

Analysis & Implications

From a performance perspective, preloading trades a small amount of background activity for quicker perceived startup time. For many modern desktops that already open Explorer nearly instantly, the user benefit will be minimal; for constrained devices the improvement could be material. Administrators will need to weigh those gains against battery and memory policies when managing fleets of tablets or handheld enterprise devices.

Usability gains come from reducing cognitive load in the context menu. Grouping infrequently used items into flyouts improves scannability and reduces the time to locate common actions like Rename or Open with. However, hiding features in submenus can hinder discoverability for occasional tasks; Microsoft will need to monitor whether users adapt quickly or express confusion in feedback channels.

For third-party file managers and enterprise tools that integrate with Explorer, the new flyouts may require adjustments to how shell extensions present actions. The cloud provider flyout centralizes cloud integrations, which could simplify vendor UX but also requires cloud providers to register in those menus if they want parity with the old layout. The net effect on ecosystem partners will depend on how Microsoft exposes extension points for the new menu model.

Comparison & Data

The table above summarizes where several common actions have moved; this reorganization reduces the number of items shown at first glance and groups related operations. Microsoft has not published numeric benchmarks for launch-time improvement in these builds, so measured gains will vary by device configuration and must be assessed by Insiders and IT departments.

Reactions & Quotes

“to help improve File Explorer launch performance”

Microsoft (release notes)

Tom Warren notes that on modern PCs File Explorer is almost instant, but preloading should help slower devices such as Windows handhelds and tablets.

Tom Warren (The Verge)

Insider testers have generally praised the cleaner right-click layout while flagging discoverability concerns for infrequent tasks.

Windows Insider community (summary)

Unconfirmed

• Exact performance improvement in milliseconds on specific device models has not been published and will vary by hardware and configuration.
• The precise enterprise update path and default enablement for managed corporate devices remains unclear until Microsoft documents deployment controls.
• The long-term placement of third-party shell extensions in the new flyout model is not yet finalized and may change based on developer feedback.

Bottom Line

Microsoft’s Dev preview changes aim to balance speed and simplicity: optional preloading targets a smoother experience on constrained hardware, while context-menu flyouts reduce visual clutter for everyday users. The company is following a cautious rollout approach, testing with Insiders before wide distribution to all Windows 11 users in early 2026.

For most desktop users the effect may be subtle, but organizations managing tablets, handhelds, or older machines should test the preload option and evaluate battery or memory impacts. Keep an eye on Insider feedback and Microsoft’s official documentation for guidance on deployment settings and any adjustments to the menu model.

Sources

• The Verge — News report by Tom Warren (journalism)
• Windows Insider — Official Windows preview program and release notes (official)