Repository navigation
Upgrade doesn't work for several packages #752
Description
Edited:
The most common reasons upgrades don't work has to do with how we match an installed application against a manifest in a configured source. We are depending on data available in Windows Apps & Features to match a manifest based on the "displayName" and "version". In many cases there are multiple packages with data similar enough to make it unclear which manifest matches to an installed package.
We are working to improve the matching heuristic so we can distinguish between packages with a true update vs. packages that have a similar name and newer versions are installed "side by side".
Original issue:
Upgrade didn't work for PowerToys.
I have all of the experimental features enabled.
PS C:\Users\denelon> winget upgrade
Name Id Version Available Source
----------------------------------------------------------------------------
Microsoft Whiteboard Microsoft.Whiteboard 21.10111.5555.0 Latest msstore
HyperLabel SixgillLLC.hyperlabel 1.1.10.0 Latest msstore
PowerToys Microsoft.PowerToys 0.31.1 0.31.2 winget
PS C:\Users\denelon> winget uprade Microsoft.PowerToys
Windows Package Manager v0.2.10191 Preview
Copyright (c) Microsoft Corporation. All rights reserved.
PS C:\Users\denelon> winget list Power
Name Id Version Available Source
--------------------------------------------------------------------------------------------
PowerToys Microsoft.PowerToys 0.31.1 0.31.2 winget
PowerShell 7-x64 {41D89B69-B90A-4CFB-9783-4B86D2B34EC3} 7.1.1.0
PowerShell 7-preview-x64 {7DDB4F02-04AE-48FA-BC1D-962D3A567FF6} 7.1.0.5
Windows Terminal Preview Microsoft.WindowsTerminalPreview 1.6.10272.0
Windows Terminal Microsoft.WindowsTerminal 1.5.10271.0
PS C:\Users\denelon> winget upgrade Microsoft.PowerToys
--------------------------------------------------------------------------------------------
Found PowerToys [Microsoft.PowerToys]
No applicable update found.
PS C:\Users\denelon> winget --info
--------------------------------------------------------------------------------------------
Windows Package Manager v0.2.10191 Preview
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19042.804
Package: Microsoft.DesktopAppInstaller v1.11.10191.0
Activity
Shatungoo commentedon Feb 15, 2021
Is upgrade work for other apps? I have the same problem with powertoys and other apps.
No one successful upgrade. But upgrade knows about the newer version.
megamorf commentedon Feb 15, 2021
Then please provide examples so that the devs can check if the issues you're describing and the PowerToys issue are identical.
Shatungoo commentedon Feb 15, 2021
Powertoys - the same as author of this issue.
After
winget install powertoysi receive new version.PythonSoftwareFoundation.Python from msstore - No applicable update found.
AdoptOpenJDK.OpenJDK - Successfully installed, but after installation i have the same old version. It was installed through winget.
Full log
LuanVSO commentedon Feb 24, 2021
i can't upgrade gh cli, it says it was successfully upgraded, but if you check the version installed it is still the old one
Shatungoo commentedon Feb 24, 2021
The same situation. The output is the same as in example with java above.
denelon commentedon Feb 24, 2021
Thanks for the additional data points here. Some applications work "Microsoft.WindowsTerminalPreview" and "Microsoft.WindowsTerminal" while others don't.
LuanVSO commentedon Feb 25, 2021
so, only msix?
arielmoisis commentedon Mar 11, 2021
Not sure if this issue is related but when running winget list I do not see a source for all my apps I have installed with winget. The ones I see with a source in winget list I can upgrade.
jedieaston commentedon Mar 12, 2021
On a similar note, PowerShell cannot be upgraded either (shipped as a MSI, product code in manifest).
YsHaNgM commentedon Mar 26, 2021
Any update yet? I saw new release but not mentioning this issue.
[-]Can't Upgrade PowerToys[/-][+]Upgrade doesn't work for several packages[/+]denelon commentedon Mar 26, 2021
This is primarily driven by "list". The way packages in Add/Remove Packages are mapped to package identifiers in the Windows Package Manager is fairly complex. Generally MSIX packages contain enough meta-data that it is trivial to get a match. Unfortunately, other legacy installers often don't have enough meta-data. We're working on improving list gradually, and we're thinking through several different heuristics to increase the number of matches.
132 remaining items
HrMitrev commentedon Aug 24, 2022
Hi!
I have similar problem with Microsoft.Office:
one thing to note - I have chocolatey and originally this app was installed with
choco install office365proplus. Also it was upgraded via chocolatey beforewinget upgrade --all. I am not sure how winget checks the version but it seems that something's off. chocolatey reports v15330.20230OfficialEsco commentedon Aug 24, 2022
WinGet uses the information reported by the Control Panel instead of Chocolatey which reports the latest version it installed.
The good thing is that both WinGet and Chocolatey reports the wrong version because you have
16.0.15427.20210installed.The bad thing is that the damn Microsoft Office installer installs the version based on region and probably some more crap...
Which doesn't make any sense when the
setup.execlaims to install16.0.15427.20220So in theory this is just a Microsoft issue..
xarthurx commentedon Aug 24, 2022
Add to the list:
Rust 1.62 (MSVC 64-bit)OfficialEsco commentedon Aug 24, 2022
Make a issue at https://github.com/microsoft/winget-pkgs/issues.
HrMitrev commentedon Aug 24, 2022
The funny thing is that WinGet is also a Microsoft project.
Are there any workarounds to force WinGet to ignore that package? Now
winget upgrade --allis totally unusable because every time it takes about a minute to run the installerdenelon commentedon Aug 24, 2022
Hristo Mitrev (@HrMitrev) put your 👍 on:
OfficialEsco commentedon Aug 24, 2022
WinGet is a highly community run project, Microsoft Office is a proprietary software.
The WinGet community can do just as much as Chocolatey about these issues. The only difference being how it matches and stores what is installed.
beppler commentedon Oct 11, 2022
pplmx commentedon Nov 21, 2022
Same issue.
saurabhsri108 commentedon Jan 28, 2023
This is a serious issue. We need a way to exclude the packages or fix this. Keeps installing these 2 over and over.
sigmaphi007 commentedon Apr 18, 2023
Surp
This fixed it, removing the wide machine installer fixed it. But surprised it's still happening
JohnLukeBentley commentedon Apr 22, 2023
Still getting this problem with ...