Windows Server 2016 End of Support: What Happens After January 12, 2027

Published: October 22, 2026 | Updated: October 22, 2026

Last reviewed: October 2026. Microsoft can change prerequisites and Extended Security Update guidance, so confirm current requirements before changing a production environment.

Windows Server 2016 end of support arrives on January 12, 2027, but your servers will not power down that morning. End of support affects Microsoft’s servicing commitment rather than switching off the software: after that date, Microsoft stops releasing free security updates, non-security fixes and assisted support for the operating system.

That leaves the questions administrators actually ask. Will a 2016 domain controller still sign people in on January 13? Can you buy more time with Extended Security Updates? Can you jump straight from 2016 to Windows Server 2025, or must you stop at 2019 or 2022 first? And what happens to your Remote Desktop licenses?

This guide explains the Windows Server 2016 end of support date, what actually stops, the paid ESU option Microsoft has announced, the supported upgrade paths and a sensible plan for each type of server, with practical checks and beginner-friendly explanations along the way.

Windows Server 2016 End of Support: Quick Answer

Here is the current position as of October 2026:

• Extended support ends on January 12, 2027. That is the final day of Windows Server 2016 extended support.
• Mainstream support already ended on January 11, 2022, so 2016 has received security-only servicing for almost five years.
• After the Windows Server 2016 end of support date, Microsoft stops free security updates, non-security fixes and support cases for the product.
• Your servers keep running, booting and serving users. Activation is not revoked.
• Microsoft has announced paid Extended Security Updates (ESU) for Windows Server 2016, delivered through Azure Arc. Windows Server 2016 ESU is a bridge, not a permanent fix.
• Microsoft supports in-place upgrades from Windows Server 2016 directly to 2019, 2022 or 2025 on nonclustered servers.
• Windows Server 2025 is supported until November 14, 2034, the longest runway of any current release.

In other words, the Windows Server 2016 end of support date is a security and compliance deadline, not an off switch.

Is Windows Server 2016 Still Supported?

Yes, but only until the Windows Server 2016 end of support date of January 12, 2027. Windows Server 2016 follows Microsoft’s Fixed Lifecycle Policy, which means it received a fixed period of mainstream support followed by a fixed period of extended support, with dates published at launch.

Here is what each phase means in one line:

• Mainstream support: security updates, bug fixes and occasional feature changes.
• Extended support: security updates at no cost; non-security fixes and support are limited.
• End of support: no new updates of any kind and no Microsoft support for the product.

Microsoft’s official Windows Server 2016 lifecycle page lists these dates and covers the Datacenter, Standard, Essentials and MultiPoint Premium editions.

Windows Server End-of-Support Dates by Version

It helps to see the Windows Server 2016 end of support date next to the versions you might move to:

If you are planning a move today, Windows Server 2025 gives you roughly eight years of support, while Windows Server 2019 gives you just over two.

Windows Server 2022 only moved into extended support this month, so it remains a reasonable target when an application vendor has not yet certified 2025.

Which Windows Server 2016 Products Reach End of Support on January 12, 2027?

All editions share the same Windows Server 2016 end of support date. Microsoft’s 2027 end-of-support list also includes several closely related products on the same day:

• Windows Server 2016 Datacenter, Standard and Essentials
• Hyper-V Server 2016, the free hypervisor-only release
• Windows Storage Server 2016
• Windows Server Update Services (WSUS) for Windows Server 2016
• IIS 10 on Windows Server 2016
• Windows Defender for Windows Server 2016
• Microsoft .NET Framework 4.6.2

One client product shares the date too: Windows 10 Enterprise LTSC 2021, the long-term servicing release used on kiosks and specialized devices. If you also manage Windows 10 PCs, our guide to the Windows 10 ESU end date covers the desktop side.

Applications that run on the server, such as SQL Server or line-of-business software, follow their own lifecycles. A supported application on an unsupported operating system is still an unsupported stack.

Does Windows Server 2016 End of Support Mean Your Server Will Stop Working?

Usually not. January 13, 2027 will feel remarkably like January 12, apart from Windows Update going very quiet.

Here is what stops after Windows Server 2016 end of support:

• Monthly security updates for newly discovered vulnerabilities
• Non-security fixes and reliability updates
• Microsoft technical support cases for Windows Server 2016
• Updated online technical content for the product
• Vendor certification, as software makers gradually drop 2016 from their supported lists

Here is what continues:

• The operating system boots and runs
• Installed roles such as Active Directory, file services, IIS and Hyper-V keep working
• Existing activation stays valid
• Previously released updates remain installable

The real risk after Windows Server 2016 end of life builds over time. Every unpatched vulnerability published after January 2027 stays open, and many security frameworks, auditors and cyber insurers expect production servers to run supported, patched operating systems.

IMPORTANT: Internet-facing servers, domain controllers and Remote Desktop hosts carry the most risk after the Windows Server 2016 end of support date. Prioritize those first.

What Are Windows Server 2016 Extended Security Updates?

Extended Security Updates (ESU) are a paid program that continues delivering security updates for a product after its end of support. Microsoft announced Windows Server 2016 ESU in February 2026, well ahead of Windows Server 2016 end of support.

Microsoft states that ESU for Windows Server 2016 is delivered through Azure Arc, its service for managing on-premises and multicloud servers from the Azure portal, with flexible subscription billing. Microsoft describes it as an option to keep running Windows Server 2016 so business-critical applications are not disrupted while you upgrade or migrate.

A few practical points are worth keeping in mind:

• ESU is a bridge, not a destination. It buys time; it does not add features.
• ESU is enrolled and billed through Microsoft’s Azure services, not activated with a new Windows Server product key.
• Coverage terms, eligibility and pricing are set by Microsoft and can change, so check Microsoft’s ESU documentation before budgeting.

Microsoft’s Windows Server 2016 end of support planning announcement explains the ESU option and names Windows Server 2025 or Azure as the recommended destinations.

Windows Server 2016 ESU makes the most sense for a small number of servers running an application that genuinely cannot move yet. Paying to extend every server is usually a sign the upgrade project needs a start date rather than a budget line.

Can You Upgrade Windows Server 2016 Directly to Windows Server 2025?

Yes, for nonclustered servers, which makes it simpler to upgrade Windows Server 2016 to 2025 before the deadline. Microsoft states that, starting with Windows Server 2025, nonclustered systems can upgrade up to four versions at a time, so Windows Server 2016 can move straight to 2025 without stopping at 2019 or 2022.

Microsoft also lists several restrictions that catch people out:

• The edition is kept by default: Standard upgrades to Standard and Datacenter to Datacenter
• Standard can move up to Datacenter during an upgrade, but Datacenter cannot move down to Standard
• You cannot switch between Server Core and Desktop Experience during an in-place upgrade
• Language changes and 32-bit to 64-bit changes are not supported
• NIC Teaming must be disabled before upgrading
• Each Windows Server upgrade requires a separate license, unlike Windows client upgrades

Microsoft’s Windows Server upgrade and migration overview keeps the full support matrix current.

In-Place Upgrade vs Migration: Which Fits Your Server?

An in-place upgrade replaces the operating system on the same machine and keeps roles, settings and data. A migration builds a fresh server and moves the workload across. They solve the same Windows Server 2016 end of support problem in very different ways.

A server that has run quietly in a closet since 2016 has usually collected a few undocumented habits. A clean build tends to leave those behind, which is why many administrators prefer migration for domain controllers and heavily customized servers.

If you are rebuilding on an older release for vendor reasons, Bcdkey’s guides to install and activate Windows Server 2022 Standard and install and activate Windows Server 2019 Standard walk through each setup.

Windows Server 2025 System Requirements

Before you upgrade Windows Server 2016 to 2025, confirm that the hardware or virtual machine can run it. Microsoft lists these minimums for Windows Server 2025:

These are minimum specifications, not a promise of ideal performance. Real servers need memory and storage sized to their roles, and the SSE4.2 and POPCNT requirements are new compared with Windows Server 2016, so check older hosts with Microsoft’s Coreinfo tool rather than assuming. The full list is on Microsoft’s Windows Server hardware requirements page.

How to Check Your Windows Server Version

Before planning for Windows Server 2016 end of support, confirm what each server is actually running:

1. Press Windows + R, type winver and press Enter. Windows Server 2016 shows Version 1607 with an OS build beginning 14393.
2. Open PowerShell as administrator for a fuller picture.
3. Run the command below to see the product name, version and build.
4. Run DISM /Online /Get-CurrentEdition to confirm Standard or Datacenter.
5. Run slmgr /dlv to see the license channel and activation status.
6. Record the results for every server in a simple inventory.

Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber

Note whether each server is physical or virtual, which roles it hosts and which applications depend on it. That inventory becomes your upgrade plan.

How to Plan Your Upgrade Before Windows Server 2016 End of Support

With roughly three months of Windows Server 2016 extended support left, a phased plan is more realistic than a single weekend of heroics. Ten-year-old servers rarely enjoy surprises.

1. Inventory every Windows Server 2016 machine, including VMs and Hyper-V hosts.
2. Rank servers by risk: internet-facing, domain controllers, RDS hosts, then internal member servers.
3. Check application support for Windows Server 2025 or 2022 with each vendor.
4. Confirm hardware compatibility, especially CPU features and storage controllers.
5. Take full backups and test that they restore.
6. Snapshot or clone virtual machines before any upgrade.
7. Upgrade or migrate a pilot group of low-risk servers first.
8. Validate the pilot for at least a week of normal use.
9. Roll out the remaining servers in planned maintenance windows.
10. Decide on Windows Server 2016 ESU only for servers that cannot move before January 12, 2027.

Test these components first in your pilot:

• Line-of-business applications and their database connections
• Backup agents and antivirus or endpoint agents
• Printing, scanning and mapped drives
• Group Policy processing and logon scripts
• Remote Desktop sessions and RemoteApp programs
• Monitoring and management tools

IMPORTANT: Domain controllers, clusters and production database servers are business-critical. If you have not upgraded these before, involve an experienced administrator and keep the old server available until the new one is fully validated.

Should You Stay on Windows Server 2016 or Upgrade to Windows Server 2025?

Not every server has to move on the same day, but every server needs a decision before Windows Server 2016 end of support.

Stay with Windows Server 2016 for now, briefly, when:

• A critical application vendor has not certified a newer release
• The server is isolated from the internet and scheduled for retirement
• You have enrolled it in Extended Security Updates
• Replacement hardware is already ordered

Consider Windows Server 2025 when:

• You want the longest support runway, through November 14, 2034
• Your hardware meets the newer CPU requirements
• You are replacing domain controllers or building new hosts
• You want to avoid doing this project again in two or three years

Consider Windows Server 2022 when:

• An application is certified for 2022 but not yet for 2025
• You need to match an existing 2022 environment

Windows Server 2019 is still a supported target, but with extended support ending January 9, 2029, it is hard to recommend for a new deployment today.

Which Windows Server Edition Do You Need?

Version and edition are separate decisions. The version (2016, 2022, 2025) sets the features and support dates. The edition (Standard or Datacenter) sets your virtualization rights and some advanced features.

Windows Server Standard covers two virtual machines, or operating system environments, when all physical cores on the host are licensed. Datacenter allows unlimited virtual machines on a fully licensed host and adds features such as Storage Spaces Direct.

You do not need Datacenter simply because a server is important. A single physical file server, application server or domain controller is normally a Standard workload.

For most small businesses replacing a server ahead of Windows Server 2016 end of support, Windows Server 2025 Standard is the practical choice. Heavily virtualized hosts are better matched with Windows Server 2025 Datacenter. If an application requires the previous release, Windows Server 2022 Standard is the alternative. Each key activates only its own version and edition, and Windows Server is licensed per physical core, so confirm how many core licenses your hardware needs. You can compare every release in the Windows Server category.

Organizations replacing many servers at once can ask about volume pricing through the Bcdkey B2B wholesale program.

