Public | Automated Build

Last pushed: a year ago
Short Description
Windows SDK 10.1 for Windows Container (base: microsoft/windowsservercore)
Full Description

Tags (i.e. Version history)

  1. latest:
    This is the oldest version even with a "Latest" name, in order to not break people's CI/CD pipeline we kept it for now, it might be removed later since it was using very old base image.

  2. srv2016rtm:
    This one replaced the old base image with RTM base image, but still using Chocolatey for sdk installation.

  3. 10.0.10586.212:
    This one has a proper beautiful name, and no longer using Chocolatey.

What's New:


  • No longer using Chocolatey for sdk install, downloading from Microsoft directly.


  • We now using microsoft/windowsservercore as base OS image, instead of TP5 era windowsservercore.


  1. The Problem:
    When you try to install the SDK, it will stop in the middle leaving you an incomplete state. The hero is Windows Desktop Extension SDK-x86_en-us.msi, despite all other 50+ MSIs install perfectly, this guy decided to call C:\Program Files (x86)\Windows Kits\10\bin\x86\GenerateUnionWinMD.cmd, within this script we got:

    REM Check for elevation
    net session >nul 2>&1
    if %ERRORLEVEL% EQU 0 (
       ECHO Confirmed running as administrator
    ) else (
       ECHO Error: You must run this script from an elevated command prompt.
       EXIT /B 2

    It was calling net session to check if you are running as administrator. And although we are admin inside the container, the Server service is not running, and we can't start it either, it's not supported as of TP5, full stop.

    Reference Link on TechNet forum

  2. The solution:
    We fake the net.exe with a skeleton .net application which does not do anything, so long as exit with 0 to make the script happy. We replace the real net.exe with our fake one and put the real one back after the installation.

Please refer to

Docker Pull Command
Source Repository