January 2027 Microsoft End of Support: Windows Server 2016 and More

By Scott Bissett Published: October 14, 2026 Two days, twenty products

January 12, 2027

Windows Server 2016 and the January 12 group reach end of support

days remaining

Microsoft's 2027 end-of-support list puts twenty products on two consecutive days. On January 11, 2027 the System Center 2016 suite, BizTalk Server 2016, Dynamics NAV 2017 and Team Foundation Server 2017 reach end of support. On January 12 it is Windows Server 2016 itself, with Hyper-V Server 2016, the roles that ship inside 2016, .NET Framework 4.6.2 and Windows 10 Enterprise LTSC 2021. Windows Server 2016 is the one with a published paid bridge. Check each of the others before assuming one exists.

Quick answer: The Windows Server 2016 end-of-life (EOL) date is January 12, 2027. Active support ended on January 11, 2022; security fixes continue until the end-of-life date. Every Windows Server version's release and end-of-support date is on the Windows Server lifecycle page.

Key Dates at a Glance

Windows Server 2016 — extended support ends January 12, 2027; paid Extended Security Updates run up to three years after that, through 2030.
Hyper-V Server 2016 — ends January 12, 2027. Hyper-V Server 2019 is supported to January 9, 2029.
.NET Framework 4.6.2 — ends January 12, 2027. Microsoft lists no end date for 4.7 through 4.8.1.
Windows 10 Enterprise LTSC 2021 — ends January 12, 2027. The IoT Enterprise edition of the same release runs to January 13, 2032.
System Center 2016 (Data Protection Manager, Operations Manager, Orchestrator, Service Manager, Virtual Machine Manager) — ends January 11, 2027.
BizTalk Server 2016 — ends January 11, 2027.
Dynamics NAV 2017 — ends January 11, 2027.
Team Foundation Server 2017 — ends January 11, 2027.

Running Windows Server past end of life?

Extended support past the official EOL date exists for many products in this position — whether it covers Windows Server is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Windows Server 2016: the one with a published bridge

Windows Server 2016 left mainstream support on January 11, 2022 and has received security fixes only since then. That stops on January 12, 2027. It also has a sanctioned bridge: Microsoft sells Extended Security Updates for up to three years after the end date, through 2030. Our Windows Server 2016 ESU guide covers what the program includes and how it is bought, and the Windows Server 2016 end-of-life guide covers the upgrade paths.

Microsoft's list counts the roles that ship inside 2016 as separate entries ending the same day: IIS 10 on Windows Server 2016, Windows Server Update Services for Windows Server 2016, Windows Defender for Windows Server 2016 and Windows Azure Pack on Windows Server 2016, plus Windows Storage Server 2016 and HPC Pack 2016. They are not separate decisions. A 2016 server that moves to a supported release takes its IIS, WSUS and Defender with it.

Hyper-V Server 2016, the free standalone hypervisor, ends on the same day, January 12, 2027. Hosts on it need a new home: Hyper-V Server 2019 is supported to January 9, 2029, and the Hyper-V role on a current Windows Server release runs much longer.

.NET Framework 4.6.2: the quiet one with the widest reach

Support for .NET Framework 4.6.2 ends on January 12, 2027. Microsoft's .NET Framework lifecycle page lists no end date for 4.7, 4.7.1, 4.7.2, 4.8 or 4.8.1, so the fix is a version move inside the 4.x line, not a rewrite. Microsoft documents 4.7 through 4.8 as in-place updates to .NET Framework 4.5: installing 4.8 replaces the 4.x runtime on the machine, and an application built for 4.6.2 normally keeps running on it. "Normally" is the word that matters. Test line-of-business applications on 4.8 before a fleet-wide rollout, because an in-place runtime change affects every 4.x application on the machine at once.

This is separate from modern .NET (.NET 8, 9 and 10), which has its own support calendar. Our .NET Framework lifecycle page has every 4.x version on one page.

Windows 10 Enterprise LTSC 2021: check the edition, not the build

Windows 10 Enterprise LTSC 2021 ends on January 12, 2027. Windows 10 IoT Enterprise LTSC 2021 is built from the same release and carries the same build number, but Microsoft supports it to January 13, 2032. A device inventory that reports only the version string cannot tell the two apart. Read the edition before deciding which kiosks, lab machines and line controllers are affected. The rest of the Windows 10 picture, including the October 2025 end of the mainstream editions, is in our Windows 10 end-of-life guide.

January 11: System Center, BizTalk, NAV and TFS

System Center 2016 ends on January 11, 2027 for all five components Microsoft lists: Data Protection Manager, Operations Manager, Orchestrator, Service Manager and Virtual Machine Manager. System Center 2025 is the current release, with mainstream support to January 8, 2030 and extended support to January 9, 2035. Configuration Manager's 2016 long-term branch (LTSB, version 1606) is on the January 12 list.

BizTalk Server 2016 ends on January 11, 2027, and Host Integration Server 2016 ends with it. BizTalk Server 2020 is the supported release: Microsoft extended its mainstream support to April 11, 2028, and extended support runs to April 9, 2030.

Dynamics NAV 2017 ends on January 11, 2027. NAV 2018, the newest NAV release, follows on January 11, 2028, so an upgrade inside NAV buys one year. The longer route is Business Central, covered in our Business Central lifecycle guide.

Team Foundation Server 2017, the release before the product was renamed Azure DevOps Server, ends on January 11, 2027. Its repositories, work items and build pipelines move either to a current Azure DevOps Server release or to the hosted Azure DevOps Services.

The triage order

Inventory Windows Server 2016 and Hyper-V Server 2016 first. They carry the most workloads. Decide per server: upgrade, rebuild, or buy ESU for what cannot move by January 12, 2027.
Find every .NET Framework 4.6.2 machine. Moving to 4.8 is usually a patch-window job, not a project, but it touches every 4.x application on the machine, so test first.
Check LTSC devices by edition. Enterprise LTSC 2021 ends in January; IoT Enterprise LTSC 2021 does not.
Schedule the January 11 platforms. System Center, BizTalk, NAV and TFS upgrades are application migrations with their own testing, and they end a day before Windows Server 2016 does.

Not sure what you're running? Paste a server or software list into our free stack scanner. It checks every line against the same lifecycle data this page is built on, in your browser, with nothing uploaded.

Frequently Asked Questions

What Microsoft products reach end of support in January 2027?

Microsoft's end-of-support list for 2027 puts two groups on consecutive days. On January 11, 2027: BizTalk Server 2016, Dynamics NAV 2017, Host Integration Server 2016, the five System Center 2016 components (Data Protection Manager, Operations Manager, Orchestrator, Service Manager and Virtual Machine Manager) and Team Foundation Server 2017. On January 12, 2027: Windows Server 2016, Hyper-V Server 2016, Windows Storage Server 2016, IIS 10 and WSUS on Windows Server 2016, Windows Defender for Windows Server 2016, Windows Azure Pack, HPC Pack 2016, .NET Framework 4.6.2, Windows 10 Enterprise LTSC 2021 and Configuration Manager (LTSB, version 1606).

Is Windows Server 2016 end of life in January 2027?

Extended support for Windows Server 2016 ends on January 12, 2027, which is its end of life under Microsoft's Fixed Lifecycle Policy. Microsoft offers paid Extended Security Updates for up to three years after that, through 2030, so organizations that cannot migrate in time have a sanctioned bridge. Hyper-V Server 2016 ends the same day.

What happens to .NET Framework 4.6.2 in January 2027?

Support for .NET Framework 4.6.2 ends on January 12, 2027. Microsoft's .NET Framework lifecycle page lists no end date for versions 4.7 through 4.8.1, and Microsoft documents 4.7 through 4.8 as in-place updates to .NET Framework 4.5, so an application built for 4.6.2 normally keeps running when the machine moves to 4.8. Test before rolling out.

Does Windows 10 IoT Enterprise LTSC 2021 also end in January 2027?

No. Windows 10 Enterprise LTSC 2021 ends on January 12, 2027, but Windows 10 IoT Enterprise LTSC 2021 is supported until January 13, 2032. The two editions share a build number, so check the edition, not the version string, before deciding which devices are affected.

Why do some products end on January 11 and others on January 12?

Microsoft's own end-of-support list for 2027 places them on the two days. Its lifecycle pages print each end as a UTC timestamp early the next morning, so BizTalk Server 2016 shows 1/12/2027 6:59:59 AM, which is the end of January 11 in Pacific time, and Windows Server 2016 shows 1/13/2027 6:59:59 AM, the end of January 12.