-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
ExplorerPatcher Won't Install #4280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Start11 and EP are not meant to be used at the same time, pick one to be installed. please see this for more info: https://github.com/valinet/ExplorerPatcher/wiki/ExplorerPatcher's-taskbar-implementation |
I still get the same error after uninstalling Start11, however this time the properties dialog shows up and it works correctly after selecting "Windows 10 (ExplorerPatcher)" Any suggestions for Start Menu replacements that work on ARM64? Since Start11 and StartAllBack also conflict and there isn't an ARM64 version of Open Shell yet. |
Not yet for open shell, but you can keep an eye on the request for arm64 support here: Open-Shell/Open-Shell-Menu#553 what error message are you referring to? |
The above error message: "An error has occured...". There is a pull request to add ARM64 support already. I wonder why said patch hasn't been integrated yet? |
you can ask there why the pull request to add arm64 support hasn't been accepted. as for that error message, uninstall EP then install EP again and you should not get it. see here for how to uninstall: https://github.com/valinet/ExplorerPatcher/wiki/Installer-How-To |
Funnily enough, you can't even run the x64 setup program on recent WoA releases as it displays this error message, even though there have been reports of it running fine under the Prism emulator. Even if I remove the "Application Compatibility" component using NTlite it still doesn't run. The only difference it that it doesn't display the above error, just silently failing instead. |
Same issue on my side. It seems like Microsoft is now blocking ExplorerPatcher from the Compatibility Assistant. Here's the entry in the Event Viewer
|
What build of Windows 11 are you running? I'm running build 26100.3775 and ExplorerPatcher setup runs fine. It's just OpenShell that fails. |
If you're using an arm laptop, install the The file |
I did. I was referring to Open Shell's x64 setup. |
Just to be clear, no one should be running the x86-64 version of EP on an arm laptop. You should be running the arm64 version of EP instead on your arm laptop. |
I am. It works without problems with Start11: ExplorerPatcher is managing the tasbar: The only feature that doesn't work with both installed is the right-click on taskbar items. |
You installed the arm version then. Because otherwise the taskbar you've selected will not work. |
Windows 11 Enterprise build 26100.3775 on a VMware ESXi with AMD Epyc CPU. OpenShell or Start11 are NOT installed. Also, SecurityHealth in KB5007651 (10.0.27777.1008) has been installed. |
This issue is about running EP on arm64 with openshell x64 version. Please create a new issue. |
@VerizonLover Is your issue resolved? Try updating to 68.1, and screenshot the error. It shows where the install failed. |
He means 68.2 :) |
Before reporting your issue
Repro ExplorerPatcher versions
ExplorerPatcher 67.1
Repro Windows Versions
Windows 111 24H2 26100.3775
3rd party tweak software installed
Start11
Describe the bug
When installing ExplorerPatcher from the pre-built ARM64 package that has the (taskbar DLLs) I'm getting the following error:
But when I compile from the repo source I don't get the error message and it installs fine.
Also, downloading the seperate taskbar DLL does not make it magically work. Even after copying the ep_taskbar DLLs to the installation directory it still says "not supported" when I try to select the Windows 10 style taskbar.
Expected outcome
ExplorerPatcher properties shortcut is created
Actual outcome
ExplorerPatcher properties shortcut is not created
Additional info
No response
Crash Dumps
No response
Media
No response
The text was updated successfully, but these errors were encountered: