Zippy ⚡
Windows Server End of Support Microsoft Security Small Business IT

Windows Server 2016 End of Support Is 60 Days Away

⏰ 60-Day Warning

January 13, 2027 is the last day Windows Server 2016 receives security updates. After that date, any new vulnerabilities discovered will never be patched — unless you pay Microsoft for Extended Security Updates (ESU).

Microsoft issued another reminder this week: Windows Server 2016 hits end of extended support on January 13, 2027. That's roughly two months away. If your organization is still running Server 2016 — whether it's your file server, domain controller, application host, or anything else — now is the time to make a plan.

What "End of Support" Actually Means

It doesn't mean the server stops working on January 14th. Your data doesn't disappear, your applications don't break, and nothing catches fire. What stops is security patches.

Every month, Microsoft releases fixes for newly discovered vulnerabilities in Windows. After January 13, those fixes simply won't be made for Server 2016. The server keeps running, but it slowly becomes a bigger target as vulnerabilities pile up with no remediation path.

For a server sitting behind a firewall that never touches the internet, that risk is manageable. For a domain controller, a server with remote access enabled, or anything handling sensitive data, it's a real exposure you're carrying indefinitely.

What To Do

You've got a few options, and the right one depends on what that server is doing:

Microsoft offers a free 180-day trial of Windows Server 2025 through the Microsoft Evaluation Center if you want to test before committing.

Not Sure If You're Running It?

If you manage your own servers and want to check: on any Windows Server, open a command prompt and type winver — it'll tell you the OS version immediately. Or reach out to us and we'll check for you.

Running Server 2016 and not sure what your upgrade path looks like? Email us or call (614) 291-4357. We've done a lot of these migrations and can walk you through the options without the sales pitch.


Also in the News

November Windows Updates Caused Activation Errors — Microsoft Pushed an Emergency Fix

If any Windows machines in your organization started showing a 0x80041008 activation error after last week's Patch Tuesday updates, you're not alone. Microsoft confirmed the November security updates broke the Windows Software Licensing Management Tool (SLMGR) used by many organizations to automate activation.

The good news: Microsoft moved quickly. Emergency out-of-band updates were released on Friday to resolve the issue. The fixes are available for Windows 11 (23H2 via Windows Update), Windows 10, and Windows Server 2019/2022/2025 (via Microsoft Update Catalog). Already-activated devices that don't use SLMGR scripting were unaffected.

If you're seeing the error, check Windows Update or the Microsoft Update Catalog for the out-of-band KB for your version. November's Patch Tuesday also caused printing issues with complex documents — that fix is included in the same cumulative updates.

What Caused Last Week's Microsoft 365 Outage

Microsoft has released its preliminary post-incident report on the near-24-hour Microsoft 365 outage that disrupted Outlook, Exchange Online, Teams, and Copilot worldwide on November 12–13.

The root cause: a software bug quietly introduced back in July — more than three months before it caused any problems. The bug could overwhelm networking gateway servers under certain traffic conditions, but those conditions didn't occur until a Microsoft Teams failover on November 12 redirected traffic to the Exchange Online infrastructure. Combined with roughly 14% of gateway capacity already offline for an unrelated reason, the bug was triggered at scale. Within two hours, over 80% of gateway servers were unresponsive. Services cascaded down from there.

Recovery was difficult because restarting affected servers caused them to be re-overwhelmed by backed-up traffic. Microsoft engineers developed a targeted fix and gradually restored services — full recovery was confirmed by 11:10 AM ET on November 13.

Microsoft says it has since increased capacity, improved load testing (the bug wasn't caught because tests used less powerful hardware than production), and added safeguards to prevent similar cascading failures. A full post-incident review is expected.

← Back to Tech News