microsoft/windowsLTSC2019 (LTSC) docker pull mcr.microsoft.com/windows:ltsc2019Note: We are not building this container image with the Windows Server 2022 release. However, you can use the Windows Server base OS container image that comes with Windows Server 2022 release: windows/server.
This is a base image for Windows Server containers. This image carries the Windows base OS image
For more information about servicing lifecycles, visit Base Image Servicing Lifecycles.
Windows requires the host OS version to match the container OS version. If you want to run a container based on a newer Windows build, make sure you have an equivalent host build. Otherwise, you can use Hyper-V isolation to run older containers on new host builds. You can read more on Windows Container Version Compatibility in our Container Docs.
The default entrypoint is for this image is Cmd.exe. To run the image:
docker run mcr.microsoft.com/windows:ltsc2019
Note: This repo does not publish or maintain a latest tag. Please declare a specific tag when pulling or referencing images from this repo.
| Tags | Architecture | Dockerfile | OsVersion | CreatedTime | LastUpdatedTime |
|---|---|---|---|---|---|
| 20H2 | multiarch | No Dockerfile | 10.0.***.1889 | 11/10/2020 | 08/09/2022 |
| 20H2-KB5016616 | multiarch | No Dockerfile | 10.0.***.1889 | 08/09/2022 | 08/09/2022 |
| 10.0.***.1889 | multiarch | No Dockerfile | 10.0.***.1889 | 08/09/2022 | 08/09/2022 |
| 20H2-amd64 | amd64 | No Dockerfile | 10.0.***.1889 | 11/10/2020 | 08/09/2022 |
| 20H2-KB5016616-amd64 | amd64 | No Dockerfile | 10.0.***.1889 | 08/09/2022 | 08/09/2022 |
| 10.0.***.1889-amd64 | amd64 | No Dockerfile | 10.0.***.1889 | 08/09/2022 | 08/09/2022 |
| 2004 | multiarch | No Dockerfile | 10.0.***.1415 | 05/27/2020 | 12/14/2021 |
| 2004-KB5008212 | multiarch | No Dockerfile | 10.0.***.1415 | 12/14/2021 | 12/14/2021 |
| 10.0.***.1415 | multiarch | No Dockerfile | 10.0.***.1415 | 12/14/2021 | 12/14/2021 |
| 2004-amd64 | amd64 | No Dockerfile | 10.0.***.1415 | 05/27/2020 | 12/14/2021 |
| 2004-KB5008212-amd64 | amd64 | No Dockerfile | 10.0.***.1415 | 12/14/2021 | 12/14/2021 |
| 10.0.***.1415-amd64 | amd64 | No Dockerfile | 10.0.***.1415 | 12/14/2021 | 12/14/2021 |
| 1909 | multiarch | No Dockerfile | 10.0.***.1556 | 11/12/2019 | 05/11/2021 |
| 1909-KB5003169 | multiarch | No Dockerfile | 10.0.***.1556 | 05/11/2021 | 05/11/2021 |
| 10.0.***.1556 | multiarch | No Dockerfile | 10.0.***.1556 | 05/11/2021 | 05/11/2021 |
| 1909-amd64 | amd64 | No Dockerfile | 10.0.***.1556 | 11/12/2019 | 05/11/2021 |
| 1909-KB5003169-amd64 | amd64 | No Dockerfile | 10.0.***.1556 | 05/11/2021 | 05/11/2021 |
| 10.0.***.1556-amd64 | amd64 | No Dockerfile | 10.0.***.1556 | 05/11/2021 | 05/11/2021 |
| ltsc2019 | multiarch | No Dockerfile | 10.0.***.8146 | 08/09/2022 | 12/09/2025 |
| 1809 | multiarch | No Dockerfile | 10.0.***.8146 | 11/13/2018 | 12/09/2025 |
| 1809-KB5071544 | multiarch | No Dockerfile | 10.0.***.8146 | 12/09/2025 | 12/09/2025 |
| 10.0.***.8146 | multiarch | No Dockerfile | 10.0.***.8146 | 12/09/2025 | 12/09/2025 |
| ltsc2019-amd64 | amd64 | No Dockerfile | 10.0.***.8146 | 08/09/2022 | 12/09/2025 |
| 1809-amd64 | amd64 | No Dockerfile | 10.0.***.8146 | 04/05/2019 | 12/09/2025 |
| 1809-KB5071544-amd64 | amd64 | No Dockerfile | 10.0.***.8146 | 12/09/2025 | 12/09/2025 |
| 10.0.***.8146-amd64 | amd64 | No Dockerfile | 10.0.***.8146 | 12/09/2025 | 12/09/2025 |
| Tags | Achitecture | OS | OsVersion | CreatedTime | LastUpdated Time |
|---|---|---|---|---|---|
| 20H2 | multiarch | windows | 10.0.***.1889 | 11/10/2020 | 08/09/2022 |
| 20H2-KB5016616 | multiarch | windows | 10.0.***.1889 | 08/09/2022 | 08/09/2022 |
| 10.0.***.1889 | multiarch | windows | 10.0.***.1889 | 08/09/2022 | 08/09/2022 |
| 2004 | multiarch | windows | 10.0.***.1415 | 05/27/2020 | 12/14/2021 |
| 2004-KB5008212 | multiarch | windows | 10.0.***.1415 | 12/14/2021 | 12/14/2021 |
| 10.0.***.1415 | multiarch | windows | 10.0.***.1415 | 12/14/2021 | 12/14/2021 |
| 1909 | multiarch | windows | 10.0.***.1556 | 11/12/2019 | 05/11/2021 |
| 1909-KB5003169 | multiarch | windows | 10.0.***.1556 | 05/11/2021 | 05/11/2021 |
| 10.0.***.1556 | multiarch | windows | 10.0.***.1556 | 05/11/2021 | 05/11/2021 |
| ltsc2019 | multiarch | windows | 10.0.***.8146 | 08/09/2022 | 12/09/2025 |
| 1809 | multiarch | windows | 10.0.***.8146 | 11/13/2018 | 12/09/2025 |
| 1809-KB5071544 | multiarch | windows | 10.0.***.8146 | 12/09/2025 | 12/09/2025 |
| 10.0.***.8146 | multiarch | windows | 10.0.***.8146 | 12/09/2025 | 12/09/2025 |
You can retrieve a list of all available tags for windows at [***]
File an issue
Contact Microsoft Support
MICROSOFT SOFTWARE SUPPLEMENTAL LICENSE FOR WINDOWS CONTAINER BASE IMAGE
This Supplemental License is for the Windows Container Base Image (“Container Image”). If you comply with the terms of this Supplemental License you may use the Container Image as described below.
CONTAINER OS IMAGE
The Container Image may only be used with a validly licensed copy of:
The Server Host Software, Client Host Software, and IoT Host Software are collectively referred to as the “Host Software” and a license for Host Software is a "Host License".
You may not use the Container Image if you do not have a corresponding version and edition of the Host License. Certain restrictions and additional terms may apply, which are described herein. If licensing terms herein conflict with Host License, then this Supplemental License shall govern with respect to the Container Image. BY ACCEPTING THIS SUPPLEMENTAL LICENSE OR USING THE CONTAINER IMAGE, YOU AGREE TO ALL OF THESE TERMS. IF YOU DO NOT ACCEPT AND COMPLY WITH THESE TERMS, YOU MAY NOT USE THE CONTAINER IMAGE.
DEFINITIONS
Windows Server Container (without Hyper-V isolation) is a feature of Microsoft Windows Server software.
Windows Server Container with Hyper-V isolation. Section 2(k) of the Microsoft Windows Server license terms is hereby deleted in its entirety and replaced with the revised terms as shown in “UPDATED” below.
UPDATED: Windows Server Container with Hyper-V isolation (formerly known as Hyper-V Container) is a container technology in Windows Server which utilizes a virtual operating system environment to host one or more Windows Server Container(s). Each Hyper-V isolation instance used to host one or more Windows Server Container(s) is considered one virtual operating system environment.
LICENSE TERMS
Host License. The Host License terms apply to your use of the Container Image and any Windows container(s) created with the Container Image which are distinct and separate from a virtual machine.
Use Rights. The Container Image may be used to create an isolated virtualized Windows operating system environment that includes at least one application that adds primary and significant functionality. You may use the Container Image only to create, build, and run Windows container(s) on Host Software. Updates to the Host Software may not update the Container Image so you may re-create any Windows containers based on an updated Container Image.
Restrictions. You may not remove this Supplemental License document file from the Container Image. You may not enable remote access to the application(s) you run within your container to avoid applicable license fees. You may not reverse engineer, decompile, or disassemble the Container Image, or attempt to do so, except and only to the extent required by third party licensing terms governing the use of certain open-source components that may be included with the software. Additional restrictions in the Host License may apply.
ADDITIONAL TERMS
Client Host Software. When running a Container Image on Client Host Software you may run any number of the Container Image instantiated as Windows containers for test or development purposes only. You may not use these Windows containers in a production environment on Client Host Software.
IoT Host Software. When running a Container Image on IoT Host Software you may run any number of the Container Image instantiated as Windows containers for test or development purposes only. You may only use the Container Image in a production environment if you have agreed to the Microsoft Commercial Terms of Use for Windows 10 Core Runtime Images or the Windows 10 IoT Enterprise Device License (“Windows IoT Commercial Agreement”). Additional terms and restrictions in the Windows IoT Commercial Agreements apply to your use of Container Image in a production environment.
Third Party Software. The Container Image may include third party applications that are licensed to you under this Supplemental License or under their own terms. License terms, notices, and acknowledgements, if any, for the third-party applications may be accessible online at [***] or in an accompanying notices file. Even if such applications are governed by other agreements, the disclaimer, limitations on, and exclusions of damages in the Host License also apply to the extent allowed by applicable law.
Open Source Components. The Container Image may contain third party copyrighted software licensed under open source licenses with source code availability obligations. Copies of those licenses are included in the ThirdPartyNotices file or other accompanying notices file. You may obtain the complete corresponding source code from Microsoft if and as required under the relevant open source license by sending a money order or check for $5.00 to: Source Code Compliance Team, Microsoft Corporation, 1 Microsoft Way, Redmond, WA 98052, USA. Please include the name “Microsoft Software Supplemental License for Windows Container base image,“ the open source component name and version number in the memo line of your payment. You may also find a copy of the source at [***]
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务