Key Takeaways
- Microsoft ends extended support for Windows Server 2016 on January 12, 2027. After that, there are no more security patches unless you pay for Extended Security Updates (ESU).
- ESU can buy you up to three years, but it costs, doesn’t include technical support, and only postpones the decision.
- Unpatched, internet-facing systems are one of the most common ways attackers get in.
- You have four options for each server: upgrade, move to the cloud, retire it, or buy time with ESU. The right answer often changes from one server to the next.
Somewhere in a lot of companies, there’s a server nobody likes to talk about. It went in around 2017. It runs the enterprise resource planning (ERP) system, or the badge readers, or a line-of-business app the vendor stopped updating years ago. It works fine, so nobody has touched it.
On January 12, 2027, that server becomes a liability. That’s the day Microsoft ends extended support for Windows Server 2016, and as of this writing, it’s about 8 weeks away. Factor in the holidays, and the real working time is shorter than that.
What “End of Support” Actually Means
After January 12, Server 2016 systems get one final monthly security update. Then the patches, bug fixes, and technical support stop, according to Help Net Security. The server will keep running. It just won’t get fixes for any new vulnerabilities that turn up, and attackers know exactly which systems those are.
If your Server 2016 machines also run SQL Server 2016, part of that stack is already unsupported. Microsoft ended support for SQL Server 2016 on July 14, 2026. This will feel familiar if you lived through the end of Windows 10 support last year. The difference is that servers tend to hold the systems a business can least afford to lose.
Why an Old Server is Such an Easy Target
The 2026 Verizon Data Breach Investigations Report (DBIR) found that exploiting software vulnerabilities has become the most common way attackers break in, overtaking stolen credentials for the first time in the report’s 19-year history. Even for supported systems, the median time for organizations to fully patch a vulnerability after finding it grew to 43 days, Help Net Security reported. An unsupported server never gets a patch to apply.
There’s a compliance angle, too. Auditors, regulators and cyber insurance underwriters routinely ask whether you’re running unsupported software. For healthcare and financial services organizations in particular, “we’re working on it” isn’t a great answer to give after the deadline has passed.
Your Four Options, Server by Server
The most useful way to approach this is one server at a time. A single company might upgrade three servers, move two workloads to the cloud, shut one down entirely and buy ESU for the one that runs a stubborn legacy app.
- Upgrade to Windows Server 2025. This is Microsoft’s recommended path. Check two things before you commit: whether your hardware can handle it and whether the vendors behind your applications support them on the new version. A server bought in 2017 is probably past its warranty, so this may be the moment to rethink the hardware as well.
- Move the workload to Azure, or replace the app. For some workloads, it makes more sense to stop running them on your own hardware at all. Microsoft is also nudging customers toward Azure as a migration path. Sometimes the better move is replacing an aging on-premises app with a software-as-a-service (SaaS) version that someone else keeps patched.
- Retire or consolidate it. Inventories almost always turn up a server or two that’s still running out of habit. If nothing important depends on it, shut it down.
- Buy time with ESU. Microsoft is offering up to three years of ESU for Server 2016, delivered through Azure Arc with subscription billing. Microsoft hasn’t published Server 2016 ESU pricing, and The Register noted that the first year of ESU for Windows Server 2012 cost the equivalent of a full license. ESU also doesn’t include technical support. It’s best used as a bridge for the handful of systems you truly can’t move in time.
How Emerge Can Help
Server end-of-support projects tend to look simple until you’re in the middle of one. Our infrastructure and cloud teams handle the pieces that usually slow things down: finding every affected system, sorting out application dependencies, sizing new hardware or Azure environments, and planning cutovers that don’t disrupt the business.
If your IT team is already stretched, we can take the whole project or work alongside your staff on the parts where an extra set of hands helps most. And for systems that need ESU as a bridge, we can help set up the enrollment and the extra protections around them.
