Different package upgrade issues #1670
Comments
ghost
added
the
|
@MikronT, Thank you for the detailed report. I believe most of these are duplicates. It's best to report a single problem with a single issue. That way we can focus on a single specific problem and resolve it. We tend to prioritize by sorting issues by the number of 👍. Duplicate issues artificially lower the priority by splitting the votes.
I will keep this bug open to see if the community can help with Visual Studio Community 2019, and I'll mark this issue as area external since the majority of the issues are related to installers. |
denelon
added
Area-External
|
Maybe as a solution to packages not reporting their versions a entry to the manifest could be added to contain the version number? That way when the manifest is created the version could be pulled from the manifest if it's missing. Just throwing ideas out |
|
We depend on Apps & Features to tell us what is installed on the machine. We don't have another trustworthy mechanism. A user might have done anything between the last event we recorded and when they try to perform an upgrade. We also can't assume the user had the previous latest version installed. |
|
Turns out Visual Studio requires a special command line argument to upgrade. PRs are open to resolve this for Community (microsoft/winget-pkgs#34094) and Enterprise, I'll try to push them for Professional too today. This should resolve that part of your issue :) |
|
Looks like all of the PRs have merged. You should be able to upgrade Visual Studio. |
|
Thank you all for your replies! It looks like the bug with upgrading Visual Studio is fixed now. As you stated above, the other problems are outside your area of influence, so this issue has no more purpose to be opened. |
|
I have the same problem with "AngusJohnson.ResourceHacker"'s wrong version numbers in winget. Is there a workaround for now so I won't see its related errors? Asking since the latest version of this app was back in 2019 and I don't think the developer is even interested in fixing anything related to the app meaning if someone else doesn't fix the issue, most likely it will remain an issue until forever. |
Brief description of your issue
3 major issues I faced:
Steps to reproduce
Install any of the packages listed below:
Let these packages upgrade themselves:
Try to upgrade them all to the latest version using
With all the packages listed above, the
upgradecommand syntax doesn't matterwinget upgrade {packageName} winget upgrade {packageId} winget upgrade --id {packageId}Expected behavior
Actual behavior
WinGet detects packages to upgrade:
And then produces different types of errors trying to perform upgrades:
Visual Studio Community 2019
Can find the upgrade but can't finish the installation.
A small dialog appears for some seconds, then disappears, and produces error level 1.
Log:
Resource Hacker & AOMEI Partition Assistant
WinGet upgrades them successfully but the version remains
Unknownso these packages can be upgraded again and again - a serious issue for automation.Viber & Oracle VM VirtualBox & PowerToys (Preview)
Packages are already upgraded to the latest versions. However, WinGet finds their updates but can't actually upgrade them. Some of these packages show up as multiple versions installed but specifying their ids resolves the issue with determining the right one.
VirtualBox
Log:
VirtualBox
PowerToys
Oracle.JavaRuntimeEnvironment
JRE can be upgraded, JRE's update checker detects a new version available but WinGet can't start an upgrade process.
Environment
Windows Package Manager v1.1.12701 Copyright (c) Microsoft Corporation. All rights reserved. Windows: Windows.Desktop v10.0.19043.1320 Package: Microsoft.DesktopAppInstaller v1.16.12701.0 Windows Terminal Preview -> Command Prompt (cmd) Running as Admin has no impactThe text was updated successfully, but these errors were encountered: