Open marticliment opened 3 months ago
Confirming for a similar reason. Recently started using your UniGetUI, started experiencing the same issue you show above but when launching PowerShell (I have the CommandNotFound PowerToys module which uses WinGet on launch) which lead to it crashing almost immediately. Managed to find a temporary fix: ONLY FIXES USERMODE
Change permissions on %TEMP%\WinGet
directory to give your user profile Full Access
.
Sadly this seems to only work as long as WinGet doesn't get called inside the gsudo elevated environment, which almost completely defeats the point of the fix but it fixes WinGet for anything non-admin
Issue Description
Sometimes, when calling using gsudo, some users complain about crashes for "illegal characters in path". The passied command-line arguments, the error seems erratic and not concisely reproducible.
Original Error trace:
Translated error trace:
Process exit code:
999
Steps to Reproduce
Run gsudo.exe with the following arguments:
"C:\Users\Giesen\AppData\Local\Microsoft\WindowsApps\winget.exe" update --id Tyrrrz.LightBulb --exact --source winget --accept-source-agreements --version "2.5.3" --silent --disable-interactivity --accept-package-agreements --force --include-unknown
It should be noted that gsudo was called from the gsudo.exe directly, started as a process using
System.Diagnostics.Process
.NET class. The filename isC:\complete\path\to\gsudo.exe
, and the arguments are the ones stated above. The error traceback was captured from STDERRScreenshots
This is a screenshot of the error shown to the user in my app, which uses gsudo.exe to automate certain tasks.
Context: