Skip to main content
Guide, 5 minute read

What Happens to Windows Server 2016 After January 12, 2027

What changes on the day Windows Server 2016 leaves extended support, what keeps working, what you lose, and the three things to have in writing before the date: an inventory, a path per server, and coverage for the stragglers.

Planning guidesIT leaders and business owners who still have Windows Server 2016 in production and need a plain answer about the risk after the deadlineBy , Founder and CEO, Days Dynamics. Published November 9, 2026, updated November 10, 2026.

The servers keep running. The security updates stop.

Nothing switches off on January 12, 2027; a Windows Server 2016 machine still boots, serves files, and runs applications exactly as it did the day before. What stops is Microsoft's security updates for the operating system, unless the server is covered by Extended Security Updates, which deliver Critical and Important updates for up to three years, through 2030. Every new vulnerability found after the date stays open on an uncovered server. That is the whole risk, and it grows each month.

What changes and what does not

AreaAfter January 12, 2027
Operating system security updatesStop, unless the server has Extended Security Updates (Standard and Datacenter editions)
Nonsecurity fixes and new featuresStop for everyone; ESUs do not include them
Microsoft support casesFixed lifecycle products leave support on the extended end date; plan on no new fixes
The applications on the serverKeep running; vendors set their own support windows for the operating system they run on
Related 2016 productsHyper-V Server 2016, Windows Storage Server 2016, and WSUS for Windows Server 2016 end the same day; SQL Server 2017 follows on October 12, 2027

See the Windows Server 2016 Extended Security Updates guide.

Questions that come up in the first month after

We missed the date. Is ESU still available?

Yes, for Standard and Datacenter editions with the right licensing. Arc-enabled ESU billing is monthly and a license provisioned after the end of support is back-billed to January 12, 2027, so enrolling late does not reduce the cost.

Can we just isolate the server?

Network segmentation reduces exposure and is worth doing for any server that must stay. It does not replace security updates, and an isolated server that users still reach is still reachable by what reaches those users.

What about our cyber insurance or compliance audit?

Policies and frameworks set their own rules about unsupported software. Ask your insurer and auditor directly what they require; the answer varies and this guide does not state it for them.

Is a one-year bridge enough?

Microsoft's published ESU pricing basis (written for the 2012 program) is 100% of the full license price per year, so each year of delay costs about a new license per server. A one-year bridge with a dated migration plan is a reasonable use; a third year rarely is.

Three things to have in writing before the date

  • An inventory: every Windows Server 2016 and Hyper-V Server 2016 machine, with edition, licensing program, role, hardware warranty date, and application owner.
  • A path per server: upgrade in place to 2019, 2022, or 2025; replace the host; move to Azure or another platform; or bridge with ESU, with a date for each.
  • Coverage for the stragglers: ESU enrollment arranged (Azure Arc or volume licensing) for the servers that will still be on 2016 on January 13, 2027, when Arc billing begins.

See the Windows Server 2016 upgrade paths guide and the Windows Server 2016 end of life guide.

If you have not started

  • Count the servers this week. Most mid-market estates have fewer than they think, plus two that nobody remembered.
  • Default new builds to Windows Server 2025, whose extended support runs to November 14, 2034.
  • Put the servers that cannot move on ESU with an end date, and treat the rest as a project with a schedule.
  • If the team does not have the time, a fixed-fee end-of-support assessment produces the inventory and the plan.

See the Infrastructure End-of-Support Assessment and the Windows Server 2016 replacement service.

Get the inventory and the plan before the date

Send us what you know about your Windows Server 2016 estate, even if it is a rough list. We will help you complete the inventory, mark a path for each server, and arrange coverage for the ones that cannot move in time. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.

Sources

Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.

Planning this project now?

Turn the checklist into a plan

The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.