Microsoft is working on a Windows 11 context-menu redesign, confirmed on June 3, 2026, by Windows design executive Marcus Ash, with the goal of making right-click menus faster, simpler by default, and configurable around the commands people use most. That sounds small only if you do not live in File Explorer all day. The right-click menu is one of those humble Windows surfaces where decades of compatibility, developer freedom, and user muscle memory collide. Microsoft’s challenge is not merely to tidy a menu; it is to prove that Windows 11 can modernize without treating power users as legacy baggage.
The context menu has always been one of Windows’ quiet productivity engines. It is not glamorous like the Start menu, not brandable like Copilot, and not easily demoed on a stage. But for anyone who compresses archives, scans files, opens terminals, manages images, syncs cloud folders, or wrangles network shares, right-click is less a convenience than a work rhythm.
That is why Microsoft’s latest signal matters. Ash did not announce a finished Settings page, a specific Insider build, or a release date. He said Microsoft is working on context menus that are faster, simpler by default, and configurable to what users use most. In Windows terms, that last phrase is the rupture.
For years, Microsoft’s answer to context-menu clutter has been curation from above. Windows 11 introduced a cleaner-looking primary menu and pushed older or less-modern integrations behind “Show more options.” The result was visually calmer, but operationally messier: one menu for Microsoft’s design principles, another for the user’s actual workflow.
A configurable context menu would acknowledge what the Windows 11 redesign initially resisted. There is no single “clean” right-click menu that works equally well for a home user, a developer, a photographer, a sysadmin, and a gamer with five shell extensions installed. The operating system can provide defaults, but the person doing the work needs a vote.
That openness was one of Windows’ great strengths. It was also a long-running UX debt machine. Every installer wanted a piece of the right-click menu because the menu was close to the user’s intent: this file, this folder, this image, this executable, this desktop background. If the program could appear at that exact moment, it felt integrated with Windows itself.
The trouble is that the menu had no strong sense of scarcity. Each vendor could argue that its command was useful, and each individual addition seemed harmless. Over time, the accumulated result became the familiar Windows sprawl: duplicate entries, nested submenus, obsolete handlers, vendor-branded commands, icons from three design eras, and delays caused by shell extensions that had to be queried before the menu could settle.
This is the part of the story Microsoft rarely says out loud. Windows’ backward compatibility is not abstract. It has a visible texture. Sometimes that texture is a 25-year-old accounting package still running on a modern PC; sometimes it is a right-click menu that looks as though every app installed since the Clinton administration left a forwarding address.
The design had logic. The old menu had become too long, too inconsistent, and too dependent on third-party extensions that could slow down basic interactions. Microsoft also had to accommodate touch and pen input better than the dense Windows 10 menu did. A modernized primary menu gave Microsoft a place to enforce a cleaner pattern while preserving the old extensibility model through “Show more options.”
But the compromise immediately irritated the people most likely to notice it. The new menu often hid exactly the commands that made right-click valuable. Users who relied on 7-Zip, Git tools, advanced image editors, terminal launchers, or device-vendor utilities found themselves performing an extra click dozens of times a day. In some workflows, Windows 11 had not reduced complexity; it had inserted a toll booth in front of it.
That is the deeper criticism. The Windows 11 menu was not wrong because minimalism is bad. It was wrong because it mistook Microsoft’s preferred command hierarchy for the user’s. Clean design becomes paternalism when it removes agency from the people who understand their own work.
That extra click mattered because context menus are about immediacy. A right-click is not a trip to Settings. It is a fast, local act: I have selected this object, and I want to do something to it now. If the desired command is hidden behind a second menu, the interaction loses the very quality that made it useful.
The keyboard shortcut workaround never fully solved the problem. Shift-right-click and Shift+F10 may satisfy longtime Windows users who are comfortable with hidden affordances, but they do not fix the underlying design tension. A workaround is not the same as a preference, and a shortcut is not the same as a first-class setting.
The reaction also exposed a split in Microsoft’s audience. Casual users may never notice the missing commands because they rarely use shell extensions. Enthusiasts and IT pros notice immediately because their Windows installations are often defined by them. A clean default is good; a locked-down clean default is where the trouble starts.
The best version of this would not simply expose a chaotic checklist of every possible shell verb. That would recreate the old problem in Settings form. Microsoft needs a disciplined customization model: pin, hide, reorder, reset, and perhaps per-file-type control for advanced users. The menu should stay sane by default, but it should stop pretending that every user has the same definition of sane.
There is also a performance angle. Context menus can feel sluggish when Windows has to enumerate handlers, query extensions, or wait on poorly behaved integrations. A configurable model could allow Windows to defer or suppress rarely used handlers without severing compatibility. The user gets speed; legacy apps keep their escape hatch.
The obvious risk is that Microsoft ships a shallow version of customization that disappoints both camps. If users can only toggle a few Microsoft-approved entries, the change will be cosmetic. If third-party entries remain uncontrollable, the menu will still be a landlord problem: Microsoft owns the building, but every app gets to hang a sign in the lobby.
The company has already been moving in that direction through modern app patterns and developer guidance. Windows 11’s primary menu is not meant to be a free-for-all clone of the old menu. Developers are expected to use modern extension mechanisms if they want their commands to appear cleanly in the new surface. That makes sense architecturally, but it also shifts burden onto software vendors that may have little incentive to revisit working code.
This is where Windows differs from more tightly controlled platforms. Microsoft cannot simply decree that old shell extensions vanish. Enterprises depend on them. Utilities depend on them. Niche workflows depend on them. The history of Windows is full of strange but business-critical integrations that look ugly until the day they save someone hours of work.
A better context menu therefore has to be both stricter and more forgiving. It should enforce clearer grouping, reduce duplicate noise, and discourage vendors from spraying commands across the top level. But it also has to preserve a route for older tools, because compatibility is still one of Windows’ strongest selling points.
These are not edge cases. In managed Windows environments, the context menu can become a support problem. Users see commands for apps they do not understand, cloud services they are not supposed to use, or legacy tools that remain installed for one department but confuse another. A right-click menu that is merely customizable per user is useful; one that is manageable at scale is far more consequential.
Performance also matters in enterprise fleets. A sluggish context menu might sound trivial compared with endpoint detection, patch compliance, or identity hardening, but small delays repeated across thousands of users become real friction. Explorer hangs and shell-extension conflicts are the kind of mundane problems that generate tickets precisely because they interrupt basic work.
Microsoft has an opportunity to treat context-menu configuration as part of Windows manageability rather than a personalization toy. If the company exposes sane policy controls, IT departments could standardize cleaner menus, reduce help-desk confusion, and still allow exceptions where specialized tools are needed.
That does not mean Microsoft is abandoning its Windows 11 aesthetic. The company still wants cleaner surfaces, modern controls, and layouts that work across input types. But it seems more willing to admit that a clean interface is not the same as a rigid one. Users can tolerate change when they are given meaningful control over the outcome.
The Start menu and the context menu are linked by a common complaint. In both places, Windows 11 often reorganized familiar workflows around Microsoft’s preferred defaults. Recommended items, pinned layouts, hidden commands, centered taskbar behavior, and simplified menus all communicated a design philosophy: fewer visible choices, more curation, more consistency.
That philosophy was not foolish. Windows had become visually and behaviorally inconsistent. But Windows users are not iPad users, and Windows PCs are not appliances. The platform’s identity is bound up with adaptation: registry tweaks, PowerToys, Group Policy, shell extensions, taskbar habits, scripts, and utilities. When Microsoft forgets that, even elegant design can feel hostile.
Defaults matter because most people never change them. Microsoft should absolutely improve the out-of-box context menu for the majority of users who do not need five compression commands or three cloud-sharing providers at the top level. A shorter menu is easier to scan, less intimidating, and less prone to accidental clicks.
Ownership matters because Windows is used by people whose workflows are deeper than the default. A developer may want “Open in Terminal” and Git commands immediately available. A designer may want image conversion and editing actions. An administrator may want hashing, permissions, and security tools. A writer may want archive, rename, and cloud-share actions but never vendor telemetry shortcuts.
The winning design is not the one that guesses perfectly. It is the one that makes guessing less important. If Windows can learn from usage, expose clear controls, and allow users to promote or demote commands, Microsoft can keep the menu clean without freezing it in someone else’s idea of usefulness.
This layering is understandable. Windows cannot be rewritten like a startup app. Every major interface change has to pass through decades of compatibility, localization, accessibility, automation, enterprise deployment, and third-party integration. The result is evolutionary design, not clean-slate design.
But users experience the seams, not the rationale. They see two menus. They see commands that appear in one place but not another. They see modern icons beside older dialog boxes. They see a system that asks them to trust a redesign while repeatedly sending them back to the legacy interface to finish the job.
A truly revised context menu must reduce that seam. If “Show more options” remains the place where real work happens, the redesign has failed. If the modern menu becomes configurable enough that most users rarely need the legacy menu, Microsoft will have done something more valuable than repainting Explorer.
Still, Windows users have learned to wait for implementation before applauding intent. Microsoft often announces direction before details, and the details matter enormously here. A toggle buried in Settings would not be enough. A limited list of first-party commands would not be enough. A configuration model that cannot manage third-party shell extensions would not be enough.
The company also has to avoid turning customization into yet another Microsoft-account-adjacent cloud preference system. Context-menu settings should be local, transparent, exportable, and manageable. Enthusiasts will want control; enterprises will want policy; developers will want documentation; accessibility users will want predictable behavior. A serious redesign must serve all four.
Most of all, Microsoft has to respect muscle memory. Users can adapt to better interfaces, but they resent churn that slows them down. If commands move, hide, or reappear unpredictably, the menu will feel less like a tool and more like a negotiation.
A mature Windows 11 does not need to abandon modern design. It needs to stop confusing modern design with enforced minimalism. The best desktop interfaces are not the ones with the fewest options; they are the ones that reveal the right options at the right time and let experienced users shape the environment around real work.
That is especially important as Microsoft pushes AI features, cloud services, and cross-device experiences deeper into Windows. The more the company asks users to accept new layers, the more it must preserve trust in the old ones. Right-click is one of those old layers. If Microsoft can make it faster and cleaner without making it less useful, it earns credibility for bigger changes.
The reverse is also true. If the redesign becomes another constrained surface where Microsoft decides what matters, users will keep restoring the classic menu, installing shell replacements, and treating Windows 11 as something to be corrected after installation. That is not the relationship Microsoft should want with its most invested customers.
Here is what will matter when the overhaul reaches real Windows PCs:
Microsoft Finally Admits the Right-Click Menu Is Not a Detail
The context menu has always been one of Windows’ quiet productivity engines. It is not glamorous like the Start menu, not brandable like Copilot, and not easily demoed on a stage. But for anyone who compresses archives, scans files, opens terminals, manages images, syncs cloud folders, or wrangles network shares, right-click is less a convenience than a work rhythm.That is why Microsoft’s latest signal matters. Ash did not announce a finished Settings page, a specific Insider build, or a release date. He said Microsoft is working on context menus that are faster, simpler by default, and configurable to what users use most. In Windows terms, that last phrase is the rupture.
For years, Microsoft’s answer to context-menu clutter has been curation from above. Windows 11 introduced a cleaner-looking primary menu and pushed older or less-modern integrations behind “Show more options.” The result was visually calmer, but operationally messier: one menu for Microsoft’s design principles, another for the user’s actual workflow.
A configurable context menu would acknowledge what the Windows 11 redesign initially resisted. There is no single “clean” right-click menu that works equally well for a home user, a developer, a photographer, a sysadmin, and a gamer with five shell extensions installed. The operating system can provide defaults, but the person doing the work needs a vote.
The Old Menu Became a Museum of Installed Software
The old Windows context menu did not become chaotic because users loved chaos. It became chaotic because Windows made shell integration powerful, durable, and broadly available. A backup tool could add a restore action. A compression utility could add archive commands. A graphics driver could add display options. A security suite could add scan commands. A cloud client could add sharing and sync controls.That openness was one of Windows’ great strengths. It was also a long-running UX debt machine. Every installer wanted a piece of the right-click menu because the menu was close to the user’s intent: this file, this folder, this image, this executable, this desktop background. If the program could appear at that exact moment, it felt integrated with Windows itself.
The trouble is that the menu had no strong sense of scarcity. Each vendor could argue that its command was useful, and each individual addition seemed harmless. Over time, the accumulated result became the familiar Windows sprawl: duplicate entries, nested submenus, obsolete handlers, vendor-branded commands, icons from three design eras, and delays caused by shell extensions that had to be queried before the menu could settle.
This is the part of the story Microsoft rarely says out loud. Windows’ backward compatibility is not abstract. It has a visible texture. Sometimes that texture is a 25-year-old accounting package still running on a modern PC; sometimes it is a right-click menu that looks as though every app installed since the Clinton administration left a forwarding address.
Windows 11 Solved the Clutter by Moving It One Click Away
When Windows 11 arrived in 2021, the new context menu was one of the most obvious signs that Microsoft wanted the OS to feel less like a dense control panel and more like a modern consumer platform. The menu adopted rounded corners, cleaner spacing, and a row of icon-first commands for common actions like cut, copy, rename, share, and delete. The visual message was clear: Windows was no longer going to dump the entire shell-extension junk drawer in front of every user.The design had logic. The old menu had become too long, too inconsistent, and too dependent on third-party extensions that could slow down basic interactions. Microsoft also had to accommodate touch and pen input better than the dense Windows 10 menu did. A modernized primary menu gave Microsoft a place to enforce a cleaner pattern while preserving the old extensibility model through “Show more options.”
But the compromise immediately irritated the people most likely to notice it. The new menu often hid exactly the commands that made right-click valuable. Users who relied on 7-Zip, Git tools, advanced image editors, terminal launchers, or device-vendor utilities found themselves performing an extra click dozens of times a day. In some workflows, Windows 11 had not reduced complexity; it had inserted a toll booth in front of it.
That is the deeper criticism. The Windows 11 menu was not wrong because minimalism is bad. It was wrong because it mistook Microsoft’s preferred command hierarchy for the user’s. Clean design becomes paternalism when it removes agency from the people who understand their own work.
“Show More Options” Became the Button That Summed Up Windows 11
Few interface labels have carried as much symbolic weight as “Show more options.” On paper, it is a sensible overflow command. In practice, it became a daily reminder that Windows 11 often knows the thing you want exists but has decided you should not see it yet.That extra click mattered because context menus are about immediacy. A right-click is not a trip to Settings. It is a fast, local act: I have selected this object, and I want to do something to it now. If the desired command is hidden behind a second menu, the interaction loses the very quality that made it useful.
The keyboard shortcut workaround never fully solved the problem. Shift-right-click and Shift+F10 may satisfy longtime Windows users who are comfortable with hidden affordances, but they do not fix the underlying design tension. A workaround is not the same as a preference, and a shortcut is not the same as a first-class setting.
The reaction also exposed a split in Microsoft’s audience. Casual users may never notice the missing commands because they rarely use shell extensions. Enthusiasts and IT pros notice immediately because their Windows installations are often defined by them. A clean default is good; a locked-down clean default is where the trouble starts.
Configuration Is the Missing Middle Ground
If Microsoft follows through, configurability could turn the context-menu debate from a binary fight into a practical compromise. The choice should not be “modern menu with hidden legacy commands” versus “old menu restored through registry edits.” Windows needs a middle layer where the user can decide which commands deserve prime real estate.The best version of this would not simply expose a chaotic checklist of every possible shell verb. That would recreate the old problem in Settings form. Microsoft needs a disciplined customization model: pin, hide, reorder, reset, and perhaps per-file-type control for advanced users. The menu should stay sane by default, but it should stop pretending that every user has the same definition of sane.
There is also a performance angle. Context menus can feel sluggish when Windows has to enumerate handlers, query extensions, or wait on poorly behaved integrations. A configurable model could allow Windows to defer or suppress rarely used handlers without severing compatibility. The user gets speed; legacy apps keep their escape hatch.
The obvious risk is that Microsoft ships a shallow version of customization that disappoints both camps. If users can only toggle a few Microsoft-approved entries, the change will be cosmetic. If third-party entries remain uncontrollable, the menu will still be a landlord problem: Microsoft owns the building, but every app gets to hang a sign in the lobby.
Developers Are Part of the Problem, and Microsoft Knows It
Context-menu clutter is not only a user-interface issue; it is an ecosystem-governance issue. Windows has spent decades encouraging developers to integrate deeply with the shell. Now Microsoft has to persuade those developers to behave more politely without breaking the software people rely on.The company has already been moving in that direction through modern app patterns and developer guidance. Windows 11’s primary menu is not meant to be a free-for-all clone of the old menu. Developers are expected to use modern extension mechanisms if they want their commands to appear cleanly in the new surface. That makes sense architecturally, but it also shifts burden onto software vendors that may have little incentive to revisit working code.
This is where Windows differs from more tightly controlled platforms. Microsoft cannot simply decree that old shell extensions vanish. Enterprises depend on them. Utilities depend on them. Niche workflows depend on them. The history of Windows is full of strange but business-critical integrations that look ugly until the day they save someone hours of work.
A better context menu therefore has to be both stricter and more forgiving. It should enforce clearer grouping, reduce duplicate noise, and discourage vendors from spraying commands across the top level. But it also has to preserve a route for older tools, because compatibility is still one of Windows’ strongest selling points.
Enterprise IT Will Care Less About Beauty Than Control
For administrators, the promise of a configurable context menu raises immediate management questions. Can the settings be controlled by policy? Can organizations hide consumer cloud commands on managed devices? Can security teams suppress risky shell extensions? Can default layouts be exported, deployed, and reset?These are not edge cases. In managed Windows environments, the context menu can become a support problem. Users see commands for apps they do not understand, cloud services they are not supposed to use, or legacy tools that remain installed for one department but confuse another. A right-click menu that is merely customizable per user is useful; one that is manageable at scale is far more consequential.
Performance also matters in enterprise fleets. A sluggish context menu might sound trivial compared with endpoint detection, patch compliance, or identity hardening, but small delays repeated across thousands of users become real friction. Explorer hangs and shell-extension conflicts are the kind of mundane problems that generate tickets precisely because they interrupt basic work.
Microsoft has an opportunity to treat context-menu configuration as part of Windows manageability rather than a personalization toy. If the company exposes sane policy controls, IT departments could standardize cleaner menus, reduce help-desk confusion, and still allow exceptions where specialized tools are needed.
The Start Menu Shift Shows a Broader Retreat From One-Size-Fits-All Design
The context-menu rethink does not appear in isolation. Microsoft has also been testing and discussing broader Windows 11 interface changes, including more flexible Start menu behavior and additional personalization around areas that many users consider promotional or distracting. The pattern is hard to miss: Windows 11 launched with strong design opinions, and Microsoft is now sanding down the places where those opinions became constraints.That does not mean Microsoft is abandoning its Windows 11 aesthetic. The company still wants cleaner surfaces, modern controls, and layouts that work across input types. But it seems more willing to admit that a clean interface is not the same as a rigid one. Users can tolerate change when they are given meaningful control over the outcome.
The Start menu and the context menu are linked by a common complaint. In both places, Windows 11 often reorganized familiar workflows around Microsoft’s preferred defaults. Recommended items, pinned layouts, hidden commands, centered taskbar behavior, and simplified menus all communicated a design philosophy: fewer visible choices, more curation, more consistency.
That philosophy was not foolish. Windows had become visually and behaviorally inconsistent. But Windows users are not iPad users, and Windows PCs are not appliances. The platform’s identity is bound up with adaptation: registry tweaks, PowerToys, Group Policy, shell extensions, taskbar habits, scripts, and utilities. When Microsoft forgets that, even elegant design can feel hostile.
The Real Contest Is Between Defaults and Ownership
The most important word in Ash’s comment may be “default.” Faster and simpler by default leaves room for a more capable menu by choice. That distinction is the difference between a redesign that users accept and one they route around with hacks.Defaults matter because most people never change them. Microsoft should absolutely improve the out-of-box context menu for the majority of users who do not need five compression commands or three cloud-sharing providers at the top level. A shorter menu is easier to scan, less intimidating, and less prone to accidental clicks.
Ownership matters because Windows is used by people whose workflows are deeper than the default. A developer may want “Open in Terminal” and Git commands immediately available. A designer may want image conversion and editing actions. An administrator may want hashing, permissions, and security tools. A writer may want archive, rename, and cloud-share actions but never vendor telemetry shortcuts.
The winning design is not the one that guesses perfectly. It is the one that makes guessing less important. If Windows can learn from usage, expose clear controls, and allow users to promote or demote commands, Microsoft can keep the menu clean without freezing it in someone else’s idea of usefulness.
The Danger Is Another Half-Modern Shell
Windows 11’s context-menu problem is part of a larger Windows problem: half-modernization. The OS often introduces a new interface layer while preserving the old one beneath it, producing a system that is simultaneously refreshed and unfinished. Settings and Control Panel are the classic example. The modern context menu and legacy “Show more options” menu are another.This layering is understandable. Windows cannot be rewritten like a startup app. Every major interface change has to pass through decades of compatibility, localization, accessibility, automation, enterprise deployment, and third-party integration. The result is evolutionary design, not clean-slate design.
But users experience the seams, not the rationale. They see two menus. They see commands that appear in one place but not another. They see modern icons beside older dialog boxes. They see a system that asks them to trust a redesign while repeatedly sending them back to the legacy interface to finish the job.
A truly revised context menu must reduce that seam. If “Show more options” remains the place where real work happens, the redesign has failed. If the modern menu becomes configurable enough that most users rarely need the legacy menu, Microsoft will have done something more valuable than repainting Explorer.
Power Users Should Be Optimistic, but Not Patient
There is reason to be optimistic. Microsoft’s language suggests it understands three distinct complaints: speed, clutter, and lack of control. That is a more complete diagnosis than simply promising a prettier menu. It also arrives after years of public frustration, registry workarounds, third-party customization tools, and Insider-era feedback.Still, Windows users have learned to wait for implementation before applauding intent. Microsoft often announces direction before details, and the details matter enormously here. A toggle buried in Settings would not be enough. A limited list of first-party commands would not be enough. A configuration model that cannot manage third-party shell extensions would not be enough.
The company also has to avoid turning customization into yet another Microsoft-account-adjacent cloud preference system. Context-menu settings should be local, transparent, exportable, and manageable. Enthusiasts will want control; enterprises will want policy; developers will want documentation; accessibility users will want predictable behavior. A serious redesign must serve all four.
Most of all, Microsoft has to respect muscle memory. Users can adapt to better interfaces, but they resent churn that slows them down. If commands move, hide, or reappear unpredictably, the menu will feel less like a tool and more like a negotiation.
The Right-Click Menu Becomes a Test of Windows 11’s Maturity
This is why the context-menu overhaul is more than a minor UX story. Windows 11 is now old enough that its launch-era design bets can be judged by their consequences. Some have aged well. Some have been softened. Some, like the right-click menu, became symbols of a broader tension between elegance and control.A mature Windows 11 does not need to abandon modern design. It needs to stop confusing modern design with enforced minimalism. The best desktop interfaces are not the ones with the fewest options; they are the ones that reveal the right options at the right time and let experienced users shape the environment around real work.
That is especially important as Microsoft pushes AI features, cloud services, and cross-device experiences deeper into Windows. The more the company asks users to accept new layers, the more it must preserve trust in the old ones. Right-click is one of those old layers. If Microsoft can make it faster and cleaner without making it less useful, it earns credibility for bigger changes.
The reverse is also true. If the redesign becomes another constrained surface where Microsoft decides what matters, users will keep restoring the classic menu, installing shell replacements, and treating Windows 11 as something to be corrected after installation. That is not the relationship Microsoft should want with its most invested customers.
A Cleaner Menu Will Only Matter If Users Can Keep It Clean
Microsoft’s opportunity is simple to describe and hard to execute: make the context menu useful before it becomes messy, and configurable before users reach for the registry. The next version should treat right-click not as a dumping ground and not as a showroom, but as a personal command surface.Here is what will matter when the overhaul reaches real Windows PCs:
- Microsoft needs to provide real user control over which commands appear in the primary context menu, not just a cosmetic reshuffle of built-in actions.
- Third-party shell extensions need clearer grouping and restraint, because the old model allowed every installer to behave as if its command deserved top billing.
- The legacy “Show more options” menu should become a safety net, not the place power users must visit dozens of times a day.
- Enterprise administrators will need policy controls if Microsoft wants this redesign to matter beyond consumer laptops.
- Performance improvements must be measurable in ordinary File Explorer use, because a prettier menu that still hesitates will not win back skeptics.
- The design should preserve Windows’ compatibility advantage while finally giving users a practical way to suppress the clutter that compatibility created.
References
- Primary source: Research Snipers
Published: 2026-06-11T07:05:07.664527
Loading…
researchsnipers.com - Related coverage: windowscentral.com
Windows 11's cluttered and controversial context menus are going away | Windows Central
Simpler, configurable context menus are on the way to Windows 11.www.windowscentral.com - Related coverage: techradar.com
In a shock move from nowhere, it seems Microsoft is finally giving Windows 11 users the ability to configure the right-click menu | TechRadar
Right-click the right waywww.techradar.com - Related coverage: windowslatest.com
Microsoft admits Windows 11's right-click menu is a mess, will let you customize it after years of complaints
Microsoft has confirmed that it'll let you customize the context menu to your liking, which means you'll be able to add or remove items.
www.windowslatest.com
- Related coverage: betanews.com
Loading…
betanews.com - Related coverage: whokeys.com
Loading…
www.whokeys.com
- Related coverage: windowsforum.com
Windows 11 Context Menus Reworked: Faster, Simpler, and Finally Configurable
Microsoft’s Windows design lead said on June 3, 2026, that Windows 11 context menus are being reworked to become faster, simpler by default, and configurable around the actions people use most. That is a small sentence with a long shadow. The right-click menu was supposed to be one of Windows...
windowsforum.com
- Related coverage: techyorker.com
Loading…
techyorker.com - Related coverage: tomshardware.com
How to Add Custom Shortcuts to the Windows 11 or 10 Context Menu | Tom's Hardware
Add new options that appear when you right click.www.tomshardware.com - Related coverage: memstechtips.com
How To Customize The Context Menu In Windows 11 With Nilesoft Shell
Nilesoft Shell is a free context menu manager for Windows 10/11. Remove Show more options, add custom shortcuts, enable dark mode, and apply blur effects.
memstechtips.com
- Related coverage: howtogeek.com
How to Get the Old Context Menus Back in Windows 11
Begone, weird new context menu!
www.howtogeek.com
- Related coverage: how2shout.com
Loading…
www.how2shout.com - Related coverage: askwoody.com
- Related coverage: u3ahavelocknorth.com
- Related coverage: fullcirclecomputing.com
What's New in Windows 11 Quick Reference
Handy What's New in Windows 11 with commonly used shortcuts, tips and tricks. Free for personal and professional training.www.fullcirclecomputing.com
- Official source: techcommunity.microsoft.com
Windows 11: Turn the "Show more options" context menu into a slide down menu | Microsoft Community Hub
Turn the "Show more options" context menu into a slide down menu and show those extra options in modern style Change the Windows 11 context menu so that...
techcommunity.microsoft.com
- Official source: support.microsoft.com
File Explorer in Windows - Microsoft Support
Find and open File Explorer in Windows, and customize Quick access by pinning and removing files and folders.
support.microsoft.com
- Official source: learn.microsoft.com
Loading…
learn.microsoft.com - Related coverage: allthings.how
Windows 11’s right‑click menu is getting split, context‑aware menus
Microsoft is testing a new “Split Context Menu” that groups related actions, trims duplicates, and can cut menu height by up to 38%.
allthings.how
- Official source: answers.microsoft.com
Loading…
answers.microsoft.com - Official source: developer.microsoft.com
Loading…
developer.microsoft.com - Related coverage: cincodias.elpais.com
Loading…
cincodias.elpais.com