Microsoft is planning another overhaul of the Windows 11 right-click context menu, according to a recent signal from a senior design lead. Marcus Ash, a principal design manager at Microsoft, recently hinted that the company is working on changes aimed at making the menu simpler, faster, and more customizable. The news, though not yet an official announcement, has reignited conversations among Windows enthusiasts about one of the operating system’s more contentious user interface elements.

The context menu—the list of options that appears when you right-click on the desktop or in File Explorer—has been a flashpoint since Windows 11 launched in 2021. Microsoft radically simplified it, burying many classic options behind a “Show more options” entry. The move aimed to reduce clutter and improve touch-friendly interaction, but it frustrated power users who relied on quick access to traditional commands. Now, nearly four years later, the company appears ready to try again.

A Brief History of Windows 11’s Context Menu

When Windows 11 debuted, the new context menu was one of its most visible changes. Gone were the long, dense lists of applications and shell extensions. Instead, users saw a compact menu with icons for common actions like Cut, Copy, Paste, and Delete. Any third-party extensions or legacy commands were hidden under “Show more options,” which required an extra click—and often loaded noticeably slower than the main menu.

The redesign was part of Microsoft’s broader effort to modernize Windows, prioritizing a cleaner aesthetic and consistency across the OS. The company argued that the old right-click menu had become a dumping ground for software developers, leading to bloated and slow-loading menus. By forcing apps to use a new extensibility model, Microsoft aimed to keep the experience lean. Unfortunately, adoption was slow. Many popular applications continued to rely on the legacy system, meaning users still had to dive into the secondary menu for common tasks.

Criticism was immediate and loud. Power users, IT professionals, and developers decried the extra step. A popular workaround—a registry tweak to restore the classic menu entirely—spread quickly across forums and social media. Microsoft itself acknowledged the friction, and over subsequent updates, it made incremental improvements. Windows 11 22H2 added labels to the top row of icons, and later updates improved performance of the secondary menu. Still, the core grievances remained.

What We Know About the Upcoming Changes

Marcus Ash’s hint came during a conversation on X (formerly Twitter), where he is known for sharing candid insights into Windows design decisions. While the exact wording of his post is not publicly detailed in the excerpt, the message was clear: Microsoft is actively working on making the context menu “simpler, faster, and more custom.” No timeline, specific features, or build numbers were mentioned. This is typical of early-stage design signals—often a way to gauge user reaction before committing resources.

Given Ash’s role as a principal design manager, his words carry weight. He has previously discussed the challenges of balancing legacy support with modern design, and his team oversees many of the shell experiences in Windows. The phrasing “more custom” is particularly intriguing because it suggests users may gain the ability to tailor the menu to their workflows—perhaps by pinning frequently used actions or rearranging items. That would be a significant departure from the current locked-down design.

Community Frustrations with the Current Menu

The Windows enthusiast community has been vocal about the context menu’s shortcomings. On platforms like Reddit, the Microsoft Feedback Hub, and various forums, users consistently list the same pain points:

  • The double menu problem: Accessing rarely used but essential commands (like 7-Zip’s “Extract here” or third-party backup tools) requires two right-clicks or a shift-right-click.
  • Performance: The legacy menu sometimes takes a second or more to appear, jarring on otherwise fast systems.
  • Inconsistent behavior: The menu looks and behaves differently depending on where you click—desktop, File Explorer, taskbar, or applications—leading to confusion.
  • Missing personalization: Unlike the old menu, which could be modified with registry hacks or tools like ShellExView, the modern version offers no officially supported customization for end users.

These issues have pushed some users to adopt tenacious workarounds. Registry edits that completely disable the modern menu remain popular. Third-party tools like Nilesoft Shell and StartAllBack offer alternative menu designs. Even Microsoft’s own PowerToys—a set of utilities for power users—doesn’t directly address the context menu problem, though its “File Locksmith” feature adds a shell extension that must be accessed through the legacy menu.

The feedback isn’t lost on Microsoft. A quick look at the Feedback Hub shows thousands of upvotes for requests like “Bring back the classic right-click context menu” and “Allow customization of the new context menu.” The company’s engagement with the Windows Insider program gives it a direct line to core users, and design leads like Ash routinely interact with the community. It’s plausible that the upcoming redesign is a direct response to this sustained feedback.

