microsoft / microsoft/Windows-Containers

Server Core LTSC 2016 contains .NET Framework 4.7.2 instead of 4.6.2

Open
#562 23 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug documentation
Dominant language
PowerShell
Stars
551
Forks
76
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by pulling mcr.microsoft.com/windows/servercore:ltsc2016 and rerunning the reported PowerShell commands, including DotNetVersions.exe and GetDotNetVersion.ps1. Compare the result with the Microsoft version-and-dependencies documentation and the linked .NET Framework container discussion. Done means the discrepancy is resolved or its ownership and expected behavior are clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, powershell
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.