New Version of ExplorerPatcher

LesFerch · Mar 4, 2024

spapakons said:
He meant Windows 11 with File Explorer set to look like Windows 10 (current Windows 11 mode uses tabs much like a browser, Windows 10 mode is the old familiar style).

Note that the "Windows 10 Ribbon" option is (mostly) switching to the Windows 10 Explorer. It's (almost) the same Explorer you get when you open the Control Panel on Windows 11 and click the up arrow. The main difference I see is that the Details pane is the one from the Windows 11 Explorer, but it's clearly the older Explorer code because "Also apply this template to all subfolders" works when the "Windows 10 Ribbon" option is selected.

Other than the Details pane, the other issue I see is that the size and position of the Explorer window is not remembered when in that mode. At least not for me. It's also not remembered using the patch here (which is also the patch used by WindHawk and my SwitchExplorer). The "Win 10 Ribbon UI" option in StartAllBack does remember the Explorer window size and position.

Stormbrain · Mar 4, 2024

Yeah I meant the Windows 10 Ribbon UI

I tested StartAllBack and yeah it remembers the windows size and position so I wonder what its doing differently

hdmi · Mar 4, 2024

spapakons said:
He meant Windows 11 with File Explorer set to look like Windows 10

No, not "look like". ExplorerPatcher restores the Windows 10 File Explorer that, thankfully, is still hidden inside Windows 11 (but is disabled by Microsoft on Windows 11).

hdmi · Mar 4, 2024

Stormbrain said:
so I wonder what its doing differently

Try an uninstall/re-install of ExplorerPatcher. To avoid unnecessary problems with ExplorerPatcher, always be sure to only use production builds of Windows 11/10.

Stormbrain · Mar 4, 2024

I have and the issue persists, ive even tried re-installing twice with a clean iso (no changes etc)

hdmi · Mar 4, 2024

Stormbrain said:
Windows 11 Build: 22631.315

Did you mean 22631.3155 (publicly released on February 13, 2024) ?

spapakons · Mar 4, 2024

When I had an issue with Explorer Patcher I downloaded the last version and reinstalled (in-place upgrade/repair), no need to uninstall first. Simply updating from Explorer Patcher didn't work. I cannot say for sure, but I think in my PC it opens the windows at the same position and size. I have to confirm it and post again.

LesFerch · Mar 4, 2024

Stormbrain said:
Yeah I meant the Windows 10 Ribbon UI

I tested StartAllBack and yeah it remembers the windows size and position so I wonder what its doing differently

I tested EP on several Windows 11 VMs. With the "Windows 10 Ribbon" option selected, Explorer always loads to the same size and position as found in the registry here:

HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell

If I switch back to the Windows 11 Explorer and change the Explorer window size and position, it updates the values in that registry key, but the values don't get updated if I'm running the Windows 10 Explorer.

@hdmi You're getting a different result?

hdmi · Mar 4, 2024

LesFerch said:
I tested EP on several Windows 11 VMs. With the "Windows 10 Ribbon" option selected, Explorer always loads to the same size and position as found in the registry here:

HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell

If I switch back to the Windows 11 Explorer and change the Explorer window size and position, it updates the values in that registry key, but the values don't get updated if I'm running the Windows 10 Explorer.

@hdmi You're getting a different result?

Yes, with the Windows 10 Ribbon option selected in ExplorerPatcher, for me, when I close/re-open File Explorer it correctly remembers its position and size. I also use Open-Shell with its Classic Explorer component for various additional tweaks to File Explorer. That is, also in addition to Winaero Tweaker and Ultimate Windows Tweaker. It's all still working as intended, and has been that ever since I selected the Windows 10 Ribbon in ExplorerPatcher such a long time ago that I can't even remember when.

Only sometimes, after finalizing the install of a Windows Cumulative Update via a reboot, explorer.exe fails to load. However, each time when this happens, I can still fix it by choosing to open Task Manager with Ctrl+Shift+Esc | Run new task to manually start explorer or by uninstalling/re-installing ExplorerPatcher as needed. (Entering %programfiles%\ExplorerPatcher\ep_setup /uninstall in Run new task uninstalls ExplorerPatcher.) That's the only minor inconvenience, aside from the fact that I sometimes have to reboot once more to get the new symbols to be downloaded automatically by ExplorerPatcher. Each time after it says that the symbols were downloaded successfully, I choose to reboot again just in case, i.e. to keep ExplorerPatcher from glitching sometimes, albeit these glitches can also be fixed by rebooting after they start occur (but rebooting before they can start to occur is what effectively causes them to be avoided altogether so, that's what I always prefer).

LesFerch · Mar 5, 2024

