-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Trying to update all apps where old and new version coexists with each update run #539
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This issue is stale because it has been open for 30 days with no activity. |
ping |
FYI that the true root cause of this is slowly being addressed by the underlying winget tool. microsoft/winget-cli#2129 |
Hm.. in such a scenario, the burden of replacing older versions falls on the manufacturer of the installation package. As long as users continue to mix InstallerTypes and installation scopes (user/machine), by installing multiple versions of apps in user scopes and then in machine scopes, we will continue to see this mess. As long as manufacturers omit the installation scope in their application manifests, winget will remain lost in the wanderings of detection. As long as manufacturers rely on a single context to automatically detect MSI files, we will see problems like those mentioned in #557 about Google Chrome messing around with someone's system.
Honestly, I don't think the burden of fixing this situation should fall on WAU. |
Interestingly the core underlying winget is addressing all of this just as separate items. Prod/dev/etc is being addressed at microsoft/winget-cli#3940 and the additional info needed to disambiguate side by side installs is in the current proposed spec for it microsoft/winget-cli#3940 (comment) |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
ping |
The problem
Imagine a situation where you have two versions of some app (7zip in my case) installed. For example 16.04 and 21.00 and the 21.00 is the latest available version.
If you run update task, it detects the 16.04 and tries to update it to 21.00. Because it is already installed, nothing happens, just a successful installation notification will pop up.
The problem is that this process will be repeated with every update task run.
Btw in my test environment, this relates to SSMS, 7zip, PowerShell Core, Putty, and Python.
The situation where you have more than one version of the app installed can occur by failed update task, where it just installs a new version side by side with the older one:
What version of WAU has the issue?
1.19.1
What version of Windows are you using (ex. Windows 11 22H2)?
Windows 10 22H2
What version of winget are you using?
v1.6.3482
Log information
Additional information
The proposed fix would be to ignore the application if the same application with the latest version is already installed.
The text was updated successfully, but these errors were encountered: