Short answer: Windows Server 2016 reaches end of support on January 12, 2027. After that date Microsoft stops shipping free security updates for it. The servers keep running, but every new vulnerability stays open unless the server is covered by paid Extended Security Updates (ESU), which Microsoft lists for three more years, ending in January 2030. Upgrade what you can, cover what you cannot move yet, and keep every remaining 2016 server patched and counted until it is gone.
Windows Server 2016 end of support dates
These dates come from Microsoft's lifecycle page for Windows Server 2016, which follows the Fixed Lifecycle Policy.
| Milestone | Date |
|---|---|
| Release | October 15, 2016 |
| Mainstream support ended | January 11, 2022 |
| Extended support ends | January 12, 2027 |
| ESU year 1 | January 13, 2027 to January 11, 2028 |
| ESU year 2 | January 12, 2028 to January 9, 2029 |
| ESU year 3 | January 10, 2029 to January 8, 2030 |
The same dates apply to the Datacenter, Standard, and Essentials editions.
What changes on January 12, 2027
Nothing switches off. A Windows Server 2016 machine boots and serves its workload the next morning the same way it did the day before. What ends is maintenance:
- No more free security updates. The January 2027 monthly update is the last one every Windows Server 2016 machine receives. Vulnerabilities disclosed after it are fixed only for servers covered by ESU.
- No more fixes for other bugs. Reliability and compatibility problems found after the date are not corrected.
- No more standard support. Microsoft support no longer takes cases for the product outside an ESU agreement.
Windows Server 2016 is the server counterpart of Windows 10 version 1607, and it shares most of its code with Windows 10. Flaws found in current Windows versions often exist in 2016 as well, so the list of open vulnerabilities on an unsupported 2016 server grows every month.
What else ends with it
Two things tend to be missed in planning:
- .NET Framework 4.6.2. Microsoft lists January 12, 2027 as its end of support too. It is the version that shipped with Windows Server 2016, and applications that still target it should move to .NET Framework 4.8.
- Third-party support. Backup agents, security tools, databases, and line-of-business software usually drop an operating system soon after Microsoft does. Check each vendor's statement for the software on your 2016 servers.
Your options
Most teams end up using all three.
- Upgrade or migrate to a supported release. Windows Server 2022 and Windows Server 2025 are the current long-term releases. An in-place upgrade keeps the server's roles and data where they are. A migration to a new server is cleaner for domain controllers and for anything that has been upgraded in place before. Confirm the supported path with Microsoft's documentation and with the vendors of the software on the server.
- Cover what cannot move yet with Extended Security Updates. ESU keeps critical and important security updates coming for up to three more years. It is paid, it is renewed each year, and it covers security updates only. Treat it as time to finish a migration, not as a place to stay.
- Retire what nobody needs. An end-of-support deadline is a good reason to find the servers that are still running only because nobody turned them off.
How to plan the last months
- Count the servers. Build the list of every machine still on Windows Server 2016, with its role and its owner. The list is usually longer than expected.
- Keep patching until the last update. Install each monthly update through January 2027. A server that enters the unsupported period already behind is exposed twice.
- Decide per server. Upgrade, migrate, retire, or ESU. Write the decision next to each server so the list shrinks on a schedule.
- Plan for what stays. For servers that will run past the date, arrange ESU before January and limit what can reach them on the network.
How TridentStack Control helps
TridentStack Control patches Windows Server 2016 alongside Windows Server 2019, 2022, and 2025 from one cloud console, so the servers you are retiring and the servers replacing them are managed in the same place. One lightweight agent covers Windows, macOS, and Linux, plus third-party application updates.
The inventory shows which endpoints still run Windows Server 2016, so the count is always current. Vulnerability scanning for Windows lists the open CVEs on each server with CISA KEV context, and once a server is past its end-of-support date it separates the fixes you can still apply from the ones that need an ESU license. Compliance scoring against the DISA STIG for Windows Server 2016 shows where an aging server has drifted.
The first 200 endpoints are free forever, then 5 dollars per endpoint per month, with every feature included. Start free with TridentStack Control and see how many Windows Server 2016 machines you have left.
Also running older desktops? See Windows 10 end of life: what to do.
FAQ
When does Windows Server 2016 reach end of life?
Windows Server 2016 reaches the end of extended support on January 12, 2027. Mainstream support ended on January 11, 2022. After January 12, 2027, Microsoft stops shipping free security updates for it.
Will Windows Server 2016 still work after January 12, 2027?
Yes. The servers keep running and nothing is switched off. What stops is the free monthly security updates, so every vulnerability disclosed after that date stays open unless the server is covered by Extended Security Updates.
Are there Extended Security Updates for Windows Server 2016?
Yes. Microsoft's lifecycle page lists three years of Extended Security Updates for Windows Server 2016: year one from January 13, 2027, year two from January 12, 2028, and year three ending on January 8, 2030. ESU is a paid program that covers security updates only.
What should I upgrade Windows Server 2016 to?
Windows Server 2022 and Windows Server 2025 are the current long-term releases. Windows Server 2025 has the longest remaining support. Check Microsoft's supported upgrade paths and your application vendors' support statements before choosing between an in-place upgrade and a migration to new servers.
Does .NET Framework 4.6.2 end at the same time?
Yes. Microsoft lists January 12, 2027 as the end of support for .NET Framework 4.6.2, the same day as Windows Server 2016. Applications that still target 4.6.2 should move to .NET Framework 4.8, which is supported for as long as the Windows version it runs on.
How do I keep Windows Server 2016 patched until I can move off it?
Keep installing every monthly update through January 2027, keep an accurate list of which servers still run 2016, and decide per server whether it will be upgraded, retired, or covered by Extended Security Updates. A patch management tool that covers every Windows Server version from one console keeps that list and the patching in one place.