Windows Server Core 2016 · Version Status
Windows Server Core 2016 End of Life Date
Windows Server Core 2016 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚡
Windows Server Core 2016 reaches end of life on January 12, 2027. Plan your migration now — 156 days remaining.
📅 Get reminded before Windows Server Core 2016 reaches EOL on January 12, 2027 — alerts 90, 30 & 7 days out.
EOL Date
Jan 12, 2027
156 days remaining
Latest Release
10.0.14393
LTS release
Release Date
Oct 15, 2016
Windows Server Core 2016 series
Lifecycle detail
Windows Server Core 2016 was released on October 15, 2016 and support is scheduled to end on January 12, 2027 — a planned supported lifespan of 10 years and 3 months, in line with the 10 years and 2 months median for Windows Server Core LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Windows Server Core 2016 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Windows Server Core Versions
| Version | Latest | EOL Date | Status |
|---|
| 2008-SP2 LTS |
6.0.6003 |
Jan 14, 2020 |
EOL |
| 2008-R2-SP1 LTS |
6.1.7601 |
Jan 14, 2020 |
EOL |
| 2012 LTS |
6.2.9200 |
Oct 10, 2023 |
EOL |
| 2012-R2 LTS |
6.3.9600 |
Oct 10, 2023 |
EOL |
| → 2016 LTS |
10.0.14393 |
Jan 12, 2027 |
Warning |
| 1607 |
10.0.14393 |
Jan 11, 2022 |
EOL |
| 1709 |
10.0.16299 |
Apr 9, 2019 |
EOL |
| 1803 |
10.0.17134 |
Nov 12, 2019 |
EOL |
What does Windows Server Core 2016 end of life mean?
When Windows Server Core 2016 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Windows Server Core 2016 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Windows Server Core 2025 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Windows Server Core 2016 reach end of life?
Windows Server Core 2016 reached end of life on January 12, 2027. That is 156 days remaining.
Is Windows Server Core 2016 still supported?
Windows Server Core 2016 is still supported but approaching end of life on January 12, 2027. Begin planning your migration now.
What should I upgrade to from Windows Server Core 2016?
The recommended upgrade from Windows Server Core 2016 is
Windows Server Core 2025 — the latest actively supported version. Check the
Windows Server Core full timeline for all supported versions.
What are the security risks of running Windows Server Core 2016 past EOL?
When Windows Server Core 2016 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Windows Server Core should migrate immediately or implement compensating controls.