Server Core LTSC 2016 contains .NET Framework 4.7.2 instead of 4.6.2
Describe the bug According to this documentation: https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-462
Server Core LTSC 2016 should have .NET Framework 4.6.2 installed. However, when using the latest LTSC 2016 container, .NET Framework 4.7.2 is actually installed:
C:\Users\paulmedynski\dev\FrameworkDescription>docker run -it -v %cd%:c:/test mcr.microsoft.com/windows/servercore:ltsc2016 powershell.exe -ExecutionPolicy Unrestricted
Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
PS C:\> cd test
PS C:\test> .\DotNetVersions.exe -b
4.0.0.0
4.7.03062
PS C:\test> .\GetDotNetVersion.ps1
.NET Framework Product Version Release
-------------- ------- ------- -------
Client 4.7.2 4.7.03062 461814
Full 4.7.2 4.7.03062 461814
Client 4.0.0.0
To Reproduce Pull the latest Server Core LTSC 2016 image and run it.
Expected behavior Server Core LTSC 2016 contains .NET Framework 4.6.2.
Configuration:
- Edition: Windows 11 Enterprise
- Base Image being used: Windows Server Core LTSC 2016
- Container engine: docker
- Container Engine version: Docker version 27.4.0, build bde2b89
Additional context See the discussion with the .NET Framework container team related to this: https://github.com/microsoft/dotnet-framework-docker/discussions/1202
Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.
We've got an internal email thread discussing this. Will post an update when we have one.
It looks like Server Core LTSC 2016 should contain .NET framework 4.7.2. The documentation was incorrect so we're working to update that.
This is still an issue.
Hi @lbussell, thank you for your patience. We're still communicating with the documentation team so that they can make the necessary changes to the documentation.
We don't own the .NET documentation but I believe the responsible team is aware and will make the necessary changes.
This is still an issue.
We've got people working on it.
Can we assign someone to this issue @ntrappe-msft?
This issue has been open for 30 days with no updates. no assignees, please provide an update or close this issue.
This issue has been open for 30 days with no updates. no assignees, please provide an update or close this issue.
This issue has been open for 30 days with no updates. no assignees, please provide an update or close this issue.