[BUG] "WinGet-Error detected. Do you want to repair WinGet?" #3153
Comments
|
What happens if you run |
|
I have the same error as above and I think I found out why. It translates to: When I delete the "WinGet" folder in my %temp% directory everything works again until UniGetUI trys to update something with it's build in elevator. Hope this helps to solve this issue here. If not, feel free to move this to a new issue. I can also provide logs if needed. |
|
I also have the same issue on multiple computers where I'm executing UniGetUI with a windows user with standard account type and I need to select a different account with admin priviledges to update the applications. After every restart of UniGetUI I need to delete my I use WinGetUI also on a machine where the executing user is an admin user account and there it just works fine. Maybe this helps a bit to get the annoying issue which I already have for a long time. |
|
Same here. Still the same error on multiple devices (on the Win 11 PC for months, on the Win 10 PC for weeks). |
|
Yes, same here. As soon as a program installation requires that GSudo-like elevation (no matter if actual GSudo or the new Uniget Elevator) I need to cancel that installation to not render UnigetUI unusable. UnigetUI at the moment is only useful for updates that the normal user can do but without knowing beforehand which those updates are and to show what updates are available for all kinds of software in a GUI. I also hope that the Winget-CLI devs fix that issue. |
|
Same here, only observed while using Elevator. It messess up the ownership of the tmp/WinGet folder and the repair does not fix it. Reported it here to the CLI team. |
|
As a temporary workaround I went back to UniGet 3.1.3 |
|
I get this error every time I install it on my work laptop, Win 11 and I am not an admin user as it is a work machine. On initial install UnigetUI works fine until a restart or a few days. After then, I keep getting warnings about Winget needing to be repaired in UnigetUI, repair script doesn't repair it so I am stuck in a loop. I can escape the loop by going to C\Users\Username\AppData\Local\Temp and deleting the Winget folder there and restarting UnigetUI. On that restart of UnigetUI it loads in all the updates I had missed for packages and tries to update them, all of them are reported as failed updates with console errors but when I refresh the updates list, the updates actually seem to have installed or Winget/UnigetUI is failing to get the list of updates on refresh after the failed updates. I also tried this command and got this error I then delete C\Users\Username\AppData\Local\Temp\WinGet folder again and then run the winget list command which then works fine. I think this could be due to this issue mentioned here - microsoft/winget-cli#4704 (comment) "Cause: the WinGet folder in the windows temp folder of my non-privileged user had - for whatever reason - admin access rights only. Fix: deleted this WinGet folder, ran winget source update from an non-elevated shell again. Et voilà, a new WinGet folder with proper permissions has been created and everything is fine again. " So the cause is likely to be a non admin user uses UnigetUI which is doing the WinGet source update command as an elevated command prompt which could then be causing the AppData/temp/Winget folder to be created with admin rights only which then causes access errors for modifying it as a non admin user which UniGetUI is trying to do I assume. This issue is probably the underlying cause |
|
I confirm the problem can be that then, maybe becouse of the evolution (and probably bugs in Winget hisself, the problem represent hisself from now and then. You need to manually delete any temp folder referencing to winget and this sux. For the moment I find more easy to simply run winget and sometime try UnigetUI as an helper. It is too bad, becouse in the old time of WingetUI and first versions of UnigetUI everything was fine, then as I said probably the "evolution" of Winget broke UnigetUI too. Martin asked me about my environments in another thread, then it is pretty common and it works with everything, always run everything as a user and always I elevate a program when needed. Pretty secure and pretty common and the same on maybe 10 or 12 machines I do administer. |
|
Please leave a thumbs up at the relevant winget-cli issue to get it fixed earlier. |
|
for me it helped to execute However i remember also that i already did this in the past, so it might come back from time to time. |
Please confirm these before moving forward
UniGetUI Version
3.1.5
Windows version, edition, and architecture
Windows 11 Pro 23H2
Describe your issue
[BUG] "WinGet-Error detected. Do you want to repair WinGet?" and if I chose yes, even if I had uninstalled the existing version and re-installed the latest version, or even starting UniGetUI as an admin did not resolve the error, the error message came back again and again.
Steps to reproduce the issue
just run UniGetUI
UniGetUI Log
Package Managers Logs
Relevant information
No response
Screenshots and videos
No response
The text was updated successfully, but these errors were encountered: