Incorrect Microsoft .NET SDK version

[jahvari]

Brief description of your issue

Winget think that there is a newer version of Microsoft .NET SDK version 6 available when there is not.

Steps to reproduce

Here is a screenshot of the latest version from Microsoft's download page.

Expected behavior

It should not attempt to upgrade or show a new version.

Actual behavior

It attempts to update the current version.

Environment

C:\WINDOWS\system32>winget --info
Windows Package Manager (Preview) v1.5.441-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.2486
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

[ItzLevvie]

It's a bug on the website because the release notes points to https://github.com/dotnet/core/blob/main/release-notes/6.0/6.0.14/6.0.14.md and only one of the architecture (arm64) shown in your screenshot has the proper Download URL which points to 6.0.406 instead of 6.0.309.

1. https://dotnet.microsoft.com/en-us/download --> https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-6.0.406-windows-x64-installer
2. https://dotnet.microsoft.com/en-us/download/dotnet/6.0 --> https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-6.0.406-windows-x64-installer

Both of them point to 6.0.406 (6.0.14)

[ItzLevvie]

cc @mthalman: Do you know anyone in your team who can update the URLs in https://dotnet.microsoft.com/en-us/download/visual-studio-sdks under Visual Studio 2022 SDK?

Download URL for x64 points to 6.0.309 Download URL for x86 points to 6.0.309 Download URL for arm64 points to 6.0.406

x64 & x86 needs to point to 6.0.406

[mthalman]

@rbhanda - Can you help out here? Where is dotnet.microsoft.com getting this information from? Is the release.json not defined correctly?

[rbhanda]

I checked our json and they are pointing to the latest sdk. May be @mairaw can help here

[aetonsi]

I think i have the same issue with Microsoft.DotNet.SDK.3_1. Version 3.1.426 is already installed, but it keeps reinstalling it.

Name                                  Id                       Version   Available Source
-----------------------------------------------------------------------------------------
Microsoft .NET Core SDK 3.1.302 (x64) Microsoft.DotNet.SDK.3_1 < 3.1.419 3.1.426   winget

Also the name says "3.1.302", but it's incorrect.

--- nb: completely uninstalling and reinstalling the package didn't do anything.

[mairaw]

Let me check why .NET 6 is showing different SDK versions on the site. But it all comes from the releases.json file. We might just have a bad logic somewhere.

[mairaw]

@rbhanda I logged an issue for our site but I think the root cause is missing information on the releases.json files for 6.0

The VS info is missing for certain releases since 6.0.404. Compare 6.0.403 entry https://github.com/dotnet/core/blob/main/release-notes/6.0/releases.json#L3593

with 6.0.404 for example https://github.com/dotnet/core/blob/main/release-notes/6.0/releases.json#L2903

From what I can see in the upload logic, if the VS version supported for x64 and x86 is null, then it assumes the SDK is not tied to a specific VS version (it has a note that this was true for pre-2.1 versions). We could certainly review the upload logic there to see what's still true or not, but I think if you add the missing VS information to releases.json, the issue on the site should be fixed.

[mairaw]

I made a change on the website that will now show the same version for all three arch values. Since the 4.0.8 version is not attached to a VS version on the releases.json, showing the 311 version is the right thing to do in this case, for now. If the releases.json is changed, then we'll display the latest version attached to a VS version.

[aetonsi]

@mairaw sorry i am not understanding, you said that about the 311 version so i guess you're talking about my problem. Can i do something to "fix" the update problem?

[aetonsi]

Waaaait a minute! I now have both the 3.1.302 (x64) and 3.1.426 (x64) installed side by side, in the control panel! I have no idea why... i actually don't even know what software/windows update installed them (i'm guessing Visual Studio Community 2022?). Anyway i just uninstalled 3.1.302 (x64) and now winget upgrade doesn't show the update available anymore. So nevermind @mairaw about what i said in the previous message. I'll let you know if it comes back (meaning if 3.1.302 (x64) gets reinstalled by something).

If anyone knows, can i somehow trace what installed the SDKs? i don't know, maybe with the Event Viewer?

[denelon]

WinGet 1.8 has improved support for "side-by-side" packages. Is this still an issue with the latest version of the client?

[microsoft-github-policy-service[bot]]

Hello @jahvari,

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

Template: msftbot/noRecentActivity