Yes, that's how I ran the script at first. But I now think that maybe it's a Windows issue, as even the script from the old local uup dump app won't detect admin rights.
I saw a opened command window with the call for the script. Probably tinkered with the rights, is many times the cause for these rights problems. I can't answer to this because i dunno what you mean exactly. But that all aside: Try it this way in a cmd prompt: Code: uup_download_windows.cmd 49127c4b-02dc-482e-ac4f-ec4d659b7547
I ran the script as normal with double click, and right click>run as admin, and accepted the UAC prompt, but the output was the same as in the mage. So then I ran it manually through elevated cmd.exe to show that it was indeed running as admin. I meant this app https://forums.mydigitallife.net/th...11-uups-with-ease.75052/page-243#post-1781105 The command you provided helped me realize where the issue was. I thinkered with powershell some time back and removed it from PATH in favor of pwsh. I only replaced powershell with pwsh in the script and it's currently running. Thanks @Enthousiast
Let's see how far the script runs, the dev replied to me that the script should run ps in more places.
There was at least one error before the converter phase, about 'findstr'. But the script did generate the iso in the end 27928.1.250815-1403.BR_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO Currently installing in vmware Also, with pwsh it has to be ran manually as .\ uup_download_windows.cmd 49127c4b-02dc-482e-ac4f-ec4d659b7547 otherwise it won't work I've added the normal powershell back to PATH to avoid this issue in the future.