"We've continued refining File Explorer based on that feedback, removing friction and improving the details that help make everyday tasks feel more natural and predictable," the File Explorer team said.
Microsoft's File Explorer redesign targets speed, reliability, and specific annoyances
Microsoft has begun testing a refreshed File Explorer in Windows 11 preview builds rolling out to Insiders this week. According to the company, the effort focuses on improving File Explorer's speed, performance, and reliability while addressing customer-reported issues. The blog post highlighted two concrete user-facing fixes: file renames are no longer interrupted by background file synchronization, and case-only filename changes now appear immediately.
Context menu: less clutter, faster access, and explicit customization
Alongside performance work, Microsoft is testing a redesigned right‑click context menu intended to reduce top-level clutter and keep commonly used actions easy to access. The new design also introduces a Settings experience for the context menu; at the bottom of the right‑click menu Microsoft added a "Customize menu" shortcut that opens a Settings page where users can tweak what appears in the menu. Microsoft described the updated menu as "faster, simpler, and more customizable."

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleWhere this sits in Microsoft's broader Explorer performance work
The current changes are part of a longer-running push to make Windows Explorer faster. Microsoft previously rolled out another set of File Explorer improvements in April and began testing a preloading feature in November meant to preload File Explorer in the background to improve launch times and performance. That preloading feature was optional: users could disable it by unchecking "Enable window preloading for faster launch times" in File Explorer's Folder Options under the View tab.
Microsoft has also experimented with similar optional performance aids elsewhere. In May 2025 the company rolled out "Startup Boost" for Microsoft Office apps, an optional feature that launches a Windows scheduled task in the background during system logon to help Office apps start faster.
Removal of WMIC starts with Windows 11 24H2 and 25H2 and current beta builds
On Monday Microsoft announced it is removing the Windows Management Instrumentation Command‑line (WMIC) tool beginning with Windows 11 24H2 and 25H2, and in the Windows 11 beta builds released this week. Microsoft described WMIC as a known LOLBIN — a living‑off‑the‑land binary — that has been abused by cybercriminals. The company’s action removes that tool from those Windows 11 channels.
What this means for technologists, enterprises, and end users
- Technologists and security teams: WMIC's removal alters the set of built‑in tooling available on Windows 11 24H2 and 25H2 and in current beta builds. Security teams will note the announced removal of a known LOLBIN; defenders and operators should inventory any legitimate workflows that use WMIC and plan alternatives where necessary.
- Enterprises and procurement leaders: the Explorer and context menu changes are arriving first in Insider preview builds. Organizations that manage broad rollouts will watch how Microsoft graduates these changes from preview channels into broadly supported releases and will need to decide when to permit optional features such as window preloading or Startup Boost.
- End users: the changes promise quicker, less interruptive everyday file operations and a right‑click menu that can be tailored via a visible "Customize menu" shortcut. Users who prefer not to preload Explorer previously had and continue to have an explicit control — an unchecked option labelled "Enable window preloading for faster launch times" under Folder Options → View.
Microsoft's update path in Windows 11 — incremental interface tweaks, optional background preloads, and removal of legacy binaries — shows a mix of usability and security tradeoffs being pushed through preview channels. The current public record shows which fixes Microsoft is testing and which tools it is removing, but it leaves open when and how broadly these changes will appear in general‑availability Windows builds and how enterprise environments will adapt those choices.




