.NET December 2021 Update -.NET 6.0.1, .NET 5.0.13 and .NET Core 3.1.22

[kalaskarsanket]

Release Notes
6.0.1
5.0.13
3.1.22

Please report any issues you find either by responding to this issue, creating a new issue or creating a new issue in one of the following repos:

• dotnet/aspnetcore - for ASP.NET Core questions
• dotnet/efcore - for Entity Framework Core questions
• dotnet/sdk - for CLI tools and questions
• dotnet/runtime - for runtime, API, or installer issues and questions
• dotnet/winforms - for WinForms issues
• dotnet/wpf - for WPF issues
• nuget/home - for NuGet questions and issues

---

Status of availability of SDK on Microsoft's Linux feeds:

Distro	6.0.1	5.0.13	3.1.22
Ubuntu 16.04	✅	✅	✅
Ubuntu 18.04	✅	✅	✅
Ubuntu 20.04	✅	✅	✅
Ubuntu 20.10	✅	✅	✅
Ubuntu 21.04	✅	✅	✅
Centos 7	✅	✅	✅
Centos 8	✅	✅	✅
Debian 9	✅	✅	✅
Debian 10	✅	✅	✅
Debian 11	✅	✅	✅
Fedora 33	✅	✅	✅
Fedora 34	✅	✅	✅
OpenSUSE 15	✅	✅	✅
SLES 12	✅	✅	✅
SLES15	✅	✅	✅

Note: This list refers to the Microsoft-provisioned feeds (packages.microsoft.com) and does not in any way represent direct availability in distros (eg RHEL, Fedora).

Known Issues

.NET 6.0.1

• There have been limited reports of a failure to install the update via Microsoft Update on Windows 11. The update fails with error code 0x80070643. A workaround is to install the package that is failing manually by downloading it from the .NET 6.0.101 x64 SDK download site, then scanning again. This issue is tracked on dotnet/issue#7062

• We missed adding Win10 21H2 to our servicing list for 6.0.1 due to a timing issue around when it became eligible for servicing through Microsoft Update. We are fixing the issue on January 10th by making the 6.0.1 bundles available for Win10 21H2. In the meantime, if you need to update you can do so by downloading and installing from Download .NET 6.0 (Linux, macOS, and Windows) (microsoft.com) win10 21H2 WU (with "receive updates for other microsoft products") does not detect the .net 6.0.1 update #7047

• Windows Update error 0x80070643 trying to install "2021-11 .NET Core 3.1.21 Update for x64 Client (KB5007885)" #7093 .NET Core 3.1 and .NET 5.0 November updates installation failure on Windows due to December updates being unpublished from MU..

If there are any more issues with this release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.

[ghost]

Edit: Nevermind, it's been uploaded.

The .deb package of dotnet-sdk-6.0 depends on a version of dotnet-targeting-pack-6.0 that is unavailable. Are all point releases (all 6.0.x, all 5.0.x, etc) supposed to depend on the same version (6.0.0, 5.0.0, etc) of dotnet-targeting-pack?

[densen2014]

CentOS 7.9.2009 x86_64(Py3.7.8) can not update to 6.0.1

error message:

warning: /var/cache/yum/x86_64/7/packages-microsoft-com-prod/packages/aspnetcore-runtime-6.0.1-cm.1-x64.rpm: Header V4 RSA/SHA256 Signature, key ID 3135ce90: NOKEY
Retrieving key from https://packages.microsoft.com/keys/microsoft.asc


The GPG keys listed for the "packages-microsoft-com-prod" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.


 Failing package is: aspnetcore-runtime-6.0-6.0.1-1.x86_64
 GPG Keys are configured as: https://packages.microsoft.com/keys/microsoft.asc

[XieJJ99]

It seems that the symbol files are not uploaded to the symbol file server msdl.microsoft.com.
The server says ” ERROR: Not Found: libSystem.Globalization.Native.so.dbg – ‘http://msdl.microsoft.com/download/symbols/.debug/elf-buildid-sym-2a934a340f4219ec2e4c9f57e6ec2a3cb298333d/.debug’ “.
Step to repro:

# docker run --rm -ti mcr.microsoft.com/dotnet/sdk:latest /bin/bash
root@41e28a9ffe9f:/#  dotnet tool install -g dotnet-symbol
Tools directory '/root/.dotnet/tools' is not currently on the PATH environment variable.
If you are using bash, you can add it to your profile by running the following command:

cat << \EOF >> ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:/root/.dotnet/tools"
EOF

You can add it to the current session by running the following command:

export PATH="$PATH:/root/.dotnet/tools"

You can invoke the tool using the following command: dotnet-symbol
Tool 'dotnet-symbol' (version '1.0.252801') was successfully installed.
root@41e28a9ffe9f:/# export PATH="$PATH:/root/.dotnet/tools"
root@41e28a9ffe9f:/# dotnet symbol --symbols /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/libclrjit.so
Downloading from http://msdl.microsoft.com/download/symbols/
ERROR: Not Found: libclrjit.so.dbg - 'http://msdl.microsoft.com/download/symbols/_.debug/elf-buildid-sym-e75450847f8476fd4afaabef785f5accf410ab72/_.debug'

[rbhanda]

Hello @XieJJ99 which .NET release version is missing the symbols?

[rbhanda]

Hello @densen2014 this issue should have been resolved by now. Let us know if you are still seeing this issue

CentOS 7.9.2009 x86_64(Py3.7.8) can not update to 6.0.1

error message:

warning: /var/cache/yum/x86_64/7/packages-microsoft-com-prod/packages/aspnetcore-runtime-6.0.1-cm.1-x64.rpm: Header V4 RSA/SHA256 Signature, key ID 3135ce90: NOKEY
Retrieving key from https://packages.microsoft.com/keys/microsoft.asc


The GPG keys listed for the "packages-microsoft-com-prod" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.


 Failing package is: aspnetcore-runtime-6.0-6.0.1-1.x86_64
 GPG Keys are configured as: https://packages.microsoft.com/keys/microsoft.asc

[densen2014]

yes。it was fixed

[XieJJ99]

@rbhanda the latest servicing version: v6.0.1。

Hello @XieJJ99 which .NET release version is missing the symbols?

[stefanjarina]

Hello, updated today on my openSUSE systems and it seems that dotnet cmd binary is not placed in correct folder (or symlink is missing)
I am pretty certain that it was working before upgrade, but now I need to put this in my .zshrc: export PATH="/usr/share/dotnet:$PATH" or need to add symlink manually

locate dotnet | grep /bin/ returns nothing. I would expect binary to be in either /usr/bin/ or /usr/local/bin
It must have been there before as I did not need to update PATH manually before this release.

$ head -2 /etc/os-release
NAME="openSUSE Leap"
VERSION="15.2"

$ rpm -q dotnet-sdk-6.0
dotnet-sdk-6.0-6.0.101-1.x86_64

Thanks

[csinkers]

Hello @XieJJ99 which .NET release version is missing the symbols?

@rbhanda It looks like 5.0.13 is also missing symbols?

dotnet-symbol --symbols --output C:\Symbols "C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.13\coreclr.dll"
Downloading from http://msdl.microsoft.com/download/symbols/
Writing files to C:\Symbols
ERROR: Not Found: coreclr.pdb - 'http://msdl.microsoft.com/download/symbols/coreclr.pdb/2a9fafa9e64546068679b2658cb87ac01/coreclr.pdb'

[conioh]

That's 5 and 3, not 6.

I think it's relevant to #7062 but for some strange reason I can't comment there.

[conioh]

I've deleted anything remotely related, uninstalled VS 2019 completely. Still getting the error.
Installed the latest SDKs from the dotnet website (with runtimes 3.1.22 and 5.0.13). Still getting the error.
Deleted everything but 6 from the dotnet directory under Program Files. Still getting the error.
Installed the latest SDKs again. Still getting the error.

Given that I have runtimes 3.1.22 and 5.0.13 I really don't need "updates" to 3.1.21 and 5.0.12. How can I make this go away?

[akshaya-a]

For what it's worth, I know the +1 on your previous comment should have been sufficient, but there seems to be something strange about these specific versions - I also had exactly these two for a while.

Uninstalling VS2019 AND upgrading 2022 to the latest preview actually fixed the 5.0.12 for me, but I'm still stuck on the 3.1.21, and have similarly installed the latest version of the series (as well as attempted the exact version which failed due to a newer one being present).

[conioh]

@akshaya-a: Thanks for the tip.

I'll consider switching to the preview channel, but that's not something I really want to do. I'd like to have a more or less stable version of things and switching to a less stable version of VS just to make the error go away seems excessive. Since it doesn't even make both error go away I'm even less inclined to do that. What I'd really like is for Microsoft's installer to actually work. 🤷

[mess84]

Hosting Bundle is not updated.
The underlying ASP.NET Core Shared Frameworks (x64 & x86) are updated.
The underlying .NET Core Runtimes (x64 & x86) are updated.
This is leaving behind aspnetcorev2.dll (under C:\Program Files\IIS\Asp.Net Core Module\V2) on the original vulnerable version.

This particular server is patched via SCCM (CB) up until today we have not been syncing the WSUS classification/products for dotnet core. I have turned it on today, forced a SUP sync and created and ADR which is targeting a couple of test machines.

I was expecting to see 3.1.22 also? But it appears only 3.1.21 is available via WSUS? and no hosting bundle / ANCM at all?! This could lull a lot of people into a false sense of security. Has 3.1.22 been pulled / ever published via WSUS?

[artazar]

OS: Fedora 32
dotnet-runtime-deps package version 5.0.13 is missing on the repo
Error:

 Problem: cannot install the best update candidate for package dotnet-runtime-5.0-5.0.12-1.x86_64
  - nothing provides dotnet-runtime-deps-5.0 >= 5.0.13 needed by dotnet-runtime-5.0-5.0.13-1.x86_64

[rbhanda]

closed in favor of #7172