What Happens to Your Remote Desktop CALs?

A Remote Desktop Services client access license (RDS CAL) lets a user or device connect to a Remote Desktop session host. Under Microsoft’s RDS licensing rules, the CAL version must match or be newer than the Windows Server version of the session host.

That means Windows Server 2016 RDS CALs will not cover a Windows Server 2025 session host. You will need User CALs for Windows Server 2025 RDS if each person connects from several devices, or Device CALs for Windows Server 2025 RDS for shared PCs used by shifts. Newer CALs also cover older session hosts, which helps during a gradual migration.

When you upgrade Windows Server 2016 to 2025 on an RDS deployment, upgrade the RD Licensing server first, then install the 2025 CALs. Browse every CAL version in the RDS category.

How to Activate a New Windows Server

Activation works the same way it did in 2016: enter the product key in Settings or with slmgr /ipk, then activate online. If an isolated server cannot reach Microsoft’s activation servers, phone activation is the fallback.

Need to activate by phone? Use the Bcdkey Get Confirmation ID tool. For a closer look at older systems you are keeping a little longer, read our guide to activate Windows Server 2016 Standard.

Recommended Action by Installed Version

Use this table to decide what each server needs before Windows Server 2016 end of support:

Final Thoughts

Windows Server 2016 end of support is not really about a server suddenly failing. It is about choosing when you stop accepting unpatched risk, rather than letting a calendar date make that choice for you.

The key Windows Server 2016 end of support date is January 12, 2027. After it, Windows Server 2016 keeps running, but new vulnerabilities stay open unless the server is enrolled in Microsoft’s paid ESU program.

For most organizations, the simplest path is a move to Windows Server 2025, either in place for straightforward servers or by migration for domain controllers and older hardware. Teams with an application that cannot move yet can use Windows Server 2016 ESU or Windows Server 2022 as a bridge.

Start this week with an inventory: list every 2016 server, its role and its owner. A plan written in October is far cheaper than one improvised in January. When you are ready to choose an edition, compare the Windows Server range on Bcdkey.

FAQ About Windows Server 2016 End of Support: What Happens After January 12, 2027

When is Windows Server 2016 end of support?

January 12, 2027. That is when Windows Server 2016 extended support ends; mainstream support already ended on January 11, 2022.

Will Windows Server 2016 stop working after end of support?

No. The server keeps running and stays activated, but it no longer receives security updates, fixes or Microsoft support unless it is enrolled in Extended Security Updates.

Is there an ESU program for Windows Server 2016?

Yes. Microsoft announced paid Extended Security Updates for Windows Server 2016 in February 2026, delivered through Azure Arc with subscription billing.

Can I upgrade Windows Server 2016 directly to Windows Server 2025?

Yes. Microsoft supports a direct in-place upgrade from Windows Server 2016 to 2025 on nonclustered servers; clusters using a rolling upgrade must move one version at a time.

Do I need a new license to upgrade Windows Server 2016?

Yes. Microsoft states that each Windows Server upgrade requires a separate license, and the key must match the new version and edition.

Do my Windows Server 2016 RDS CALs work with Windows Server 2025?

No. RDS CALs must be the same version as, or newer than, the session host, so a Windows Server 2025 RDS host needs 2025 RDS CALs.

Is Hyper-V Server 2016 affected by Windows Server 2016 end of support?

Yes. Hyper-V Server 2016 reaches end of support on the same date, January 12, 2027, so hosts running it need a new plan too.

Is Windows Server 2016 end of life the same as end of support?

Yes. Windows Server 2016 end of life and Windows Server 2016 end of support describe the same date, January 12, 2027, when Microsoft stops all updates and support for the product.

Is Windows Server 2019 still supported?

Yes. Windows Server 2019 is in extended support until January 9, 2029, receiving security updates but no new features.

Should I choose Windows Server 2022 or 2025 to replace 2016?

Normally, Windows Server 2025, because it is supported until November 14, 2034. Choose 2022 only when an application or existing environment specifically requires it.