Windows Server 2016 support ends January 12, 2027. Here’s what to do now.

Every version of Windows Server has a published end date. When it arrives, Microsoft stops releasing security updates for that version. The server keeps turning on and your files are still there — which is exactly why this deadline is easy to ignore until something goes wrong.

What “end of support” actually means

Microsoft supports each server release in two phases. Mainstream support includes new features and fixes; for Windows Server 2016 that phase ended on January 11, 2022. Extended support covers security updates only, and it ends on January 12, 2027.

After that date, newly discovered vulnerabilities in Windows Server 2016 will not get free patches. Attackers know this. Unpatched, internet-reachable systems are some of the easiest targets there are.

Why it matters for a small business

• Security risk grows every month. Each new flaw that isn’t fixed stays open on your network permanently.
• Cyber insurance applications ask. Many insurers ask whether you run unsupported operating systems. A “yes” can affect your coverage or premium — and a wrong answer can affect a claim.
• Compliance reviews flag it. If you handle patient records or other regulated data, an unsupported server is the kind of finding a HIPAA security risk analysis is designed to catch.
• Software vendors move on. Line-of-business and practice-management software publishers eventually stop supporting old server versions, too.

How to check what you’re running

You don’t need to be technical. On the server itself, try either of these:

1. Press Windows + R, type winver and press Enter. The window that opens names the version.
2. Or open Server Manager and select Local Server. The operating system is listed on the right.

If you’re comfortable with PowerShell, this one line returns the exact edition:

(Get-CimInstance Win32_OperatingSystem).Caption

Check every server, including the one in the closet nobody touches. Those are often the oldest.

Your real options

1. Migrate to a current Windows Server release

For most small offices this is the right answer: new hardware, a current supported version, and your roles moved over with a written plan. We generally recommend running the new server as virtual machines. It costs little extra now, and it turns the next hardware refresh into a far simpler move.

2. Move some workloads to the cloud

File shares, email and some line-of-business apps may fit better in Microsoft 365 or a hosted service. It depends on your software and your internet connection. Not everything should move — but some things can, and that can shrink the server you need.

3. Buy time with paid Extended Security Updates

Microsoft has offered paid Extended Security Updates for some past server versions. Availability, eligibility and pricing vary, so confirm the current terms before planning around them. Treat them as a short bridge to a migration, not a destination.

4. Do nothing

Not an option we can recommend. If you choose it anyway, we’ll document that decision in writing with you, so everyone is clear on the risk being accepted.

A timeline that beats the deadline

1. Inventory now. List every server, what it runs, and who depends on it.
2. Call your software vendor. Confirm which server versions your critical applications support. This is the step most often left late, and it can stall everything else.
3. Write the plan. Hardware, licensing, migration steps, a rollback path and a cutover window that avoids your busy days.
4. Prove your backup. Run a test restore before touching anything. A backup you haven’t restored is a hope, not a backup.
5. Migrate, test, then retire. Move users in a pilot group first, then cut over and securely wipe the old drives.

Hardware lead times and vendor scheduling vary, so the safest time to start is now — not the week before January 12.

The bottom line

January 12, 2027 is fixed. You decide whether it arrives as a planned project or an emergency. If you’re not sure what you’re running, book a free IT review — we’ll check your servers and give you a written summary of where you stand, yours to keep either way.

This article is general information, not legal, compliance or insurance advice. Confirm dates and terms for your specific products on Microsoft’s official lifecycle pages.