END OF SUPPORT · WINDOWS SERVER 2016

Security fixes end, except through paid Extended Security Updates

Jan. 122027the final monthly security update
  • SQL Server 2016 support ended July 14, 2026
  • Extended Security Updates: three years at most
  • Department of Labor best practices: software “kept up to date”
Sources: Microsoft Lifecycle pages; DOL Cybersecurity Program Best Practices (#11)

The short answer: Microsoft releases its final monthly security update for Windows Server 2016 on January 12, 2027; after that, a server still running it stays open to every newly found flaw unless your firm qualifies for paid Extended Security Updates, which Microsoft limits to three years. Use the weeks left to list every 2016 server and every SQL Server 2016 database (support for that ended July 14, 2026), then decide, server by server, whether to upgrade, replace, move to a hosted private cloud or pay for that short bridge.

“Upon retirement or end of support, there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates.” Source: Microsoft Lifecycle, Ending Support in 2027⁠ (opens in new tab)

What Ends on January 12, 2027

Extended support for every edition of Windows Server 2016⁠ (opens in new tab), including Essentials, ends that day. Microsoft says these servers “will receive a final monthly security update” on January 12; after that, there are no more security updates, bug fixes or technical support. Support also ends for the built-in Windows Defender antivirus, Windows Server Update Services (WSUS, Microsoft’s update tool) and the IIS 10 web server on Windows Server 2016.

For remote desktop servers, another deadline has already passed: Microsoft 365 Apps (Word, Excel, Outlook) lost support on Windows Server 2016⁠ (opens in new tab) on October 14, 2025. Security updates for them there continue only until October 10, 2028, and only on servers that download them straight from Microsoft.

Nothing shuts off on January 13. What changes is that every flaw found after January 12 stays open.

Why It Matters for a TPA

The Department of Labor (DOL) notes that plans “store and/or transfer participant personally identifiable data, which can make them tempting targets for cyber-criminals.” Its Cybersecurity Program Best Practices⁠ (opens in new tab), guidance rather than requirements, are “for use by recordkeepers and other service providers responsible for plan-related IT systems and data.” Practice 11, strong technical controls, lists “Hardware, software and firmware models and versions that are kept up to date” and “Routine patch management (preferably automated).” Practice 2 says a risk assessment should “Describe how the cybersecurity program will mitigate or accept the risks identified.”

In our view, a server that can’t be patched is hard to defend to a plan sponsor, an insurer or your own risk assessment without a written decision and a retirement date.

Database Servers: Check the SQL Server Version

If your plan administration or document and testing software keeps its data in Microsoft SQL Server, check that version too:

  • SQL Server 2016 lost support on July 14, 2026. Paid Extended Security Updates last up to three years but cover only flaws Microsoft rates Critical, and Microsoft’s own guidance⁠ (opens in new tab) says the option “can be costly.”
  • SQL Server 2017 loses support on October 12, 2027; SQL Server 2022 is supported until January 11, 2033.
  • Not every pairing is supported. Microsoft doesn’t support⁠ (opens in new tab) SQL Server 2016 on Windows Server 2022 or 2025, or SQL Server 2017 on Windows Server 2025.

Ask your software vendor in writing which Windows Server and SQL Server versions it supports.

Remote Desktop Servers: Licenses and Office Apps

If your staff sign in to a remote desktop server to run your software (Microsoft’s Remote Desktop Services, or RDS), keep three things in mind:

  • Licenses follow the version. Each person or device that connects needs an RDS client access license (CAL)⁠ (opens in new tab), and Windows Server 2016 CALs work only with 2016 servers. A 2025 remote desktop server needs 2025 CALs on a licensing server that also runs 2025.
  • Move them together. Microsoft supports upgrading⁠ (opens in new tab) remote desktop servers, but not a setup that mixes versions.
  • Office needs a current version. Microsoft supports Microsoft 365 Apps on Windows Server 2025; its support on 2016, 2019 and 2022 has ended.

Four Ways Forward

You can mix these, server by server. Microsoft supports upgrading⁠ (opens in new tab) Windows Server 2016 directly to 2019, 2022 or 2025.

Options for a server running Windows Server 2016
OptionGood fit whenWatch for
Upgrade in placeA simple server, such as a file server, on hardware under warrantyA backup first and a license for the new version. Microsoft doesn’t support it for print servers, which must be moved to a new server, and doesn’t recommend it for domain controllers, the servers that check every sign-in.
Migrate to a new serverDatabase, remote desktop and sign-in servers, or aging hardwareNew Windows Server, SQL Server and remote desktop licenses, and a SQL Server version your software vendor supports
Move to a hosted private cloudYou’d rather not own server hardware againWhere the data will live, how staff connect, the provider’s security evidence and its exit terms
Buy Extended Security UpdatesOne server can’t move by January 12 and qualifiesSecurity fixes only, three years at most, strict eligibility and a price you must get quoted

Extended Security Updates: The Fine Print

Microsoft calls them “a last resort paid option” and “a temporary bridge.” For Windows Server 2016:

  • Eligibility: Standard and Datacenter editions only⁠ (opens in new tab), covered by active Software Assurance (an add-on to Microsoft volume licenses), subscription licensing or licenses supplied by a hosting provider under Microsoft’s service-provider program. The client access licenses that reach the server need Software Assurance or subscription licensing too.
  • Buying: yearly through Microsoft licensing, or monthly through Azure Arc⁠ (opens in new tab), Microsoft’s cloud-based server management service, which you can set up now; Arc billing starts January 13, 2027, at a minimum of eight cores per virtual server. Late sign-ups pay for the months they missed.
  • Coverage: security fixes rated Critical or Important (Microsoft’s two highest severity ratings), with no bug fixes or general technical support. The first year ends January 11, 2028; the last, January 8, 2030.
  • Price: Microsoft lists monthly rates for Azure Arc on its Azure Arc pricing page⁠ (opens in new tab). Prices through Microsoft licensing come from your reseller. Get a written quote either way.
  • If a server doesn’t qualify: switching it to subscription licensing can make it eligible. Otherwise, our advice is to move it, or limit what can reach it until it’s retired.

A Realistic Timeline

Our suggested schedule for a firm with a handful of servers: tight, but workable if you start now.

Now to Friday, December 4, 2026

Take inventory. List each server’s Windows version and edition, its job, its SQL Server version, its license type and its warranty date. Ask your software vendors which versions they support; order any new hardware now.

By Friday, December 11

Decide server by server and order licenses. For any server that can’t move in time, confirm Extended Security Updates eligibility and get a quote.

December 12–20

Build, test, move. Have a few staff run real work on the new servers, prove a full backup restores, then switch over on the weekend of December 19–20.

January 9–10, 2027

Last switch-over weekend. Enroll anything still on Windows Server 2016 after Sunday in Extended Security Updates.

Tuesday, January 12, 2027

Final monthly security update. Install it on every server still running 2016.

Wednesday, January 13, 2027

First day without support. Power off replaced servers, keep them briefly as a fallback, then wipe their drives.

By Wednesday, June 30, 2027

Off the bridge. Move any server still on Extended Security Updates once your first-quarter deadlines have passed. If you pay monthly through Azure Arc, turn off the server’s Extended Security Updates license once it has moved, so billing stops.

What We Recommend

This section is TPAIT’s advice, not Microsoft’s or DOL’s.

  • Go to Windows Server 2025, not 2019 or 2022. Microsoft recommends it, its support runs to November 14, 2034, and it is the only one of the three on which Microsoft still supports Microsoft 365 Apps. Microsoft supports those apps on Windows Server 2025 until October 2029.
  • Replace database, remote desktop and sign-in servers rather than upgrading them in place, and move databases to the newest SQL Server version your software vendor supports. For databases, Microsoft itself says a side-by-side migration “might be the more prudent, yet more costly, approach.”
  • Use Extended Security Updates for one or two stubborn servers, not as the plan, and set the date you’ll be off them.
  • Write it down. One page per server: what it does, what you decided, who owns it and the finish date. It feeds your risk assessment and answers plan sponsor questionnaires.

If you would rather not own servers again, consider our private cloud. Your firm gets its own virtual servers on a shared pool of servers, with each TPA kept apart on its own VLAN (a private network segment), in a Southern California facility engineered to a concurrently maintainable design, with N+1 redundant power and cooling; we can also host your own hardware there (colocation). We plan the move for a weekend—preparation on Friday, migration on Saturday, testing on Sunday—and our managed IT service keeps the servers patched and monitored afterward.

Frequently Asked Questions

Will our Windows Server 2016 servers stop working on January 12, 2027?

No. They keep running, but after the final monthly security update on January 12, 2027, Microsoft stops providing security fixes, bug fixes and technical help, except security fixes for servers covered by paid Extended Security Updates. On other servers, newly found flaws stay open.

Can a small TPA buy Extended Security Updates?

Only if each server qualifies: Standard or Datacenter edition, covered by active Software Assurance, subscription licensing or licenses supplied through a hosting provider’s Microsoft agreement, with Software Assurance or subscription licensing on the client access licenses that reach it. Coverage lasts three years at most, ending January 8, 2030, and late sign-ups pay for the months they missed.

Is SQL Server 2016 still supported?

No. Its extended support ended on July 14, 2026. Paid Extended Security Updates are available for up to three years but cover only flaws Microsoft rates Critical. SQL Server 2017 buys little time, since its support ends October 12, 2027, and Microsoft doesn’t support SQL Server 2016 on Windows Server 2022 or 2025.

Do we need new remote desktop licenses when we upgrade?

Yes, if your remote desktop servers move to a newer version. Remote desktop (RDS) client access licenses are tied to a Windows Server version, and 2016 licenses work only with 2016 servers. A Windows Server 2025 remote desktop server needs 2025 licenses, installed on a licensing server that also runs 2025.

Does the DOL require us to replace unsupported servers?

No. The Department of Labor’s cybersecurity guidance is a set of best practices, not a regulation. But its practice on strong technical controls lists “Hardware, software and firmware models and versions that are kept up to date.” If an unsupported server must stay for a while, document why, how you protect it and when it will be retired.

Not Sure Which Option Fits?

Book a free 30-minute assessment call. We talk through how your servers are set up today and point out what to look at first.

Book a Free Assessment Call⁠ (opens in new tab)