Found the internet!![Wholesome](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32"><rect fill-opacity="0"/></svg>)
How-To: Disable new context menu, Explorer command bar
No 3rd-party apps or patches or whatever, just a simple registry value.
Restart Explorer shell to take effect.
Disable new context menu:
reg.exe add "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve
Restore new context menu:
reg.exe delete "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}" /f
Disable Explorer command bar:
reg.exe add "HKCU\Software\Classes\CLSID\{d93ed569-3b3e-4bff-8355-3c44f6a52bb5}\InprocServer32" /f /ve
Restore Explorer command bar:
reg.exe delete "HKCU\Software\Classes\CLSID\{d93ed569-3b3e-4bff-8355-3c44f6a52bb5}" /f
![User avatar](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="256" height="256"><rect fill-opacity="0"/></svg>)
Thanks. Care to explain how does it work?
Edit: Basically, it overrides the values in HKLM which specify where the code for the COM components responsible for the new immersive context menu and the new command bar are located, providing empty values (for path and the threading model) so that Explorer fails to load the aforementioned components and the code falls back to the old code path where the ribbon or command bar is used. Right, that's how I get it looking a bit on it. A very smart approach, I might add. Have I got it right or...? Thanks.
Yup, that's exactly it.
It's pretty much the same effect as removing the listed components from HKCR, however modifying the OS entries in HKLM would require messing with ACLs or elevating to TrustedInstaller and would likely be reverted by feature updates, so just overriding in HKCU is a cleaner way to do this. And of course, this sort of UI change really should be a user preference setting. :)
HOLY MOTHER OF GOD, it' so much better now though i have to sacrifice the looks which tbh sucks. But, now i know what to do to switch between them.
So, this was really just a skinned file manager which explains the horribble latencies while browsing. I am just disappointed.
There's no real reason that a redesign should slow the explorer down so much. There's a clear issue here in that instead of actually redesigning explorer, they're tacking the new stuff on top as extensions. I'm sure that makes it easier to write things like the ribbon replacement, and normally I'd say that's fine but explorer is a critical part of the OS. COM interop is not the fastest thing in the first place, bad coding practices on top of that make for a really bad time.
I mean yeah, completely redesigning legacy applications might break them but idk
Thank you very much! Tried disabling the new context menu. Works on 10.0.22000 (Build 22000)
![User avatar](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="245" height="245"><rect fill-opacity="0"/></svg>)
Oh wow. Thank you.
Thanks to you, I just removed the only thing I hate about Windows 11: the new context menu.
The old search box is implemented in the component with CLSID {bc32b5-4eec-4de7-972d-bd8bd0324537}. The new one is in the component with CLSID {1d64637d-31e9-4b06-9124-e83fb178ac6e}. In the code from ExplorerFrame.dll, in the code that initializes the search box for each window (CUniversalSearchBand::InitializeSearchControl) there is a check where they initially set the CLSID of the search box to initialize to the "modern" one, and then call a method (CUniversalSearchBand::IsModernSearchBoxEnabled) that tells whether the new search box is enabled (for example, that method says it should not be enabled in Control Panel windows, that's why there you get the old box still). If the search box is determined to be disabled, the CLSID for the search box to create is switched to the CLSID for the old search box (also called CLSID_SearchBox, can be Googled). Of course, an in-memory patch would be to modify the CUniversalSearchBand::IsModernSearchBoxEnabled method and make it always return 0, but I also very much prefer static patches, so since patching the DLL is kind of out of the question and expanding on the idea proposed by the OP, I used the TreatAs emulation mechanism to have the new CLSID point to the old CLSID, so even though the new search box is determined to be enabled, CoCreateInstance with the new CLSID still invokes the old CLSID. In the spirit of OP's one liners, here are the commands to disable/enable the atrocious new search box:
Disable new search box
reg.exe add "HKCU\Software\Classes\CLSID\{1d64637d-31e9-4b06-9124-e83fb178ac6e}\TreatAs" /f /ve /t REG_SZ /d "{64bc32b5-4eec-4de7-972d-bd8bd0324537}"
Enable new search box
reg.exe delete "HKCU\Software\Classes\CLSID\{1d64637d-31e9-4b06-9124-e83fb178ac6e}" /f
Can you please change your OP to get these commands out of these boxes? Copying the text is a bitch.
Maybe a stupid question, but what exactly is the "Explorer command bar", and does disabling it bring back the old look? As much as I like 11 overall, the context menu stupidity and File Explorer reskinning are awful.
--EDIT-- For anyone who ran into something similar see edit below
I ran this and for some reason after restarting (even after restoring back/regedit key no longer there) my explorer just crashes every time I right click the desktop or try to open an explorer window. Anyone else have this issue?
--EDIT INFO-- So after some snooping, I figured out it is related to a 3rd party software that added a context menu to right click. Using this program http://www.nirsoft.net/utils/shexview.html , I disabled each 3rd party program that added a context menu. Turns out it was NVIDIA whomp whomp.
NVIDIA CPL Context Menu Extension Yes Context Menu NVIDIA Display Shell Extension 472.12 NVIDIA Shell Extensions NVIDIA Corporation No No No No No No C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_19c79fb6254e3b11\nvshext.dll {3D1975AF-48C6-4f8e-A182-BE0E08FA86A9} 9/21/2021 11:58:49 PM 10/5/2021 12:46:14 PM No Directory\Background A 129,144 No No
thanks. new context menu SUCKS.
are you reading this, microsoft? the new context menu SUCKS. having to click twice to open the "open with" cascade is a horrific design decision. it wasn't broken, you shouldn't have tried to fix it.
Otherwise I love everything about Win11. Been using it for a while and I've had 0 bugs! Just disappointed in whoever at MS put that Recommended Section in the Start Menu. Really, really despise it. I also think that the taskbar shouldn't go across the whole screen and it should dynamically 'grow'.
Like when you have more apps opened or pinned then the taskbar should take up the amount of space used. They could even give us more screen there and I don't think it would be a prob if the extra screen real estate given is on the left and right sides cause aren't phones like that? I also REALLY wish they would allow us to see All Apps by default and not the pinned ones.
Anyway purely my opinion.
32Yes, you read that right - Windows 11 is out now to download! You can find out more about Windows 11 here, read more about the upgrade process here, and download it by going to Settings > Update & Security > Windows Update and clicking Check for updates. If you would prefer to use the installation assistant, create installation media, or download the ISO file, you can find those here.
All other posts about it being available, screenshots of the Windows update screen, "just updated" posts, and anything similar will be removed, but a megathread for those will be coming soon.
Members
Online