New Version of ExplorerPatcher

hdmi · Aug 28, 2023

spapakons said:
I didn't remember of this shortcut, never used it, so I pressed the good old CTRL+ALT+DEL which works on all Windows versions since XP.

Pressing CTRL+SHIFT+ESC opens Task Manager on all versions of Windows since Windows 95.

spapakons · Aug 28, 2023

Never used it. I remember only stuff I have used more then once. Short memory...

AlwaysWhy · Aug 28, 2023

hdmi said:
Pressing CTRL+SHIFT+ESC opens Task Manager on all versions of Windows since Windows 95.

CTRL+ALT+DEL

hdmi · Aug 28, 2023

spapakons said:
Never used it. I remember only stuff I have used more then once. Short memory...

You never used Task Manager more than once?

spapakons · Aug 28, 2023

hdmi said:
You never used Task Manager more than once?

Never used the shortcut to directly launch Task Manager. I always go through CTRL+ALT+DEL.

spapakons · Sep 6, 2023

I just read in a Greek site that you can speedup File Explorer if you press F11 to go into full screen mode and then press F11 again or ESC to return to window mode. This allegedly works independently of Explorer Patcher, haven't yet tried myself. So if you feel File Explorer is too slow and that Search results take too long to appear, just try this and share your results. Press F11 to go into full screen mode and then press F11 again or ESC to return to window mode.

starbuck · Sep 7, 2023

Before I updated to build 22621.2215 (KB5029351), I uninstalled Explorer Patcher and then made sure I reinstalled using the current release of 22621.1992.56.3.

However, I get 5-6 Explorer crashes each day as follows:

Code:

Faulting application name: explorer.exe, version: 10.0.22621.2215, time stamp: 0xb9c28810
Faulting module name: twinui.pcshell.dll, version: 10.0.22621.2215, time stamp: 0xd43f0915
Exception code: 0xc000001d
Fault offset: 0x000000000067395e
Faulting process id: 0x0x252C
Faulting application start time: 0x0x1D9E1C781CDAED0
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\WINDOWS\SYSTEM32\twinui.pcshell.dll
Report Id: 27744f8f-5751-4870-aa35-a8c36f36352c
Faulting package full name:
Faulting package-relative application ID:

I've always had Explorer Patcher using the Windows 10 Ribbon Control Interface. It sounds like other users here are having an 'OK' time using the latest Explorer Patcher on 22621.2215 if I read the recent posts correctly? If so, any suggestions as to why I'm having such difficulty? Should I just uninstall the (KB5029351) and wait for newer version of Explorer Patcher I guess?

p.s. I don't use Open Shell

antspants · Sep 7, 2023

starbuck said:
Before I updated to build 22621.2215 (KB5029351), I uninstalled Explorer Patcher and then made sure I reinstalled using the current release of 22621.1992.56.3.

However, I get 5-6 Explorer crashes each day as follows:

Code:

Faulting application name: explorer.exe, version: 10.0.22621.2215, time stamp: 0xb9c28810 Faulting module name: twinui.pcshell.dll, version: 10.0.22621.2215, time stamp: 0xd43f0915 Exception code: 0xc000001d Fault offset: 0x000000000067395e Faulting process id: 0x0x252C Faulting application start time: 0x0x1D9E1C781CDAED0 Faulting application path: C:\WINDOWS\explorer.exe Faulting module path: C:\WINDOWS\SYSTEM32\twinui.pcshell.dll Report Id: 27744f8f-5751-4870-aa35-a8c36f36352c Faulting package full name: Faulting package-relative application ID:

I've always had Explorer Patcher using the Windows 10 Ribbon Control Interface. It sounds like other users here are having an 'OK' time using the latest Explorer Patcher on 22621.2215 if I read the recent posts correctly? If so, any suggestions as to why I'm having such difficulty? Should I just uninstall the (KB5029351) and wait for newer version of Explorer Patcher I guess?

p.s. I don't use Open Shell

I had the same issue. That many explorer restarts isn’t worth my time so I have simply removed it. I’ve read that Microsoft is addressing the explorer ribbon in the next major update, due to many users complaining.

hdmi · Sep 7, 2023

starbuck said:
It sounds like other users here are having an 'OK' time using the latest Explorer Patcher on 22621.2215 if I read the recent posts correctly? If so, any suggestions as to why I'm having such difficulty?

I already posted my answer to that question... when you install Open-Shell, make sure that the Classic Explorer component will be a part of what you are going to install. After Open-Shell has been installed, make sure to enable Classic Explorer Bar in File Explorer. Finally, change the Control Interface option to Windows 10 Ribbon in ExplorerPatcher. You may hide the Classic Explorer toolbar (via right-clicking on it) in File Explorer if you don't need this toolbar. If the issue still isn't fixed and you already tried the sfc /scannow (and dism /online /cleanup-image /restorehealth), try repairing your Windows 11 by doing an in-place upgrade (with the option to keep your apps and personal files).

