the thing about versioning is I don't feel like I'm a maintainer of this mess in a perfect world we would host it on GitHub and maybe even update uupdump.net to the current code, but it's not possible at this moment anyway, I'm going to drop Electron app and PHP-built-in server support and release new version based on PHP & Apache HTTP server (it's much faster and way more stable), version number in filename and some scripts wouldn't hurt
admin rights are not mandatory, it just works for me without elevated rights on 22621 Host OS I've added auto elevation in other scripts which really requires it
My bad. I got an error message when executing the mlink statements of the script at #4841; but the applications worked (the mlink don't figure in the latest release).; admin rights are not requested.
In the latest version, the file "uupdump-run-website.cmd" has been replaced by "uupdump-run-apache.cmd". Slightly confusing, but it works.
PHP built-in server was replaced with much more faster and way more reliable Apache HTTP Server https://forums.mydigitallife.net/posts/1781105 you can find old scripts in the "scripts" folder as a fallback if Apache isn't working for some reason
"uupdump-run-apache.cmd" works just fine. It was just confusing for a minute because of the name change.
But this problem above occurred because of downloading the version of "uup-converter-wimlib" in the old version overwriting the version you downloaded manually. so it was necessary to delete these lines. Currently, this procedure is no longer necessary. However, you can modify the script to use PwSh if you don't have native PowerShell 5.1 on your system. Code: where.exe /F PowerShell.exe >nul 2>&1 && ( set "PSexe=PowerShell.exe" ) if "%PSexe%" equ "" where.exe /F PwSh.exe >nul 2>&1 && ( set "PSexe=PwSh.exe" ) %PSexe% -NoProfile -ExecutionPolicy Unrestricted .\files\depends_win.ps1 || (pause & exit /b 1) or Code: where.exe /F PowerShell.exe >nul 2>&1 && ( set "PSexe=PowerShell.exe" ) if "%PSexe%" equ "" where.exe /F PwSh.exe >nul 2>&1 && ( set "PSexe=PwSh.exe" ) %PSexe% -NoProfile -ExecutionPolicy Unrestricted .\files\depends_win.ps1 -ForDownload || (pause & exit /b 1)
That's curious. Usually the native Powershell is 5.1 although the folder has the 1.0 nomenclature. What is your system? For your case you can invert the code. Code: where.exe /F PwSh.exe >nul 2>&1 && ( set "PSexe=PwSh.exe" ) if "%PSexe%" equ "" where.exe /F PowerShell.exe >nul 2>&1 && ( set "PSexe=PowerShell.exe" ) %PSexe% -NoProfile -ExecutionPolicy Unrestricted .\files\depends_win.ps1 || (pause & exit /b 1) or Code: where.exe /F PwSh.exe >nul 2>&1 && ( set "PSexe=PwSh.exe" ) if "%PSexe%" equ "" where.exe /F PowerShell.exe >nul 2>&1 && ( set "PSexe=PowerShell.exe" ) %PSexe% -NoProfile -ExecutionPolicy Unrestricted .\files\depends_win.ps1 -ForDownload || (pause & exit /b 1) So it will always use Powershell 7.x when present. If not, native Powershell will be used.