Provision Technologies
Support Contact

Windows Server 2016 End of Support: What to Do Before January 2027

IT Infrastructure22 Nov 20266 min readChandan Munshi

The Windows Server 2016 end of support date is 12 January 2027. That is when extended support finishes, and the January 2027 security update is the last one Microsoft will ship for it. Any flaw found after that stays open on your servers, unless you have paid for Extended Security Updates or moved them to a newer version.

If you still run file servers, domain controllers, ERP or accounting servers, or Hyper-V hosts on Windows Server 2016, you have about seven weeks to decide what happens to each one.

What Windows Server 2016 end of support changes

Nothing breaks overnight. Your servers will boot, share files and run applications on 13 January exactly as they did the day before. The change is on Microsoft's side. No more security patches, no bug fixes, and no technical support for that version. Over the following months your software vendors follow suit, and backup agents, antivirus and business applications start listing Windows Server 2016 as unsupported.

The same date takes out Hyper-V Server 2016, Windows Storage Server 2016 and WSUS on Windows Server 2016, so check your virtualisation hosts and your patch server as well. And if any of these machines run SQL Server 2016, the database already went out of support on 14 July 2026.

What happens if you leave them running

Every month Microsoft publishes fixes for newly found Windows flaws, and attackers study those fixes to find the same weakness in older code. From February 2027, Windows Server 2016 will share much of that code with supported versions and receive none of the fixes.

The timing matters in India. Cyble counted 1,034 organisations named as ransomware victims worldwide in August 2026, the worst month of the year so far, with manufacturing the most-hit sector and India the most targeted country in Asia-Pacific. Servers are what ransomware groups go after, because that is where the data and the admin credentials live.

Then there is the Digital Personal Data Protection Act. It requires anyone handling personal data to take reasonable security safeguards, and its main obligations become enforceable on 13 May 2027. Explaining to a customer, an auditor or the Data Protection Board why your servers were knowingly left unpatched is not a conversation you want.

Your five options

You will probably use more than one, decided server by server.

1. Upgrade in place to Windows Server 2025

Microsoft supports a direct in-place upgrade from 2016 to 2025 using the Windows Server 2025 installation media. Roles, settings and data stay where they are, and Windows Server 2025 is supported until November 2034.

This works well for stable member servers on hardware that still has a few years left. Don't use it for domain controllers (Microsoft recommends building new ones), Windows Storage Server editions (there is no in-place path) or failover clusters, which can only move one version at a time.

2. Build new servers and migrate

Install Windows Server 2025 on new hardware or new virtual machines and move the roles and applications across. It takes longer than an in-place upgrade but gives you a clean system, and it is the right route for domain controllers, ageing hardware and servers that have collected a decade of tweaks. Get hardware quotes early. Server memory and storage prices rose sharply through 2026, and lead times stretch over the holidays.

3. Move the workload to Azure

Windows Server 2016 virtual machines running in Azure get Extended Security Updates at no extra charge. That buys time to modernise without a hardware purchase. It suits servers you were planning to replace anyway, and application servers that don't depend on low latency to on-site equipment.

4. Buy Extended Security Updates for the servers that can't move yet

For servers that must stay on-premises past 12 January, Microsoft sells Extended Security Updates through Azure Arc for up to three years, ending January 2030. You get critical and important security fixes only. There are no new features and no general bug fixes, and it is a paid subscription. Use it for named servers with a dated exit plan.

5. Switch it off

Almost every end-of-support project turns up servers nobody uses any more, and lightly loaded ones that can be merged. Retiring them costs nothing.

A seven-week plan to 12 January

  1. Week 1, inventory. Pull the list from Active Directory rather than from memory: Get-ADComputer -Filter 'OperatingSystem -like "*Server 2016*"' -Properties OperatingSystem | Select Name, OperatingSystem. Then walk the server room. The machine that holds up projects is usually one nobody listed, such as a workgroup box running a licence dongle, or a CCTV recorder on an embedded 2016 build. Record each server's roles, applications, owner and hardware age.
  2. Week 2, decide. Pick one of the five options for every server. Ask your application vendors in writing whether they support Windows Server 2025.
  3. Week 2, licences and hardware. Windows Server 2025 is licensed per core, and your existing client access licences (CALs) don't cover it if they are for an older version. Order now.
  4. Week 3, test. Upgrade a copy of each critical server first, then check the application, the backup agent and the endpoint security tool on it.
  5. Weeks 4 to 6, upgrade and migrate. Domain controllers and infrastructure servers first, application servers after. Take a backup before every change and confirm it restores.
  6. Week 6, enrol the stragglers. Connect any server that won't be finished in time to Azure Arc and enrol it in ESU before 12 January, so it never misses a month of patches.
  7. Week 7, check and record. Every server should now be on a supported version or covered by ESU, with an exit date written down for the ESU ones.

Most businesses freeze infrastructure changes for the last fortnight of December, so the real working window is closer to five weeks.

Mistakes we see most often

  • Upgrading domain controllers in place. Build new 2025 domain controllers, transfer the roles, then demote the old ones.
  • Upgrading without testing a restore first. Restore at least one file and one full server image before you touch anything. Our backup and disaster recovery work always starts with this check.
  • Upgrading the virtual machines but leaving the Hyper-V Server 2016 host underneath them unsupported.
  • Buying ESU with no end date in mind. You pay for every year, and coverage stops in January 2030 whatever happens.
  • Forgetting the database. A 2016 server running SQL Server 2016 needs both upgraded.

Frequently asked questions

Should we upgrade to Windows Server 2022 or 2025?

Go to 2025 unless an application only supports 2022. Windows Server 2022 left mainstream support in October 2026 and its extended support ends in 2031. Windows Server 2025 is supported until 2034.

How long can we buy Extended Security Updates for Windows Server 2016?

Up to three years, until January 2030, through Azure Arc for on-premises servers. Servers running as Azure virtual machines receive them at no extra charge.

Is an in-place upgrade from 2016 straight to 2025 safe?

Microsoft supports it for most standalone servers, and it usually goes smoothly on healthy systems. Take and test a backup first, and use migration instead for domain controllers, clusters and Storage Server editions.

Getting it done before January

Provision Technologies plans and carries out Windows Server upgrades for businesses across India. That covers in-place upgrades, new server and storage builds, domain controller migrations, moves to Azure or private cloud on Hyper-V and Proxmox, and ESU enrolment for servers that need more time. If you'd rather not face the same deadline again with Windows Server 2019, our managed IT services keep servers patched and on supported versions as routine work.

We work on-site in Kolkata and remotely everywhere else in India. Tell us how many Windows Server 2016 machines you run and what they do, and we'll reply within one business day.

Talk to our engineers or email sales@provisiontech.in.

Sources: Microsoft lifecycle documentation on products ending support in 2027, Microsoft's guide to Extended Security Updates enabled by Azure Arc, Microsoft's Windows Server upgrade overview, and Cyble Research and Intelligence Labs ransomware data for August 2026. Dates as published by Microsoft in November 2026.

PT
Chandan Munshi

Written by the engineers who design, deploy and run security and infrastructure for Provision Technologies clients.