What Could a ‘Simpler, Faster, More Custom’ Menu Look Like?

Without official details, we can only speculate based on the three adjectives Ash used. Yet they align closely with what users have been demanding, and they also fit into broader trends in Windows UX development.

Simpler: This could mean reducing the current hybrid approach. One possibility is a unified menu that intelligently surfaces both modern and legacy commands without a separate “Show more options” layer. Microsoft might introduce a grouped layout with collapsible sections, similar to how the new Outlook places less-used features behind a “More commands” button. Another approach is a dynamic menu that adapts to context—showing a compact set of actions for quick tasks but expanding automatically when a user lingers or presses a modifier key.

Faster: Performance has been a sore spot. The legacy menu’s delay often stems from shell extensions loading on demand. Microsoft might pre-load commonly used extensions or cache their metadata. The modern menu already uses a separate process for extensions to prevent crashes, but further optimization could minimize the perceived lag. Ash’s mention of “faster” likely signals an engineering focus on reducing menu display time to near-instantaneous, even on older hardware.

More custom: This is the wildcard. Microsoft has historically been cautious about letting users modify shell components, fearing instability and security risks. But the company has also embraced limited customization in other areas, like the taskbar and Start menu. A customizable context menu could allow dragging commands from an app’s registered actions, pinning scripts, or even creating nested shortcuts. Developers might be given better tools to integrate their actions directly into the modern menu without resorting to hacky workarounds. The power user community would welcome a return to the flexibility of the classic menu, but with the safety and visual polish of the modern UI.

Why Another Redesign?

It’s worth asking why Microsoft would revisit the context menu now. The current design, while imperfect, has been stable for years. One likely driver is the feedback loop from enterprise customers. Organizations often deploy Windows with custom right-click actions for security, data management, or proprietary software. The “Show more options” hurdle can disrupt workflows and increase support tickets. A more efficient menu—especially one that allows IT teams to pre-configure shortcuts—would be a selling point in the corporate world.

Another factor is the growing desktop operating system competition. While Windows remains dominant, ChromeOS and macOS both offer streamlined, responsive right-click menus that are highly praised. Apple’s menu integrates seamlessly with third-party apps via Services and Shortcuts, and ChromeOS’s minimalist approach works well in educational settings. Microsoft may feel pressure to match or exceed these experiences.

Finally, the internal design philosophy at Microsoft has shifted since Windows 11’s launch. The company has increasingly embraced user choice, walking back some of the most restrictive decisions. The taskbar, for instance, regained the ability to ungroup application icons and show labels. The Start menu received folders. These reversals suggest a new openness to power-user cues, making a context menu redesign a logical next step.

When Might We See This?

Marcus Ash did not provide a timeline, and it’s wise to temper expectations. Large UI changes typically go through months of internal prototyping, usability testing, and Insider flights before they reach stable public builds. A major overhaul like this likely wouldn’t appear in the current 24H2 development cycle; instead, it might target Windows 11 25H2 or even a future Windows release.

That said, smaller iterative improvements could arrive sooner. Microsoft might first ship performance optimizations or an API update that allows developers to better integrate their commands. A preview could appear in a Windows Insider Dev Channel build later this year, with the full rollout phased over several months. Given the mixed reception to the original menu, the company will want to get this right the first time.

The Road Ahead for Windows 11 UX

The context menu redesign is emblematic of a larger challenge: balancing simplicity with capability. Windows’ strength has always been its vast ecosystem of software and hardware—and the deep customization that comes with it. But that legacy also brings complexity that can alienate newer users. The original Windows 11 context menu leaned too far toward minimalism, ignoring the habits of its most loyal base. A successful redesign will need to thread the needle, offering a clean default experience while making power features seamlessly accessible.

Community reaction to Ash’s signal has been cautiously optimistic. Many longtime users are weary of past promises, but the specific mention of “custom” has sparked hope. If Microsoft delivers a menu that loads instantly, surfaces both modern and legacy commands intelligently, and allows personalization, it could finally put the right-click wars to rest.

For now, Windows enthusiasts will watch the Insider builds closely. As always, the feedback loop will be crucial. Users who want to influence the direction should join the Insider program and share their ideas via the Feedback Hub. The message from Redmond seems clear: they’re listening, and change is coming—again.