hdmi said:
Yes, with the Windows 10 Ribbon option selected in ExplorerPatcher, for me, when I close/re-open File Explorer it correctly remembers its position and size. I also use Open-Shell with its Classic Explorer component for various additional tweaks to File Explorer.

Open-Shell with its Classic Explorer component is an important difference. Once I installed that software, Explorer correctly remembered its position and size. After uninstalling Open Shell (and restarting) Explorer continued to remember its position and size. I assume this means that Open Shell made a helpful registry change that remained after uninstalling.

Now to track down that specific change....

hdmi · Mar 5, 2024

LesFerch said:
Open-Shell with its Classic Explorer component is an important difference. Once I installed that software, Explorer correctly remembered its position and size. After uninstalling Open Shell (and restarting) Explorer continued to remember its position and size. I assume this means that Open Shell made a helpful registry change that remained after uninstalling.

Now to track down that specific change....

It's one vital piece of free open source software alright.

Silbian · Mar 5, 2024

Stormbrain said:
I have and the issue persists, ive even tried re-installing twice with a clean iso (no changes etc)

If I correctly understood, your problem is same of mine. I mean, starting file explorer it starts in normal windows and not maximized as I choose in it's settings. I can maximize it but, when closed and restart.... normal window again. No way to overtake that little but annoying problem except... I uninstalled EP 62.3 and I checked file explorer, it starts again maximized. Than I reistalled EP 62.2 and everything runs fine so far.

P.S. I'm running Win 11 Home .3155 but another my PC with Win 11 Pro .3155 is working correctly with 62.3 and does not face same problem with file explorer maximized/normal windows, anyway... it's true that any PC is a case history.
Last but not least, I didn't understand why explorer patcher versions 62.3 has been "downgraded" by Valinet as "pre-release version" since I got it as normal update already some weeks ago.

LesFerch · Mar 5, 2024

Silbian said:
If I correctly understood, your problem is same of mine. I mean, starting file explorer it starts in normal windows and not maximized as I choose in it's settings. I can maximize it but, when closed and restart.... normal window again. No way to overtake that little but annoying problem except... I uninstalled EP 62.3 and I checked file explorer, it starts again maximized. Than I reistalled EP 62.2 and everything runs fine so far.

P.S. I'm running Win 11 Home .3155 but another my PC with Win 11 Pro .3155 is working correctly with 62.3 and does not face same problem with file explorer maximized/normal windows, anyway... it's true that any PC is a case history.
Last but not least, I didn't understand why explorer patcher versions 62.3 has been "downgraded" by Valinet as "pre-release version" since I got it as normal update already some weeks ago.

I'm researching this issue. It seems to be due to a Microsoft change. I built Windows 11 23H2 from ISO and did not apply updates (build 2428). No issue with the Windows 10 Explorer remembering its window size and position. On updated builds it's an issue, but overcome by installing Open Shell. I'm trying to isolate the relevant setting(s).

Silbian · Mar 5, 2024

LesFerch said:
I'm researching this issue. It seems to be due to a Microsoft change. I built Windows 11 23H2 from ISO and did not apply updates (build 2428). No issue with the Windows 10 Explorer remembering its window size and position. On updated builds it's an issue, but overcome by installing Open Shell. I'm trying to isolate the relevant setting(s).

Well, for sure it seems due to a Microsoft change, even I don't know why the different behavior between Home and Pro 3155 versions, anyway...
On both of them I have Open Shell 4.4.191 active, but the problem was present in Home version regardless of Open Shell.

hdmi · Mar 5, 2024

LesFerch said:
I'm researching this issue. It seems to be due to a Microsoft change. I built Windows 11 23H2 from ISO and did not apply updates (build 2428). No issue with the Windows 10 Explorer remembering its window size and position. On updated builds it's an issue, but overcome by installing Open Shell. I'm trying to isolate the relevant setting(s).

So basically, Open-Shell fixes Microsoft bugs even before Microsoft creates bugs (not wholly dissimilar to how Brink also bans new forum members before new forum members even get a chance to register an account, lol). Yet people keep still blaming tweak tools like ExplorerPatcher and Open-Shell.

LesFerch · Mar 9, 2024

I'm back to looking at this issue and it's definitely a user profile difference. I currently have a Windows 11 VM with EP installed and set to use the Windows 10 Explorer for two different accounts (both type Administrator). One account remembers the Explorer window size and position, the other account does not.

Normally, in a situation like that, it's relatively easy to find the difference (typically a registry setting found by comparing dumps of both user's HKCU hives), but the difference in this case is proving difficult to find. I'm sure I'll eventually find it, but I'd be happy if someone else beats me to it, as I've already spent way too much time spinning my wheels looking for the difference.

Silbian · Mar 9, 2024

