Cool_Tools/ExplorerPatcher
1
0
Fork 0
mirror of https://github.com/valinet/ExplorerPatcher.git synced 2025-02-25 22:38:10 +01:00
Code Releases Wiki Activity

Updated Reporting problems (markdown)

Valentin-Gabriel Radu 2022-01-30 02:53:18 +02:00
parent 2a2bcee906
commit 7536f13a2c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Reporting-problems.md

@ -64,4 +64,4 @@ ExplorerPatcher is provided AS-IS. I do my best to make it work under most circu
* **ExplorerPatcher running on Windows Insider Preview builds** is not supported. The reason is because code there changes so often that developing and maintaining patches against that is not feasible long term. Some features and the program may generally work, but active or long term support is not provided for these builds.
* **ExplorerPatcher running on preview stable builds (C and D releases)** is not supported. This mostly has to do with symbol unavailability, otherwise the program generally works as well as it does on public releases, so there shouldn't be much difference. Read more about how symbols affect ExplorerPatcher [here](https://github.com/valinet/ExplorerPatcher/wiki/Symbols).
* **ExplorerPatcher on ARM64** is not supported. This is because I do not own (or need) an ARM64 machine, so I cannot test it there. Some patches may be architecture specific; EP is not the average Electron-based web wrapper. It cannot run as-is, care has to be taken to natively compile and test it against that architecture. Emulation doesn’t cut it, in this case. If someone’s willing to pick up the port for the architecture, they have my support and maybe something comes out of it. But personally, at the moment, I have no plans of working on that.
* **ExplorerPatcher on Windows 10** is not supported. This should be pretty obvious from the headline of the project: "restore a productive working environment on Windows 11". I moved on from Windows 10 to Windows 11. I do not have time to fully test against both versions. I daily drive stable Windows 11 (builds based on 22000), so I test on that. If someone wants to help maintain a Windows 10 port, sure, they have all my support. As it stands now, PLEASE do not try running this on Windows 10. There are no checks for preventing you from doing so an you will probably brick your system; not really, but you should be prepared with knowledge to restore `explorer` to a non-crashing state (i.e. delete `dxgi.dll` from `C:\Windows` BY RENAMING IT TO `dxgio.dll` FIRST, starting `explorer`, confirming it no longer crashing, and then deleting `dxgio.dll`)
* **ExplorerPatcher on Windows 10** is not supported. This should be pretty obvious from the headline of the project: "restore a productive working environment on Windows 11". I moved on from Windows 10 to Windows 11. I do not have time to fully test against both versions. I daily drive stable Windows 11 (builds based on 22000), so I test on that. If someone wants to help maintain a Windows 10 port, sure, they have all my support. As it stands now, PLEASE do not try running this on Windows 10. There are no checks for preventing you from doing so an you will probably brick your system; not really, but you should be prepared with knowledge to restore `explorer` to a non-crashing state (i.e. delete `dxgi.dll` from `C:\Windows` BY RENAMING IT TO `dxgio.dll` FIRST, starting `explorer`, confirming it no longer crashing, and then deleting `dxgio.dll`; afterwards, press `Win`+`R`, type "control" - this will open Control Panel: use this to uninstall ExplorerPatcher from the system using Programs and Features in order to undo all the changes the installer made).