[BUG] UnigetUI keep asking me to repair Winget, then Winget is properly installed and working (just not with UnigetUI #3087
Comments
|
please run the command |
|
Hello Martin and thankx for your reply! I want to add it's long time I'm a user of the program and I deeply appreciate it. If I do run from command line: winget list, I get the list of my installed packages, example; Power Automate MSIX\Microsoft.PowerAutomateDesktop_1.0.1324.0_… 1.0.1324.0 And so on... I had to accept the lWinget license agreement before getting the list. After accepting the agreement I also did a try to UnigetUI again, then it still say winget is broken and ask me to reinstall it again and again. I have to say I also reinstalled UnigetUI with no luck. |
|
UniGetUI Version: Windows version, edition, and architecture: Describe your issue: ALL with standard user (non-admin) Windows account. Repeated re-installations and Winget repairs from within the program did not help. UniGetUI Log:
winget list command prompt output shows at least as many installed programs as with Piggoz. |
|
This is weird, I will investigate the issue. Please try to enable "Use bundled WinGet instead of System WinGet" from UniGetUI Settings -> WinGet |
|
Hi Marti, even if the option system say in green color: Winget is ready (Bundled Winget CLI version: Using Bundled winget helper (CLI parsing), after I enabled it from your previous advise, nothing happen. Then it STILL say at startup: Perhaps Winget doesn't work. do you want to repair it? There is something new: yesterday I test winget list as a administrator! If I run it as a simple user I get this: winget list Now, if I try to run UnigetUI as an administrator, it still don't work! |
|
I can confirm the bug in another system, still windows 11 pro 24H2. After updating UnigetUI, he had FOUND the updates related with Winget, not just does related to pip. Then it installed the pip updates, but the winget updates. They all failed. After they failed, I closed UnigetUI and reopened it and from that moment IT CAN'T FIND the winget packages. The only difference with the other system is: here it don't ask to repair Winget. Winget list works in administrator mode, fail in user mode, like the other system. Here the new system log: [20/12/2024 03:41:46] __ __ _ ______ __ __ ______ Here the package manager log of the new system Manager WinGet with version: —————————————————————————————————————————— Logged native task on manager Winget. Task type is ListSources -- Task information The task reported success —————————————————————————————————————————— Logged native task on manager Winget. Task type is ListInstalledPackages The task has not finished yet —————————————————————————————————————————— Logged native task on manager Winget. Task type is OtherTask -- Task information -- Task errors The task reported a failure (1) —————————————————————————————————————————— Logged subprocess-based task on manager Winget. Task type is RefreshIndexes -- Process STDOUT Return code: SUCCESS (0) —————————————————————————————————————————— Logged native task on manager Winget. Task type is ListUpdates The task has not finished yet —————————————————————————————————————————— Logged native task on manager Winget. Task type is ListInstalledPackages The task has not finished yet —————————————————————————————————————————— Logged native task on manager Winget. Task type is OtherTask -- Task information -- Task errors The task reported a failure (1) —————————————————————————————————————————— Logged subprocess-based task on manager Winget. Task type is RefreshIndexes -- Process STDOUT Return code: SUCCESS (0) —————————————————————————————————————————— Logged native task on manager Winget. Task type is ListUpdates The task has not finished yet —————————————————————————————————————————— Logged native task on manager Winget. Task type is OtherTask -- Task information -- Task errors The task reported a failure (1) —————————————————————————————————————————— Logged native task on manager Winget. Task type is ListInstalledPackages The task has not finished yet —————————————————————————————————————————— Logged native task on manager Winget. Task type is ListInstalledPackages The task has not finished yet —————————————————————————————————————————— Logged native task on manager Winget. Task type is OtherTask -- Task information -- Task errors The task reported a failure (1) —————————————————————————————————————————— NOW IT WANT REINSTALL WINGET TOO LIKE IN THE OTHER SYSTEM!!! and if I do reinstall, it keep asking again and again and again, exactly like in the other system. |
|
Please try to go to %TEMP% and delete the WinGet folder. |
|
Hi marti, cleaned up %temp% and that helped with the winget problem asking to reinstall everytime and now it find packages. Then it is unable to install them with this error: Errore durante l'apertura della/e origine/i; provare il comando 'source reset' se il problema persiste. This happen on FOUR SYSTEMS, 3 windows 11 pro 24H2 and one Windows 10. I can confirm NO problems with old UnigetUI version 3.1.12: refusing to update it on a 5th 24h2 windows system, and UnigetUI worked pretty fine updating 79 packages! So, IMHO, still badly broken 3.1.4. |
|
Hi Marti, 3.1.5 doesn't change anything for me, the bug is still there. Then, in an effort to try to help, I learned the magic of Winget!
|
|
Yes, I have the same error on my Win11 |
|
Keeps happening for me also, UnigetUI runs fine for the first launch on an reinstall, then after system reboot UnigetUI wants to update, after an update then the Winget repair message keeps showing on each successive launch and no app updates show in UnigetUI. |
|
I didn’t say nothing anymore becouse I was wondering it was just me with this bug. Then it was impossible: In this days I had access to three new real machines, two with win11 and one with win10 and they all act weird like in the subject of this bug report. So now I keep this on a total of ten real machines (didn’t try virtual) and what was a fantastic helper to update programs is now useless for Winget and I do have problems on Choco too. Remaining on winget bug, on the ‘new’ three machines the sequence to get the bug is exactly the one described by another user. Considering I’m a long time user of UnigetUI (started when it still was wingetUI) those three machines new for the bug all had 3.1.3 installed. When I launched UnigetUI for the first time, I was offered to upgrade from 3.1.3 to 3.16. I firmly said no, 3.1.3 found all the updates and installed them with no glitch (but a pair, exactly XYPlorer and found an update not update for Geekbanch). just for testing purposes I closed UnigetUI, launched again, offered the upgrade to 3.16, did it and it started to act weird again asking to upgrade what he call screeed winget and from that moment not founding anything and obviously not installing uodates anymore. THIS HAPPEN ON NINE MACHINES! The ten one, the one with I originally reported the bug, fixed hisself , I don’t lnow how, then one day 3.16 started doing his job. It was lying in the traybar and found some updates. Did nothing and fron that moment still works and not report not exiatant winget problem. Lucky, this problem had me to learn winget, so now I update my Winget apps manually and this even have some advantage if, like me, run the program on an elevated powershell or cmd (no ask for confirmation). on one machine I also learned choco becouse I had two apps to update and for me UnigetUI have problem with it too (doesn’t find the choco path in progeamdata then this is another story). I didn’t report anything becouse the winget logs are very similar to the one reported when I first reported the bug. |
|
The same thing is now happening to me on my Windows 10 PC (in addition to my Windows 11 PC listed above: #3087 (comment)). Updates are now no longer found here either. Error messages in logs: The repair prompt is now constantly appearing. However, the repair does not help - PowerShell always outputs the following:
|
|
@Piggoz, there is clearly a hidden pattern here. I have done lots of tests, but I haven't been able to reproduce the issue. However, on your environment, it seems to be quite reproducible. I need you to provide as much details as possible about the environments on which you are running UniGetUI (how many users? are they admin? any special network settings? Windows edition? is it entreprise-managed? How is being UniGetUI used? Are you using any special settings on UniGetUI? etc.), so I can figure out what is going wrong and finally fix it once and for all. If you wish, for privacy, you may send said details privately by email to me. You can find my email on my GitHub profile. |
Please confirm these before moving forward
UniGetUI Version
3.1.4
Windows version, edition, and architecture
Windows 11 24H2 build SO 26100.2605 X64
Describe your issue
Like in the subject. This problem wasn't there before UnigetUI asked me to update the version. I said yes, and after the update went installed with apparently no issues, UnigetUI started to behave erratic keep asking me to repair Winget. If I allow it, it say operation was successfully then no Winget update are found and it keep me asking to repair Winget.
As said, my Winget is perfectly fine, it is version 1.9.25200, can manually install everything.
Python is 3.13.1 working fine in the system.
Steps to reproduce the issue
So what I said in Describe the issue
UniGetUI Log
Package Managers Logs
Relevant information
Nothing other to report.
Screenshots and videos
The text was updated successfully, but these errors were encountered: