New Version of ExplorerPatcher

spapakons · Sep 9, 2024

Once I hadn't updated Explorer Patcher, I was more than two versions behind and File Explorer would crash. The solution was to load Task Manager and kill the Explorer process. Then I loaded Microsoft Edge, downloaded latest Explorer Patcher version and installed it. If you update both applications regularly you shouldn't have any issues.

Wolfzz · Sep 10, 2024

ExplorerPatcher 22621.3880.66.5 Final

GitHub - valinet/ExplorerPatcher: This project aims to enhance the working environment on Windows

This project aims to enhance the working environment on Windows - valinet/ExplorerPatcher

github.com

Download ExplorerPatcher - MajorGeeks

ExplorerPatcher is an Open Source, portable executable that lets you customize the Windows 11 Start Menu, Taskbar, System Tray, File Explorer, and more.

www.majorgeeks.com

spapakons · Sep 10, 2024

Just a reminder:

Every time you update Explorer Patcher it closes all File Explorer windows and doesn't re-open them. If you have many File Explorer windows before updating Explorer Patcher and you don't want to manually re-open them, you can use a PowerShell command to save them, update Explorer Patcher and use another command after the update to restore them. Thanks for the fellow poster that had posted it, don't remember who he was. I have saved the instructions on a text file and I copy-paste them here:

Open a PowerShell and execute this command to SAVE open windows:

$a=(New-Object -ComObject Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}

Don't close the PowerShell window.

Update Explorer Patcher or restart File Explorer.

Execute this command to RESTORE open windows:

$a |% {explorer "$_"}

Million thanks again!

MaitieS · Sep 10, 2024

Since the newest version they were able to bring back Live Tiles for W10 Star Menu. Impressive work.

hdmi · Sep 10, 2024

spapakons said:
Just a reminder:

Every time you update Explorer Patcher it closes all File Explorer windows and doesn't re-open them. If you have many File Explorer windows before updating Explorer Patcher and you don't want to manually re-open them, you can use a PowerShell command to save them, update Explorer Patcher and use another command after the update to restore them. Thanks for the fellow poster that had posted it, don't remember who he was. I have saved the instructions on a text file and I copy-paste them here:

Open a PowerShell and execute this command to SAVE open windows:

$a=(New-Object -ComObject Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}

Don't close the PowerShell window.

Update Explorer Patcher or restart File Explorer.

Execute this command to RESTORE open windows:

$a |% {explorer "$_"}

Million thanks again!

This was my post: New Version of ExplorerPatcher

About 2 months ago I began writing another script that, provided that ExplorerPatcher settings | File Explorer | Control Interface: Windows 10 Ribbon is enabled, lets you restore open File Explorer windows in such a way that also restores all of the following:

their folderpath,
their window position and size,
their minimized/maximized/restored state,
their horizontal and vertical scrollbar positions, and
their selected items paths (if any).

It does have some limitations like, e.g., not being able to correctly restore a File Explorer window that is showing some Search results. The idea is that you run this script, then wait for the script to display a message before you update ExplorerPatcher or before you restart explorer. The script should ask you to press the Enter key. So, next, when you press the Enter key it should restore the File Explorer windows [that have been closed as a result of you updating ExplorerPatcher or as a result of you restarting explorer]. This specific script can be found in the 1st part of my post: What powershell scripts are you using

spapakons · Sep 10, 2024

It is working as it is. No need to enhance it. I only have to remember to save the open File Explorer windows (first part) before updating Explorer Patcher or restarting File Explorer. Then I execute the second part to restore them. Easy, well with a little help from copy-paste.

dacrone · Sep 10, 2024

put the first command into powershell ise and save it as a .ps1
do the same for the second command
create a shortcut to each .ps1
right click - properties - target box:

powershell.exe -ExecutionPolicy Bypass -File “C:\Path\to\ps1”

now you can just run one, do your update and run the second

*If those .ps1 dont work, you need to run this first (only once)

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted

hdmi · Sep 10, 2024

spapakons said:
It is working as it is. No need to enhance it. I only have to remember to save the open File Explorer windows (first part) before updating Explorer Patcher or restarting File Explorer. Then I execute the second part to restore them. Easy, well with a little help from copy-paste.

Well you could always decide to just run this instead:
$a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}
The pause command in it will make it ask you to press the Enter key to continue.

I agree that restoring open File Explorer windows based on their folderpath alone should usually be enough, but it isn't always enough.

hdmi · Sep 10, 2024

dacrone said:
put the first command into powershell ise and save it as a .ps1
do the same for the second command
create a shortcut to each .ps1
right click - properties - target box:

powershell.exe -ExecutionPolicy Bypass -File “C:\Path\to\ps1”

now you can just run one, do your update and run the second

*If those .ps1 dont work, you need to run this first (only once)

If you do that, then $a will return an empty string when the 2nd script is run, as the variable named a will not be found by it. The result will be the equivalent of running explorer "" so it has the same effect as when you simply run explorer (with no path parameter specified).

dacrone · Sep 10, 2024

i compiled both parts in separate ise tabs. ran the first, closed my 3 tabbed explorer instance, ran the second and it reopened all three but each in its own explorer window. it did not open a default explorer (to this pc, as explorer "" does)

spapakons · Sep 10, 2024

The condition is not close the PowerShell window during restart or it will not work. Creating two separate .ps1 files might not work. I will try the new version with the pause. If that works, I can save it as .ps1 file so I don't have to copy-paste the commands every time.

