Skip to content
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

winget tries to upgrade .NET 5 Runtime over and over #2345

Open
exchange12rocks opened this issue Jul 17, 2022 · 11 comments
Open

winget tries to upgrade .NET 5 Runtime over and over #2345

exchange12rocks opened this issue Jul 17, 2022 · 11 comments
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@exchange12rocks
Copy link

Brief description of your issue

I have two .NET runtimes installed side by side: 5 and 6
image

winget sees the 5.0.17 version and tries to upgrade it to 6.0.7, even though 6.0.7 is already installed on the machine.

Steps to reproduce

  1. Install .NET Runtime 5.0.17
  2. Install .NET Runtime 6.0.7
  3. Run winget upgrade
  4. You'll see the following:
Name                                               Id                                Version       Available     Source
-----------------------------------------------------------------------------------------------------------------------
Microsoft .NET Runtime 6.0                         Microsoft.DotNet.Runtime.6        5.0.17.31213  6.0.7         winget

Expected behavior

winget treats .NET Runtime 5 and 6 as two different applications and does not offer new .NET 6 versions for .NET 5.

Actual behavior

winget treats .NET Runtime 5 and 6 the same application, offering new .NET 6 versions as upgrades for .NET 5.

Environment

Windows Package Manager v1.2.11601
Windows: Windows.Desktop v10.0.19044.1766
Package: Microsoft.DesktopAppInstaller v1.17.11601.0
@ghost ghost added the Needs-Triage Issue need to be triaged label Jul 17, 2022
@denelon
Copy link
Contributor

denelon commented Jul 19, 2022

The issue with dotnet runtimes is due to there being multiple versions of the runtime installed side-by-side and is related to

We have enhancements in Windows Package Manager 1.3 support for "AppsAndFeatures" data that will help in this scenario.

@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels Jul 19, 2022
@dw72
Copy link

dw72 commented Jul 21, 2022

For me, this situation is a little bit different... I have installed only one version 5.0.13

image

but winget list to install version 3.1.27

image

o course when I try install it

image

@denelon
Copy link
Contributor

denelon commented Jul 21, 2022

@dw72

Can you try with "--verbose-logs" and share the resulting logs? I'd also like to know which version of Windows Package Manager you're running.

@dw72
Copy link

dw72 commented Jul 25, 2022

Hi @denelon, see attachments below.

image

WinGet-2022-07-25-14-18-12.581.log

@denelon
Copy link
Contributor

denelon commented Feb 22, 2023

@exchange12rocks? Is this still happening?

@denelon denelon added the Needs-Author-Feedback Issue needs attention from issue or PR author label Feb 22, 2023
@exchange12rocks
Copy link
Author

@denelon Yes:

Name                                        Id                           Version Available Source
-------------------------------------------------------------------------------------------------
Microsoft .NET Runtime - 5.0.17 (x64)       Microsoft.DotNet.Runtime.6   < 6.0.5 6.0.14    winget
1 upgrade available.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention Issue needs attention from Microsoft and removed Needs-Author-Feedback Issue needs attention from issue or PR author labels Feb 22, 2023
@denelon denelon added Area-Matching Issue related to correlation between installed package and manifest and removed Needs-Attention Issue needs attention from Microsoft labels Feb 22, 2023
@denelon denelon modified the milestones: v1.5-Client, v.Next-Client Jun 6, 2023
@functionkey-12
Copy link

I am also having this issue with different versions of the .NET runtime and winget. I have .NET 6.0.23 installed and winget would like me to upgrade it to 6.0.25. However, I already have that version installed as well.

In any case, winget downloads and attempts to install 6.0.25 and then closes shortly after starting the install. If I try to upgrade with the the -id flag, I get the "No installed packages [...]" message. If I try to install with the id, the package is found, downloaded and tries to install.

I have also found and ran the .NET Fix Repair tool, and it found no issues with my installed packages.

Winget version v1.6.3421

winget_issue2345_20231219

@sharpsalat
Copy link

Having similar issue:
image

image

@aaronliu0130
Copy link

To workaround this, set the architecture and install.

@Chudesnov
Copy link

set the architecture and install.

@aaronliu0130 could you elaborate further?

@aaronliu0130
Copy link

e.g. winget install Microsoft.DotNet.SDK.5 -a x64

@denelon denelon removed this from the v.Next-Client milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

7 participants