LesFerch said:
I'm back to looking at this issue and it's definitely a user profile difference. I currently have a Windows 11 VM with EP installed and set to use the Windows 10 Explorer for two different accounts (both type Administrator). One account remembers the Explorer window size and position, the other account does not.

Normally, in a situation like that, it's relatively easy to find the difference (typically a registry setting found by comparing dumps of both user's HKCU hives), but the difference in this case is proving difficult to find. I'm sure I'll eventually find it, but I'd be happy if someone else beats me to it, as I've already spent way too much time spinning my wheels looking for the difference.

Thanks ! I did some further trials too, even after rolling back to EP 62.2 the issue fortunately didn't appear again, File Explorer opens maximized now.
Another disturbing issue was, opening File Explorer, often took up to 30 seconds to show drives and folders... and less responsive in general.
I firstly tried updating to KB5034848 ( Winver .3235 ), who instalIs a new version of Explorer.exe... I know is not recommended by EP Team to update cumulative previews... anyway.
EP 62.2 works with 3235 version too, no major issues but... File Explorer persists to be slow as before.
This morning I tried to unregister EP as shell extension, now File Explorer starts fast and increased its responsiveness... let see...

LesFerch · Mar 9, 2024

It's the ITBar7Layout value in the HKCU\Software\Microsoft\Internet Explorer\Toolbar\ShellBrowser key that determines if the Windows 10 Explorer remembers its size and position.

If Explorer is not remembering its size and position, run this script:

hdmi · Mar 9, 2024

Silbian said:
Thanks ! I did some further trials too, even after rolling back to EP 62.2 the issue fortunately didn't appear again, File Explorer opens maximized now.
Another disturbing issue was, opening File Explorer, often took up to 30 seconds to show drives and folders... and less responsive in general.
I firstly tried updating to KB5034848 ( Winver .3235 ), who instalIs a new version of Explorer.exe... I know is not recommended by EP Team to update cumulative previews... anyway.
EP 62.2 works with 3235 version too, no major issues but... File Explorer persists to be slow as before.
This morning I tried to unregister EP as shell extension, now File Explorer starts fast and increased its responsiveness... let see...

I always install Preview Cumulative Updates. Never had any problems with them that were impossible to be fixed right away i.e. via the usual Ctrl+Shift+Esc | Run new task | etc.. At worst, I had to wait half a day or so before Microsoft published the new symbols. I do have to keep the Windows 10 Ribbon option selected in the EP settings or else File Explorer acts like a gambling machine. But then, if I don't use EP, File Explorer always acts like a gambling machine, even after I do a clean install of Windows 11 on every PC, everywhere, and with no exceptions. So, I can't complain (about EP, that is...

).

P.S., I never register EP as a shell extension. But I always keep the "Receive pre-release versions, if available" enabled in the EP settings (even though it says that it's not recommended). My weather recently ~~broke~~ un-broke, but Google is what's to ~~blame~~ thank for that.

Silbian · Mar 10, 2024

hdmi said:
I always install Preview Cumulative Updates. Never had any problems with them that were impossible to be fixed right away i.e. via the usual Ctrl+Shift+Esc | Run new task | etc.. At worst, I had to wait half a day or so before Microsoft published the new symbols. I do have to keep the Windows 10 Ribbon option selected in the EP settings or else File Explorer acts like a gambling machine. But then, if I don't use EP, File Explorer always acts like a gambling machine, even after I do a clean install of Windows 11 on every PC, everywhere, and with no exceptions. So, I can't complain (about EP, that is... ).

P.S., I never register EP as a shell extension. But I always keep the "Receive pre-release versions, if available" enabled in the EP settings (even though it says that it's not recommended). My weather recently ~~broke~~ un-broke, but Google is what's to ~~blame~~ thank for that.

Got it with thanks, well, I installed today the EP pre-release 63.4, just to check if the File Explorer start delay will continue and... sometimes yes, it does without any reason.
Of course it happens only with my Win11 Home version, the Pro version of the other device works perfectly with EP 62.2 and same .3235 update.
Definitely useless to struggling myself to understand the reason why, both PCs have almost the same config and startup apps, of course some device drivers are different due to different hardwares.
To be clear about this strange behavior, here below the screenshots, it tooks ( measured ) around 20 seconds to show the normal aspect.

New Version of ExplorerPatcher

Well-known member

My Computer

Active member

My Computer

Jack of all trades – master of none

My Computers

Jack of all trades – master of none

My Computers

Active member

My Computer

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Well-known member

My Computer

Jack of all trades – master of none

My Computers

Well-known member

My Computer

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Jack of all trades – master of none

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

Attachments

My Computer

Jack of all trades – master of none

My Computers

Well-known member

Attachments

My Computers

Similar threads