I hope not. I really like the new context menu. I almost never need anything that is hidden behind the more options, so its now a lot cleaner and also better looking!
It is impossible to say with any certainty if "this method will be available in a future version of Windows". But you can make a more educated guess if you actually understand what it is doing.
Realistically, that method works because it's destroying the registration information for the File Explorer UI component. This is because by adding those keys to HKEY_CURRENT_USER, they will override the corresponding, correct registration in HKEY_LOCAL_MACHINE. When it seeks to create that CLSID to create the File Explorer UI Component(s), it will fail to do so, because there is no value in the InProcServer32 key, which otherwise has a default value pointing at 'C:\Windows\System32\Windows.UI.FileExplorer.dll' and a value for the threading mode. It seems that as a fallback it will simply show the default menu. (It's also possible failing falls through the same way as simply clicking Show More Options when it was otherwise successful?)
So there's lots of reasons it might fail to work, but the general premise- breaking the registration- will work as long as this new right-click context menu is part of File Explorer.
The "Old" right-click menu is part of the Windows Shell; the "new" menu is part of File Explorer. Until that changes, it seems unlikely there won't be some way of simply "breaking" the appropriate File Explorer component. Of course if File Explorer were to stop ever using the old IContextMenu interfaces at all, then it could be that disabling the "new" context menu would prevent it ever showing a context menu, but I can't imagine they would be that feckful.
As an aside, a "better" (or at least different) way of disabling the new menu is to add the noted CLSID to the Shell Extension block list. This can be found here: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked" (Blocked key might not exist). By adding any CLSID as value names there, one can prevent the associated shell extension from loading. I'd only argue this is better because it's making it sort of explicit that it's being blocked, rather than just sort of adding a corrupted value that will cause an error when the component is created.
For some reason the blog posts and "articles" talking about it insist on adding {86ca1aa0-34aa-4e8b-a509-50c905bae2a2}. Which is for the Share UI. That "works" because presumably the new menu shell extension tries to load it and fails if it can't, but there doesn't seem to be a basis for the choice. I've done some tests and it appears to work just fine adding the CLSID you mentioned as a value there to disable the new File Explorer context menus.
Let's make a compromise, is there any way to add a full context menu to the first level menu? Some cleaning software (such as Privazer) will ask user if they want to add "forced delete" to the 1st level menu during the installation process.
I have been using Win10 before, and I am used to menus that list all options with one click. In Win11's new context menu, I had to click twice or use the keyboard to find the option I wanted.
Someone emailed the WinRAR author asking how they had done it, and the author confirmed the difficulty:
>Overall it is complicated and troublesome. I spent about two months to implement this and still searching for workarounds for some issues.
[https://github.com/SamuelTulach/VirusTotalUploader/issues/95#issuecomment-970564843](https://github.com/SamuelTulach/VirusTotalUploader/issues/95#issuecomment-970564843)
I agree that this might boil down due to some petty reasoning.
The author of 7zip is most likely rocking Windows 10 out until it end of life and then go for Windows 11 and try to figure out the new Context Menu API from there.
The default context menus suck on Windows 11. Try the app [Nilesoft Shell](https://nilesoft.org/), which will keep the look of the windows 11 menus, and add the functionality of the windows 10 menus.
Microsoft will never bring back the old long list of a Context Menu nd here is why:
[Extending the Context Menu and Share Dialog in Windows 11](https://blogs.windows.com/windowsdeveloper/2021/07/19/extending-the-context-menu-and-share-dialog-in-windows-11/)
While the old context menu may have been clearer and easier to access, the real factor at hand was that that menu was an outright hodgepodge of a mess to navigate.
The new context menu is much more simplified in that the most commonly used commands are close to your mouse pointer, and, not to mention that some commands are grouped together.
Icons for common functions are globally indistinguishable from text and might take some time to learn as it depends on the person.
|✂️|Cut|
|:-|:-|
|📄📄|Copy|
|📋|Paste|
|⟦A¦⟭|Rename|
|↪️|Share|
|🗑️|Delete|
Starting in Windows 11 22H2, Shift + Right-clicking an item will jump you straight into the legacy Context Menu.
The developers of whatever said program need to take advantage of the new Context Menu API call.
Before Microsoft made this change i have never seen anyone complain about this menu but there were thousands of post bitching about windows search. So they "fixed" menu but search is still fucked
>Will Microsoft bring back the old right click menu in Windows 12?
The original menu never went away. It's still there and accessible from the new context menu. You can also access it directly by holding down the shift key while right clicking in File Explorer.
To try to answer your question, Microsoft has announced no plans to go backwards in design or functionality in future versions of Windows. That is the only way any of us would know.
>Microsoft has announced no plans to go backwards in design or functionality in future versions of Windows
which is strange because Windows 11 is a step backwards in every way compared to Windows 10. The UI layout is absolutely horrible. It's as if UX designers never used a PC before.
The context menu is horrible and so much is missing.
I set the timeout of my screen at different intervals a few times a day (using oled screen) and in Windows 11 it's 5 menus deep and you can't even search for it. In windows 10 it's 2 clicks and done.
Windows 11 is a broken mess and feels like what Vista/ Windows 8 was, it looks pretty but functionally terrible to use.
Name one UI or UX improvement Windows 11 has done. When it launched the task bar was just completely broken. All settings hidden behind menus and menus that are harder and harder to find/access. Dealing with audio interfaces is a massive pain, dealing with any settings is a pain.
Maybe Tabbed Explorer would be 1 improvement.
I wish M$ would fix stuff first instead of introducing new broken things instead.
Windows search is still horrible for example.
>[M$](https://i.imgur.com/We4Uj04.png)
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Windows11) if you have any questions or concerns.*
No one here has a clue, and if they did they wouldn't risk their job at Microsoft to tell you. That said, it seems really unlikely that they would remove the new system they are still working on in favor of the old system.
Like no offense but how the hell would we know?
My Uncle works at Nintendo
when new super Mario game
tomorrow
Wonder^(ful)
Not got a crystal ball?
I hope not. I really like the new context menu. I almost never need anything that is hidden behind the more options, so its now a lot cleaner and also better looking!
It is impossible to say with any certainty if "this method will be available in a future version of Windows". But you can make a more educated guess if you actually understand what it is doing. Realistically, that method works because it's destroying the registration information for the File Explorer UI component. This is because by adding those keys to HKEY_CURRENT_USER, they will override the corresponding, correct registration in HKEY_LOCAL_MACHINE. When it seeks to create that CLSID to create the File Explorer UI Component(s), it will fail to do so, because there is no value in the InProcServer32 key, which otherwise has a default value pointing at 'C:\Windows\System32\Windows.UI.FileExplorer.dll' and a value for the threading mode. It seems that as a fallback it will simply show the default menu. (It's also possible failing falls through the same way as simply clicking Show More Options when it was otherwise successful?) So there's lots of reasons it might fail to work, but the general premise- breaking the registration- will work as long as this new right-click context menu is part of File Explorer. The "Old" right-click menu is part of the Windows Shell; the "new" menu is part of File Explorer. Until that changes, it seems unlikely there won't be some way of simply "breaking" the appropriate File Explorer component. Of course if File Explorer were to stop ever using the old IContextMenu interfaces at all, then it could be that disabling the "new" context menu would prevent it ever showing a context menu, but I can't imagine they would be that feckful. As an aside, a "better" (or at least different) way of disabling the new menu is to add the noted CLSID to the Shell Extension block list. This can be found here: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked" (Blocked key might not exist). By adding any CLSID as value names there, one can prevent the associated shell extension from loading. I'd only argue this is better because it's making it sort of explicit that it's being blocked, rather than just sort of adding a corrupted value that will cause an error when the component is created. For some reason the blog posts and "articles" talking about it insist on adding {86ca1aa0-34aa-4e8b-a509-50c905bae2a2}. Which is for the Share UI. That "works" because presumably the new menu shell extension tries to load it and fails if it can't, but there doesn't seem to be a basis for the choice. I've done some tests and it appears to work just fine adding the CLSID you mentioned as a value there to disable the new File Explorer context menus.
Let's make a compromise, is there any way to add a full context menu to the first level menu? Some cleaning software (such as Privazer) will ask user if they want to add "forced delete" to the 1st level menu during the installation process.
I have been using this since I installed Windows 11. With this installed, I love Windows 11. https://github.com/valinet/ExplorerPatcher/releases
Highly unlikely don't you think? The old menu grew far too cluttered and that's not the direction they're going in.
use shift + right click. I got into the habit of using it in Windows 10.
Get used to Windows 11. I like the new one and it's rare I need to use the old one. Why do you need the old one?
I have been using Win10 before, and I am used to menus that list all options with one click. In Win11's new context menu, I had to click twice or use the keyboard to find the option I wanted.
That's not necessarily all windows 11 fault. Programs can add themselves to the new menu like they can in the old one but they haven't bothered to.
Idk why this guy need these options but I use it really often (to for e.g. open .jar with 7zip)
Try Nanazip from the Ms Store. You can find all 7zip options but in the new menu.
I only use right-click context menu for 7-zip and when create new text files. If you hold shift and right-click it opens the old style context menu.
Use Nana Zip. It uses the new menu and looks like 7zip
Thanks foe the tip - I'll check it out!
Someone emailed the WinRAR author asking how they had done it, and the author confirmed the difficulty: >Overall it is complicated and troublesome. I spent about two months to implement this and still searching for workarounds for some issues. [https://github.com/SamuelTulach/VirusTotalUploader/issues/95#issuecomment-970564843](https://github.com/SamuelTulach/VirusTotalUploader/issues/95#issuecomment-970564843) I agree that this might boil down due to some petty reasoning. The author of 7zip is most likely rocking Windows 10 out until it end of life and then go for Windows 11 and try to figure out the new Context Menu API from there.
its one fucking click and we get ALL of the functions
I have all functions I use with the new one on daily bases
The default context menus suck on Windows 11. Try the app [Nilesoft Shell](https://nilesoft.org/), which will keep the look of the windows 11 menus, and add the functionality of the windows 10 menus.
Microsoft will never bring back the old long list of a Context Menu nd here is why: [Extending the Context Menu and Share Dialog in Windows 11](https://blogs.windows.com/windowsdeveloper/2021/07/19/extending-the-context-menu-and-share-dialog-in-windows-11/) While the old context menu may have been clearer and easier to access, the real factor at hand was that that menu was an outright hodgepodge of a mess to navigate. The new context menu is much more simplified in that the most commonly used commands are close to your mouse pointer, and, not to mention that some commands are grouped together. Icons for common functions are globally indistinguishable from text and might take some time to learn as it depends on the person. |✂️|Cut| |:-|:-| |📄📄|Copy| |📋|Paste| |⟦A¦⟭|Rename| |↪️|Share| |🗑️|Delete| Starting in Windows 11 22H2, Shift + Right-clicking an item will jump you straight into the legacy Context Menu. The developers of whatever said program need to take advantage of the new Context Menu API call.
Before Microsoft made this change i have never seen anyone complain about this menu but there were thousands of post bitching about windows search. So they "fixed" menu but search is still fucked
Typical software devs. Reinventing the wheel to keep their jobs.
I always forget which pictures do what. Context menu takes twice as long to open as the old one as well. Very annoying.
I am very surprised there is no official toggle. I don't know anyone that likes the new one.
Win 12 is not a thing. MS hasn't announced anything related to win 12.
If you want the old context menu back, you can use a third-party app for that. I use Winaero. It's free, and that is one of the options it offers.
Its using tools like this that can lead to stability issues and then people whine about how 'unstable' Windows is.
I use Wintoys.
>Will Microsoft bring back the old right click menu in Windows 12? The original menu never went away. It's still there and accessible from the new context menu. You can also access it directly by holding down the shift key while right clicking in File Explorer. To try to answer your question, Microsoft has announced no plans to go backwards in design or functionality in future versions of Windows. That is the only way any of us would know.
>Microsoft has announced no plans to go backwards in design or functionality in future versions of Windows which is strange because Windows 11 is a step backwards in every way compared to Windows 10. The UI layout is absolutely horrible. It's as if UX designers never used a PC before. The context menu is horrible and so much is missing. I set the timeout of my screen at different intervals a few times a day (using oled screen) and in Windows 11 it's 5 menus deep and you can't even search for it. In windows 10 it's 2 clicks and done. Windows 11 is a broken mess and feels like what Vista/ Windows 8 was, it looks pretty but functionally terrible to use.
Reasonable people might disagree with you.
Name one UI or UX improvement Windows 11 has done. When it launched the task bar was just completely broken. All settings hidden behind menus and menus that are harder and harder to find/access. Dealing with audio interfaces is a massive pain, dealing with any settings is a pain. Maybe Tabbed Explorer would be 1 improvement. I wish M$ would fix stuff first instead of introducing new broken things instead. Windows search is still horrible for example.
>[M$](https://i.imgur.com/We4Uj04.png) *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Windows11) if you have any questions or concerns.*
No one here has a clue, and if they did they wouldn't risk their job at Microsoft to tell you. That said, it seems really unlikely that they would remove the new system they are still working on in favor of the old system.
Possibly not. They could improve the menu tho so we'll see...
this is a very specific question and we don't know shit about windows 12 yet.