News and insights

Windows Server 2016 reaches end of support on 12 January 2027

Microsoft will stop supporting Windows Server 2016 on 12 January 2027. The January 2027 security update will be the last one for this version. Servers still running it after that date get no more security fixes unless the organisation pays for extended updates.

Ten weeks is not long to upgrade or replace a server, especially one that runs an older business application. Here is what is changing and how to plan for it.

What’s changing

Windows Server 2016 was released in October 2016. Its mainstream support ended in January 2022, and its extended support ends on 12 January 2027. Microsoft confirmed the date in a blog post in February 2026, and again in a 90-day reminder to administrators on 14 October 2026.

The change covers every edition: Datacenter, Essentials, MultiPoint Premium and Standard. Containers released with Windows Server 2016 follow the same dates. Support for features specific to the Essentials edition, including Remote Web Access, ends on the same day.

After end of support, Microsoft says customers no longer receive technical assistance, software updates or security fixes. The server keeps working, but any flaw found after January stays unfixed.

Extended Security Updates. Organisations that need more time can buy Extended Security Updates (ESU). Microsoft’s reminder says these are available for the Standard and Datacenter editions only. The Register and Help Net Security report that ESU can be bought for up to three years. Microsoft’s blog says the updates are delivered through Azure Arc. ESU covers security updates only, not new features or technical support. When those articles were published, Microsoft had not announced a price for Windows Server 2016.

Where to move. Microsoft recommends upgrading to Windows Server 2025, or moving the workload to Azure. A free 180-day evaluation of Windows Server 2025 is available. According to BleepingComputer, Windows Server 2025 has extended support until 14 November 2034.

What it means for you

  • Find every server. Include virtual machines, servers in the cloud, and servers your suppliers run or host for you.
  • Decide for each one. Upgrade it, replace it, move the workload, retire it, or keep it for now with ESU.
  • Check what the server runs. Older applications may not support a newer version of Windows Server. Ask the application’s vendor early.
  • Budget for ESU if you need it. The Register reports that the cost will depend on your licensing agreement.
  • Plan around January. Allow time for testing and change approval before 12 January 2027.

How RiskWitness helps

End of support is a known date with a clear set of decisions. An information security risk register keeps those decisions in one place. This is how it looks in RiskWitness.

Find your servers. Search your asset register for servers running Windows Server 2016. Each asset shows its owner, where it’s kept or hosted, and the risks, controls and suppliers linked to it.

Record the risk. Add a risk such as “Servers running an unsupported operating system can’t be fixed when a new flaw is found”. Score it before and after your controls, and link the affected assets.

Link the controls that reduce it. For example, patch management, network separation for older systems, or a paid ESU subscription. Record how effective each control is, and test them.

Give each upgrade an owner and a date. Add an action for each server to upgrade, replace or retire, with a due date before January. Overdue actions show on the dashboard until they’re done.

Ask your suppliers. For suppliers that host servers or run systems for you, record what you asked and what they told you. Keep their answer as assurance evidence on their record.

Record what you’ll keep running. Some servers may stay on Windows Server 2016 for a while, with or without ESU. Record that as a risk acceptance, with a reason and an expiry date, so it comes back for review. If it’s outside your tolerance, a named approver has to sign it off.

Report on progress. Share a PDF report or slide deck with your board or risk committee. Record the committee’s decisions in its meeting minutes.

Every step is kept in a history that shows who did what, when, and the old and new values. Nobody can edit or delete it. When the board, an auditor, a customer or a regulator asks how you handled the end of support, the answer is already written down.

Sources