Windows Server 2016 · Version Status
Windows Server 2016 End of Life Date
Windows Server 2016 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚡
Windows Server 2016 reaches end of life on January 12, 2027. Plan your migration now — 66 days remaining.
📅 Get reminded before Windows Server 2016 reaches EOL on January 12, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jan 12, 2027
66 days remaining
Latest Release
10.0.14393
LTS release
Release Date
Oct 15, 2016
Windows Server 2016 series
Where these dates come from
End of lifeJan 12, 2027Vendor's own page, read by our adapter · learn.microsoft.com · checked Nov 3, 2026high · 3 sources agree End of active supportJan 11, 2022Vendor's own page, read by our adapter · learn.microsoft.com · checked Nov 3, 2026high · 3 sources agree ReleaseOct 15, 2016Vendor's own page, read by our adapter · learn.microsoft.com · checked Nov 3, 2026high · 3 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Windows Server 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 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
30/30 Critical tier
CISA KEV Exposure
20/20 Named in CISA 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 2016 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Windows Server Versions
What does Windows Server 2016 end of life mean?
When Windows Server 2016 reaches end of life, the maintainers stop issuing security patches for this version except under paid ESU, up to three years; no end date is published. 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Windows Server 2016 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Windows Server 2025 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Windows Server 2016 reach end of life?
Windows Server 2016 reaches end of life on January 12, 2027. That is 66 days remaining.
Is Windows Server 2016 still supported?
Windows Server 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 2016?
The recommended upgrade from Windows Server 2016 is
Windows Server 2025 — the latest actively supported version. Check the
Windows Server full timeline for all supported versions.
What are the security risks of running Windows Server 2016 past EOL?
When Windows Server 2016 reaches end of life, the maintainers stop issuing security patches except under paid ESU, up to three years; no end date is published. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Windows Server should migrate immediately or implement compensating controls.