PS: I created a new text file with Notepad, copy-pasted the command
$a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}
and saved as .ps1 file (without the .txt at the end of course). I right-clicked on the file and selected Run with PowerShell. It didn't work, I just got some error message in red text but the PowerShell window closed before I could read it. Please tell me step-by-step how to make it work. Thanks. When I copy-paste the same command in a PowerShell window it works.

hdmi · Sep 10, 2024

dacrone said:
i compiled both parts in separate ise tabs. ran the first, closed my 3 tabbed explorer instance, ran the second and it reopened all three but each in its own explorer window. it did not open a default explorer (to this pc, as explorer "" does)

In PowerShell ISE, choosing File | New PowerShell Tab creates a different PowerShell session (PSSession). You can open other script tabs using the Open option in the File menu or create a new script tab via the New option. When you create a new script tab that belongs to the same session as the script tab that already is present in it, the variable still continues to exist in that session after the 1st script has been run in it. Whereas running
powershell.exe -ExecutionPolicy Bypass -File "C:\Path\to\ps1" causes your script file to be run in a new session. Similarly, opening a new PowerShell window also causes a new session to be created. That's why I wrote "Don't close the PowerShell window."

hdmi · Sep 10, 2024

spapakons said:
The condition is not close the PowerShell window during restart or it will not work. Creating two separate .ps1 files might not work. I will try the new version with the pause. If that works, I can save it as .ps1 file so I don't have to copy-paste the commands every time.

PS: I created a new text file with Notepad, copy-pasted the command
$a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}
and saved as .ps1 file (without the .txt at the end of course). I right-clicked on the file and selected Run with PowerShell. It didn't work, I just got some error message in red text but the PowerShell window closed before I could read it. Please tell me step-by-step how to make it work. Thanks. When I copy-paste the same command in a PowerShell window it works.

Create a new desktop shortcut that has

Code:

powershell -C $a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}

in its Target field.

spapakons · Sep 11, 2024

hdmi said:
Create a new desktop shortcut that has

Code:

powershell -C $a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}

in its Target field.

It didn't work because I also have PowerShell 7.4.5 installed. It opens the folder containing version 7 and 7.4.5 of PowerShell. Never mind, I just copy-paste the combined command (with the pause) and it works fine.

hdmi · Sep 11, 2024

spapakons said:
It didn't work because I also have PowerShell 7.4.5 installed. It opens the folder containing version 7 and 7.4.5 of PowerShell. Never mind, I just copy-paste the combined command (with the pause) and it works fine.

Code:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -c $a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}

spapakons · Sep 11, 2024

hdmi said:

Code:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -c $a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}

That worked, thanks! All I have to do is run the shortcut I created, update Explorer Patcher, wait for File Explorer to load again and then press ENTER to restore saved windows. Thanks!

PS: For the PowerShell 7 64-bit version, create a new shortcut and copy-paste this code in the target field:

Code:

"C:\Program Files\PowerShell\7\pwsh.exe" -c $a=(New-Object -Com Shell.Application).Windows() |% {$_.Document.Folder.Self.Path}; pause; $a |% {explorer "$_"}

Wolfzz · Sep 12, 2024

ExplorerPatcher 22621.3880.66.6 Pre-Release

GitHub - valinet/ExplorerPatcher: This project aims to enhance the working environment on Windows

This project aims to enhance the working environment on Windows - valinet/ExplorerPatcher

github.com

Download ExplorerPatcher - MajorGeeks

ExplorerPatcher is an Open Source, portable executable that lets you customize the Windows 11 Start Menu, Taskbar, System Tray, File Explorer, and more.

www.majorgeeks.com

Hary · Sep 12, 2024

Wolfzz said:
ExplorerPatcher 22621.3880.66.6 Pre-Release

GitHub - valinet/ExplorerPatcher: This project aims to enhance the working environment on Windows

This project aims to enhance the working environment on Windows - valinet/ExplorerPatcher

github.com

Download ExplorerPatcher - MajorGeeks

ExplorerPatcher is an Open Source, portable executable that lets you customize the Windows 11 Start Menu, Taskbar, System Tray, File Explorer, and more.

www.majorgeeks.com

Unfortunately, I no longer use EP because I cannot (defender) nor know how to (powershell) install it, there are certainly other users like me who had to give up after several years of using EP

spapakons · Sep 12, 2024

If you get a false positive, disable Windows Defender temporarily, install Explorer Patcher and enable it again. Further updates done from Explorer Patcher should not have any issues installing.

Hary · Sep 12, 2024

spapakons said:
If you get a false positive, disable Windows Defender temporarily, install Explorer Patcher and enable it again. Further updates done from Explorer Patcher should not have any issues installing.

I'll see how I function without EP, I love that program, but I'm getting more and more tired of the "fight" with Microsoft, which acts as if EP is their enemy No.1

New Version of ExplorerPatcher

Well-known member

My Computers

Well-known member

ExplorerPatcher 22621.3880.66.5 Final​

My Computer

Well-known member

My Computers

New 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

Jack of all trades – master of none

My Computers

Well-known member

My Computer

Well-known member

My Computers

Jack of all trades – master of none

My Computers

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Jack of all trades – master of none

My Computers

Well-known member

My Computers

Well-known member

ExplorerPatcher 22621.3880.66.6 Pre-Release​

My Computer

Well-known member

ExplorerPatcher 22621.3880.66.6 Pre-Release​

My Computer

Well-known member

My Computers

Well-known member

My Computer

Similar threads

ExplorerPatcher 22621.3880.66.5 Final

ExplorerPatcher 22621.3880.66.6 Pre-Release

ExplorerPatcher 22621.3880.66.6 Pre-Release