All posts
Legacy Modernization

Windows Server 2016 End of Support (January 12, 2027): Your Options on AWS

By

October 25, 2026

7 min read

Windows Server 2016 stops receiving security updates on January 12, 2027, and IIS 10 and .NET Framework 4.6.2 on it go with it. In-place upgrade, ESUs through Azure Arc, AWS's End-of-Support Migration Program, containers or Linux: the cost, effort and licensing traps of each on EC2.

Windows Server 2016
End of Support
EC2
Licensing
Migration
2027

Microsoft's extended support for Windows Server 2016 ends on January 12, 2027. The same day, IIS 10 on Windows Server 2016, .NET Framework 4.6.2, Hyper-V Server 2016 and WSUS on 2016 also reach end of support. For an EC2 fleet, that is typically a large share of the Windows instances still running.

The options

Option

Effort

Cost

Buys you

In-place upgrade to Windows Server 2022 or 2025

Low to medium, per server

License Included pricing unchanged on EC2

Supported until 2031 (2022) or later (2025)

Replace with a new instance on a current AMI

Medium; needs the app reinstalled

Same

A clean, reproducible build

Extended Security Updates via Azure Arc

Low

Annual subscription, rising each year

Up to three more years of security fixes

AWS End-of-Support Migration Program

Medium; partner-led

Engagement cost

Runs old apps on a current OS without code changes

Containers or modern .NET on Linux

High

Removes the Windows licence

An end to Windows lifecycle deadlines for that app

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

Licensing traps on AWS

  • If you bring your own Windows Server licences, Microsoft's October 2019 rule applies: licences bought after October 1, 2019, and versions released after that date (including Windows Server 2022 and 2025), are not eligible for BYOL on AWS dedicated hosts. Upgrading a BYOL server usually means moving to License Included.

  • Windows Server has no License Mobility, even with Software Assurance. SQL Server, SharePoint and Exchange do.

  • License Included instances already include the right to run the current version, so on most EC2 fleets the upgrade costs labour, not licences.

How we run an upgrade wave

  1. Inventory with Systems Manager: OS version, installed software, last login and network connections per instance.

  2. Retire what is unused. Snapshot it, stop it for 30 days, then delete.

  3. Group the rest by application and test one representative instance per group: take an AMI, launch a copy, upgrade the copy, run the application's tests. AWS publishes Systems Manager Automation runbooks that clone and upgrade a Windows instance.

  4. Upgrade in waves with a rollback AMI for each instance.

  5. For the few applications that cannot move by January, buy ESUs for exactly those servers, with an exit date.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.