Windows Server 2016 Ends 12 January 2027: What Indian Businesses Must Do Now
Short answer: Microsoft will stop supporting Windows Server 2016 on 12 January 2027. Your servers will not switch off that day, but after it they stop receiving security updates unless you pay for Extended Security Updates (ESU). You have four realistic options: buy ESU through Azure Arc, upgrade the operating system in place (a direct 2016 to 2025 upgrade is supported), move the workload to newer hardware, or consolidate it into virtual machines on a newer host. About 12 weeks remain as of 16 October 2026, which is enough time if you start with an inventory this week.
Key takeaways
- Microsoft states that extended support for Windows Server 2016 ends on 12 January 2027. Mainstream support already ended in January 2022.
- After that date there are no free security updates. ESU covers Critical and Important security updates for up to three years, through 2030, and does not add features or non-security fixes.
- Windows Server 2016 ESU is delivered through Azure Arc, billing begins on 13 January 2027, and Microsoft says buying it needs Software Assurance or an equivalent subscription.
- Microsoft lists in-place upgrade paths from 2016 to 2019, 2022 and 2025. Each upgrade needs its own licence and your hardware has to be supported by the server maker for the new version.
- Check the vendor's support list for your exact model before you upgrade or buy: older generations are not automatically certified for the newest Windows Server.
- Dates, prices and support lists change. This guide was last verified on 16 October 2026.
This guide is for IT managers, sysadmins, founders and procurement teams in India who run Windows Server 2016 on physical servers or virtual machines. It explains what the end date really means, how to find every affected server, how the four options compare, what to check on the hardware, and a 12-week plan you can adapt. Nothing here is legal or licensing advice: confirm your final licence position with an authorised Microsoft reseller.
What does “end of extended support” actually mean?
Windows Server 2016 follows Microsoft's Fixed Lifecycle Policy. Mainstream support, which included feature fixes, ended in January 2022. Extended support, which includes security updates only, ends on 12 January 2027. Nothing breaks on that day: the servers keep running and applications keep working. What changes is that Microsoft stops publishing security fixes for the operating system, so every vulnerability found afterwards stays open on your servers.
That is a business risk, not just a technical one. An unpatched server that holds accounting data, customer records or an ERP database is exactly what an attacker looks for. The Digital Personal Data Protection Act, 2023 expects a data fiduciary to take reasonable security safeguards to prevent a personal data breach, and running an unsupported operating system is hard to defend as a safeguard. Ask your auditor and your cyber-insurance provider how they treat unsupported software before the date, not after.
Software that runs on top has its own dates. For example, Microsoft lists extended support for SQL Server 2016 as having ended in July 2026, with paid ESU after that. If a 2016 server also runs SQL Server 2016, plan both upgrades together.
Step 1: Find every Windows Server 2016 machine
You cannot plan what you have not counted. Servers that hide in a corner of the office, test machines and old virtual machines are the usual surprises.
- On one server: press Windows key + R, run
winver, or in PowerShell run(Get-CimInstance Win32_OperatingSystem).Caption. Windows Server 2016 reports build 14393. - Across a domain: in PowerShell with the Active Directory module, run
Get-ADComputer -Filter {OperatingSystem -like "*2016*"} -Properties OperatingSystemto list every domain-joined machine that reports Windows Server 2016. - Virtual machines: list guests on each Hyper-V, VMware or Proxmox host, because guest operating systems are easy to forget. See our VMware and Proxmox server configuration guide.
- Write down for each one: its role, the application it runs, the hardware model and age, the licence type, the owner and the backup status.
Step 2: Compare the four options
| Option | What it means | Good when | Watch out for |
|---|---|---|---|
| A. Stay on 2016 with ESU | Keep the server as is and receive paid security updates delivered through Azure Arc | An application cannot move yet and you need time | Critical and Important security fixes only, for up to three years (through 2030); billing starts 13 January 2027; the server must be connected to Azure Arc (agent version 1.62 or higher); Microsoft says purchase requires Software Assurance or an equivalent subscription |
| B. Upgrade in place | Install a newer Windows Server over the existing one, keeping roles, settings and data | The hardware is supported by its maker for the new version and the roles support in-place upgrade | Needs a new licence; back up first and rehearse on a copy; some configurations are restricted (see below) |
| C. Move to newer hardware | Build a new server on a current OS and migrate roles and data to it, either new or refurbished | The old hardware is not supported for the new version, or it is simply old and slow | More work than an in-place upgrade; plan data migration, cutover and a rollback |
| D. Virtualise or rent as a bridge | Run the legacy workload in a virtual machine on a newer host, or rent a server with a current Windows Server while you migrate | You want to leave old hardware quickly or need a temporary landing zone | A virtual machine running Windows Server 2016 still needs security updates after the date; renting delays the work, it does not remove it |
Microsoft itself recommends the ESU period as a chance to upgrade to Windows Server 2025 or consider migrating to Azure. ESU is best treated as a safety net for the few workloads that cannot move in time, not as a long-term plan.
How an in-place upgrade works, and its limits
Microsoft's upgrade documentation lists these in-place paths when you upgrade from installation media: Windows Server 2016 can upgrade to 2019, 2022 or 2025, and Windows Server 2025 itself can upgrade nonclustered systems up to four versions at a time. A few rules matter for planning:
- Each Windows Server upgrade needs its own licence for the target version.
- You cannot switch between Server Core and Server with Desktop Experience, or change the language, during an in-place upgrade.
- Servers booted from a VHD, and Windows Storage Server editions, are not supported for in-place upgrade.
- If the server uses NIC Teaming, disable it before the upgrade and re-enable it afterwards.
- Domain controllers and some roles have their own procedures; check Microsoft's role and feature guidance before you touch them.
- Always back up first. Our backup and disaster recovery guide explains a backup you can actually restore.
An in-place upgrade is the fastest path on the same hardware, but only if that hardware is supported for the new version. That is the next check.
Hardware readiness: will your server run the new version?
Microsoft's published minimums for Windows Server 2025 include a 1.4 GHz 64-bit processor with NX and DEP, support for the CMPXCHG16b, LAHF/SAHF and PrefetchW instructions, second-level address translation (EPT or NPT), and, new for 2025, the SSE4.2 and POPCNT instructions. It also lists 2 GB of RAM as the minimum (4 GB recommended with Desktop Experience), 32 GB of disk as an absolute minimum, a 1 Gbps network adapter, and ECC-type memory for physical host deployments. UEFI and TPM are needed only for certain features such as Secure Boot and BitLocker. You can check a processor with Microsoft's free Coreinfo tool. Microsoft adds that these are minimums and that you should test your own roles.
Minimums are only half the story. What matters in practice is whether the server's maker supports that model with that version of Windows Server, because the drivers, firmware and management tools come from the maker:
- Dell: publishes the supported operating systems per PowerEdge model through its Server Operating System Support page (Dell.com/ossupport) and each model's Supported Operating Systems page. Public information for some 14th generation models is mixed, so read the entry for your exact model.
- HPE: publishes a Windows Server Certification and Support matrix by ProLiant model and generation. Check your model's row for each Windows Server version.
- Lenovo, Cisco, Supermicro: each publishes its own compatibility list; use the official one.
Read the model and age from the label or the controller, as described in our server warranty and serial number guide, then look it up in the maker's list. Our Intel Xeon generations guide helps you place the processor in its generation. If a server is too old for the new version, option C is the answer, not a workaround.
Licensing basics before you spend
Windows Server is licensed per physical core, with a minimum number of core licences per processor and per server, plus Client Access Licences (CALs) for the users or devices that connect, and Remote Desktop Services CALs for staff who work in remote sessions. These are Microsoft's published terms and they are summarised, with worked counting examples, in ProStation's Windows Server licensing guide. If you are not sure what licence your 2016 servers carry, find the invoice or the Microsoft licensing account first, because it decides whether ESU is even available to you.
If a seller quotes a server with Windows Server “installed”, ask for the licence to be named and confirmed in writing. Installed and licensed are not the same thing. Serverwale's Windows Server rental page states that the hardware comes with Windows Server pre-installed, licensing included and a choice of edition and version; confirm the exact terms for your requirement.
Where refurbished hardware fits
Many Indian businesses bought their current servers around the time Windows Server 2016 launched. A refurbished server of a later generation can be a sensible way to retire an old machine without paying new-server prices, provided it is on the maker's support list for the Windows Server version you will install. Compare options in our refurbished vs new TCO guide, the Dell R740 vs R640 comparison and the Dell vs HP servers page, and see the refurbished server price index for how prices compare with new.
Whatever you buy, test it before you move production onto it (our post-delivery testing checklist shows how), read the warranty terms (Serverwale states a 1-year hardware warranty on its servers; extended cover is available at extra cost) and use the refurbished server buying checklist. For budget planning, GST on second-hand hardware has its own rules; see our GST and import duty guide.
If the old server is leaving, plan its retirement too: the server decommissioning checklist and data wiping and e-waste guide cover wiping data properly, and the trade-in value guide and exchange and upgrade page show how to recover some value. Our general explainer on server end-of-life vs end-of-support covers the hardware side of the same problem.
A 12-week plan you can adapt
From 16 October 2026 to 12 January 2027 is 88 days, or about 12 weeks. This is a suggested plan, not a Microsoft schedule; shrink or stretch it to your size.
| Weeks | What to do | Output |
|---|---|---|
| 1 to 2 | Inventory every Windows Server 2016 machine and its role, application, hardware, licence and backup status | One spreadsheet of every server |
| 3 to 4 | Decide per workload: upgrade in place, migrate, virtualise, retire, or ESU as a stopgap. Ask each application vendor which Windows Server versions it supports | A decision per server and a budget |
| 5 to 6 | Confirm hardware support lists, order hardware and licences, and set up the target servers | Target servers ready, licences confirmed |
| 7 to 8 | Test restores from backup, then rehearse the upgrade or migration on a copy | A tested runbook and rollback steps |
| 9 to 10 | Migrate the least critical servers first, then the critical ones in a planned window | Servers running on supported systems |
| 11 | Keep the old servers available for rollback; watch for problems | Confirmed stable |
| 12 | Decommission old servers, wipe data and update the asset list. Anything left on 2016 either gets ESU or is isolated and scheduled for removal | No unmanaged 2016 server after 12 January |
Power and cooling are easy to forget when you add a temporary second server; see our UPS sizing guide before the migration weekend.
Frequently asked questions
Will Windows Server 2016 stop working after January 2027?
No. The servers keep running and your applications keep working. What stops is Microsoft's security updates for the operating system after 12 January 2027, unless you buy Extended Security Updates. Running without security updates leaves every newly discovered vulnerability open.
Can I upgrade directly from Windows Server 2016 to 2025?
Yes. Microsoft's upgrade documentation lists an in-place upgrade from Windows Server 2016 to 2019, 2022 and 2025 when you use installation media. You need a licence for the new version, the hardware must be supported for it, and the roles on the server must support in-place upgrade. Back up first and test on a copy.
Is there Extended Security Updates support for Windows Server 2016, and what does it cost?
Yes. Microsoft delivers ESU for Windows Server 2016 through Azure Arc. It covers Critical and Important security updates for up to three years, through 2030, and billing begins on 13 January 2027. Microsoft says purchase requires Software Assurance or an equivalent subscription, or licensing through SPLA or a Server Subscription. We do not quote a price here because Microsoft sets it; check Microsoft's current pricing.
Which refurbished servers are safe to run Windows Server 2022 or 2025?
It depends on the exact model, not just its generation. Check the manufacturer's supported operating systems list for that model, for example Dell's Server Operating System Support page or HPE's Windows Server Certification and Support matrix, and confirm the processor meets Microsoft's requirements. Send us the model and we will help you read the vendor list before you buy.
What if my ERP or accounting software only supports an older Windows version?
Ask the software vendor which Windows Server versions it supports now, because many have updated. For instance, Tally lists Windows Server 2012 or above for TallyPrime Server; see the Tally server sizing guide. If something truly cannot move, ESU or strict network isolation of that one server buys time while you plan its replacement.
Can I move my licence to a new server?
It depends on how the licence was bought, for example with the server (OEM), through volume licensing or as a retail copy, because the transfer terms differ. Check your licence agreement or ask an authorised Microsoft reseller before you assume it moves with you, and confirm the licence for any replacement server in writing.
Plan your Windows Server 2016 exit with us
Not sure which of the four options fits each server? Send us the server model and a short note about what it runs, and our team will help you check it against the maker's support list and suggest a refresh path, free of charge. Call or WhatsApp +91-87962-44410, or contact us. You can also browse refurbished servers, the Dell server rental page for a temporary bridge, server AMC plans, enterprise solutions and the server store.
Sources: Microsoft Windows Server Team blog, “Extended Security Updates for Windows Server 2016” (25 February 2026, announcement); Microsoft Learn, Windows Server 2016 lifecycle, SQL Server 2016 lifecycle, Prepare to deliver Extended Security Updates through Azure Arc, Plan your Windows Server upgrade path and Hardware requirements for Windows Server; Dell, Microsoft Windows Server Operating System Support; HPE, Windows Server Certification and Support; Digital Personal Data Protection Act, 2023 (reasonable security safeguards); ProStation Systems, Windows Server licensing guide; Serverwale Windows Server rental page and policy and FAQ. Vendor pages, dates and prices change, so confirm on the vendor's site. Last verified 16 October 2026.