Here are a few extra tips. Don't use any 3rd party AV and/or internet security suites. They interfere with Windows and various software running on Windows, enough to turn your PC that is working perfectly fine into major FOOBAR. Just don't download any viruses, protect your browser by running it under the supervision of Sandboxie-Plus. Not pointing any fingers here, but don't be stupid, like, don't use registry cleaners or programs with a nice GUI that promise to boost your PC performance by 450 percent. Before you jump to all sorts of ridiculous conclusions about what's causing the flurb, run some actual testing first. Like, don't just disable the Windows Search service in services.msc and keep it that way after complaining that File Explorer is acting slow... there exists a Search and Indexing Troubleshooter in Windows 11 for a reason, just like there also exists a Reset Windows Search script for a reason, and you can play with the whole garden of settings that let you determine what does versus what doesn't get indexed. You don't like to play with settings and experiment? Then buy a Macbook. lol [/rant]

starbuck · Sep 7, 2023

hdmi said:
I already posted my answer to that question... when you install Open-Shell, make sure that the Classic Explorer component will be a part of what you are going to install. After Open-Shell has been installed, make sure to enable Classic Explorer Bar in File Explorer. Finally, change the Control Interface option to Windows 10 Ribbon in ExplorerPatcher. You may hide the Classic Explorer toolbar (via right-clicking on it) in File Explorer if you don't need this toolbar. If the issue still isn't fixed and you already tried the sfc /scannow (and dism /online /cleanup-image /restorehealth), try repairing your Windows 11 by doing an in-place upgrade (with the option to keep your apps and personal files).

Just to make sure I understand you correctly @hdmi , the only was to get Explorer Patcher working nicely with .2215 build is to also run Open Shell?

I was trying to minimize the amount of things I install for the very reasons you cited about running extraneous utilities (I don't ever use registry 'optimizers' and all that nonsense that pretends to offer performance boosts). For me, everything was hunky dory with just Explorer Patcher until I applied the (KB5029351) update that rolled me up to .2215.

hdmi · Sep 8, 2023

starbuck said:
Just to make sure I understand you correctly @hdmi , the only was to get Explorer Patcher working nicely with .2215 build is to also run Open Shell?

I don't know if it is the only way. The only thing I can attest is that it works, at least for me. I'll also repeat that my laptop uses no "exotic" type of hardware components/configuration, this Medion laptop does not have any OEM drivers from Medion that could possibly interfere (because there simply aren't any), I'm using official generic drivers from Intel/Realtek on a fully updated Windows 11 "outsider" build... if you mean what I get.

starbuck said:
I was trying to minimize the amount of things I install for the very reasons you cited about running extraneous utilities (I don't ever use registry 'optimizers' and all that nonsense that pretends to offer performance boosts). For me, everything was hunky dory with just Explorer Patcher until I applied the (KB5029351) update that rolled me up to .2215.

As a matter of fact I run a whole bunch of utilities. I am a pragmatist, always trying to find what works to satisfy my own personal needs. The new File Explorer with the modern command bar that replaced the old Windows 10 Ribbon always had visible bugs, for as long as I can remember it. At least for me, reverting it to the Windows 10 Ribbon with ExplorerPatcher was what made these visible bugs disappear so, ExplorerPatcher is like bug spray according to what I have seen. The same thing goes for the Windows 11 taskbar or who knows maybe Microsoft has (at very long last) provided all the necessary fixes in that regard, but why should I even care if they did or still didn't, when, after all, using ExplorerPatcher to bring back the Windows 10 taskbar lets me effectively avoid all these shenanigans altogether. Each time when someone posts in another thread or elsewhere that we "should adapt" and "why should anyone care about making new Windows look like older Windows", I have to be careful to not keep laughing myself to death. I already tried to convince myself that this is because I am a Sagittarian and, according to the Greek Zodiac, a Chiron.

spapakons · Sep 8, 2023

As I posted before, just download latest Explorer Patcher and run it to install again (in-place upgrade). This fixed the crashes for me.

Hary · Sep 12, 2023

AlwaysWhy said:
CTRL+ALT+DEL

CTRL+SHIFT+ESC

hdmi · Sep 13, 2023

Hary said:
CTRL+SHIFT+ESC

Nah. The mouse button manufacturers would be losing too much money.

starbuck · Sep 13, 2023

spapakons said:
As I posted before, just download latest Explorer Patcher and run it to install again (in-place upgrade). This fixed the crashes for me.

Thanks, I missed that. This has turned into such a giga-thread its easy to miss somethings.

At any rate, @spapakons that seems to have worked and also seems ok with yesterday's September update to 22621.2283. I haven't had an explorer crash for 3 days and I was getting 5-6 daily

spapakons · Sep 13, 2023

I haven't checked lately my build number but since last time I made Explorer Patcher work never crashed again. I will do all updates and report back.

portex7000 · Sep 16, 2023

same problem here

spapakons · Sep 16, 2023

I have installed all Windows updates up to build 22621.2283 and updated to the latest Explorer Patcher version 22621.1992.56.3 no issues here. It seems that they are fixed. If you still have issues, don't check for updates from Explorer Patcher. Go to the site and manually download and install latest version (in-place upgrade/repair) in order to fix any issues due to corrupted files or settings.

Release 22621.1992.56.3 · valinet/ExplorerPatcher

Tested on OS build 22621.1992. Installer requires Internet connectivity. Details 1 Windows 10 Start menu: Fixed a bug that prevented the menu from working on OS builds 22621.1413 and newer (46c504...

github.com