After update to 3.1.0 all winget updates fail #2426
Comments
VOOM108
changed the title
|
Please downgrade to 3.0.2 and disable automatic updates. I will investigate the issue |
How? 3.0.2 tries hard to update itself to 3.1.0 even when every option I can find about updating itself it set to off. |
|
You need to disable autoupdates again on 3.0.2 |
|
I did not even get that far, after downgrading it crashes when starting it. I will probably stick with 3.1.x and wait, until it is fixed. Would completely uninstalling it and reinstalling 3.0.2 keep my settings, and could that help to successfully downgrade? |
|
Downgrading from 3.1.0 to 3.0.2 will not keep your settings. |
|
One question, do you have "Elevate all installations by default" option enabled? |
|
Also, please share your operation history |
Yes, it was enabled. I turned it off now, and most updates now go through. The remaining one may be an issue with the package.
I don't know, what that is. |
|
|
|
|
This issue seems to be related to GSudo, I have opened an issue on their repo regarding this |
|
I'm also getting repeated errors when Wenget tries to update itself: Starting package update operation for package id=SomePythonThings.WingetUIStore.Pre-release with Manager name=Winget This looks different from the above error, so I am unsure if it's related though I thought it may be of use. |
|
I think this is a very serious issue, making the latest version downloaded from the release almost unusable. Why hasn't a fix been released after such a long time? |
|
Because, as said, this issue is caused by GSudo, not by UniGetUI. As said, you can check the associated issue here: gerardog/gsudo#365 |
|
Any solution ? Because even after having WingetUI uninstalled, I can't install latest uniget :/ |
|
There is a simple solution for that problem with gsudo, you can overwrite gsudo.exe (in Winget\Assets\Utilities) with the version from 3.0.2 and it will work. Just a small hint: the gsudo from 3.0.2 is much bigger than the actual one in 3.1.1 (5.878 kB and 197 kB). I'll hope that helps all with that. |
|
So why let the problem fester for so long? On some computers, downloading the latest installation package makes it completely unusable. The issue has become so severe that it's unusable. Why didn't we just revert to the old version of gsudo from the beginning? I don’t understand. |
|
It does seem odd. |
|
As I assume that behavior about the filesize of gsudo.exe, it works with the standalone Version (see releases from gsudo: |
|
Hello, I was not aware that the old version did work. As said, I haven't been able to recreate the bug, so I can't create any workaround for it. I am now aware that gsudo from 3.0.2 works, which I was not aware before reading your comments. Nevertheless, rest assured I will downgrade GSudo and ship the next version with the older GSudo release. |
You can enable system GSudo from UniGetUI settings -> Experimental features |
Good job, I have waited this for one month. |
Well... No : As I can't install Uniget, I obviously can't get into its menus :/ |
Since I have a few times upgraded und downgraded UnigetUI and WingetUI (it allways install the new version, even Updating is disabled), I have noticed, that not all will be deleted in the Uninstall-Process. This fixed the problem for me with non installing. If you try to install it with winget (the original from MS) you can try also this: But you can also use the installer who can be found under releases. |
|
No Winget nor Uniget folders in program_files or program_files (x86)... And I cleared all reference to wingetui in register :/ I tried the installer :
To no avail. |
I'm not shure why the install fails on your maschine, but you may try to run winget (from Microsoft) in a shell (as admin), to install it with winget. First you should open an admin-shell an type in I hope that it will help you in this situation. |
This will also only work if gsudo is installed on the system (not standalone), so it makes no difference for me 😉 |
I've done some more tests with the gsudo v2.51 portable version and it did not work with this. Some about my system: Windows 11 Enterprise 23H2 build: 22631.3958 I also noticed, that there is a problem with Format.Exception at parsing input string ('850.' - the dot I think) at CoreData.cs:line 26 on the start - that is on all tests the same issue. Also if you press abort in unigetui the installation itself will not be killed (the winget-process) and continues with its installation (this may one reason, while it become an endless loop with using gsudo v2.51). Here is the Log with using gsudo v2.51 portable and the unhandled exception:
|
|
Huh, this is weird. I will investigate |
As I've seen in your code, you didn't use a Cancellation-Token when using async-tasks. Another point is, that the timeout is to short, as you can see in my provided log, what is importent to slower machines, or if you use it eg. in a virtual environment. |
|
Thanks for the links, they seem to point me in the right direction for the fix! |
Thanks for the help !
Log output : Puzzling. |
|
(update) I tried to install older versions : everything installs with no error from 2.2.0 up to 3.0.2.
|
This looks very strange to me, the install-process opens the kernel, import a dll function and it raised an exception, now it is good to see why this happened. After Runtime error the output is translated "This action is only valid for currently installed products" (suppressed message). There comes 3 possibilites in my mind, one is that a virus-scanner blocked that process (to test it, disable it temporary and try again), the other thing is, that you memory is corrupted, also a virus infection can be possible. If the installation work after disable your virusscanner, all is ok. If not, you should check your whole system, but please use an Live-CD from an Antivirus-Developer to prevent for hidden viruses (with e.g. rootkit-technology), or viruses who disable Antivirus-Scanner (they are in the wild). |
Ok, to install a alpha-version makes no sense, alpha and beta releases are only for testing purposes and can have many bugs, even in the installation process. |
|
Thanks for this. Only antivirus I have is the regular Windows "Defender"... I may try to disable it, but as I'm pretty sure almost everybody has it enabled, it is quite unlikely it is involved :/ To be sure, I tried to install after having it disabled. To be sure, I ran an "offline check" with Windows Defender. I'm pretty sure my RAM is OK, as I have absolutely no other problem/crash on this PC, even during heavy, RAM-hungry game sessions and video editing. To be sure, I ran the Windows RAM diagnostic tool (damn... this was long). I searched for the Common fix is to reinstall the same versions of products over the corrupted installation (doesn't work here) or use the MS "Install and Uninstall Troubleshooter" (https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d). |
I don't intend to use them. Just verifying the installer works. |
To verify this, you should try the official release of 3.1.x, not the alpha (remember the installation-script have been changed in 3.1.x) 😉 What you can do is, you shouls search the registry for that string: Here is a sample of a found registry entry on my system: As you can see, there is no direct reference to wingetui, or unigetui, windows uses app-IDs 😉 After that I hope you are able to install 3.1.1 without problems and you do not hack your registry anymore, without a backup.. Another notice: the troubleshooting tool runs on win11 also, but it is not further developed (since some time), so it is useless in your situation I think. |
Since the version 3.1.x the installer have been modified (you can read it it in the history) while some changes must be made to upgrade from 3.0.2 to 3.1.x. In normal situations that will not occur, so I don't think it is importent to handle this, don't know what marti think about. |
I can install and run 3.0.2 nicely. So... Why isn't it able to find the 3.0.2 registry entries when attempting to upgrade (?) |
|
If you install verson 3.1.1 (latest) don't forgett to made the changes with gsudo as I wrote some points earlier. Here is the solution:
|
|
Thanks for helping. This said : I (re)deleted all the entries (yep, I know about GUID refs) to no avail... I could replace my actual As you said : manually fiddling with files and settings could lead to quite unwanted consequences. Thanks again :) |
Your actual gsudo must not be changed for that, only the provided one in unigetui (it should be a standalone one) 😉
If you don't become errors on installations, there is no need to change the provided gsudo, but in other cases there is no way (at the moment) to solve that issue, who makes unigetui completely unuseable (remember the topic of this threat). But hopefully these bugs (there are some more) will be fixed soon. best regards :) |
|
fixed on 2dc1fb8 |
|
I still have this issue in the 3.1.6 & 3.1.7 beta: |
Please confirm these before moving forward
UniGetUI Version
3.1.0
Windows version, edition, and architecture
Win 11 Pro Build 22631.3810
Describe your issue
I get this kind of error message for any winget package that wants to update since the update to unigetui 3.1.0:
Steps to reproduce the issue
No response
UniGetUI Log
Package Managers Logs
Relevant information
No response
Screenshots and videos
The text was updated successfully, but these errors were encountered: