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

Microsoft .NET SDK 6.0.412 (x64) is detected as Microsoft.DotNet.SDK.7 < 7.0.100 #3480

Closed
BrianL-STCU opened this issue Jul 27, 2023 · 4 comments
Labels
Area-Matching Issue related to correlation between installed package and manifest Resolution-Duplicate Issue is a duplicate
Milestone

Comments

@BrianL-STCU
Copy link

Brief description of your issue

Microsoft .NET SDK 6.0.412 (x64) is incorrectly identified as Microsoft.DotNet.SDK.7 version < 7.0.100, triggering an install of Microsoft.DotNet.SDK.7 version 7.0.306 every time I run winget upgrade --all, which is already installed.

Steps to reproduce

winget upgrade --all

Expected behavior

The .NET 6 SDK should be detected as Microsoft.DotNet.SDK.6 with an accurate version, or ignored.

Before installing a package version, a system check for that package should be made to avoid slowly downloading and installing a large package version that is already installed, in case multiple installations end up mapping to the same package, which has been a recurring issue for winget.

Actual behavior

The presence of the .NET 6 SDK triggers the reinstall of the .NET 7 SDK each time winget upgrade --all is executed.

Environment

Windows Package Manager (Preview) v1.5.441-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.3208
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.20.441.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

User Settings: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json

Links               
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Jul 27, 2023
@BrianL-STCU
Copy link
Author

I'm running in a corporate environment under an unprivileged account, entering privileged account credentials when prompted by the installer. I'm not able to run winget itself under the privileged account, because that results in this error:

Failed when searching source: winget
An unexpected error occurred while executing the command:
0x8a15000f : Data required by the source is missing

Even getting that far under that account was a huge battle because winget doesn't have a simple installer. After trying a bunch of suggestions in #1861, I've gotten it only this far.

Under that account, winget source list returns:

Name    Argument
-----------------------------------------------------
msstore https://storeedgefd.dsx.mp.microsoft.com/v9.0
winget  https://cdn.winget.microsoft.com/cache

Under that account, winget --info returns:

Windows Package Manager (Preview) v1.5.441-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.3208
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.20.441.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

User Settings: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json

Links               
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Enabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

@Trenly
Copy link
Contributor

Trenly commented Jul 27, 2023

[Policy] Area-Matching

@microsoft-github-policy-service
Copy link
Contributor

Hello @BrianL-STCU,

We've identified this as a duplicate of another issue or PR that already exists. This specific instance is being closed in favor of the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your contribution!

Template: msftbot/duplicate/closed

@microsoft-github-policy-service microsoft-github-policy-service bot added the Area-Matching Issue related to correlation between installed package and manifest label Jul 27, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate Issue is a duplicate and removed Needs-Triage Issue need to be triaged labels Jul 27, 2023
@microsoft-github-policy-service
Copy link
Contributor

Hello @BrianL-STCU,

We've identified this as a duplicate of another issue or PR that already exists. This specific instance is being closed in favor of the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your contribution!

Template: msftbot/duplicate/closed

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 Resolution-Duplicate Issue is a duplicate
Projects
None yet
Development

No branches or pull requests

3 participants