Free tools Windows power users keep installed
One-click scans. No signup required.
Plan to move each Windows Server 2016 workload to a supported state before Microsoft’s January 12, 2027 end-of-support milestone. The right route depends on the server’s edition, roles, applications, hardware, downtime tolerance, and licensing; a direct upgrade is not suitable for every system. Standard and Datacenter customers may be able to use Extended Security Updates (ESUs) as a temporary security-update bridge, but Windows Server 2016 Essentials is excluded.
What Windows Server 2016 end of support means
Microsoft’s support and ESU guidance uses January 12, 2027 as the Windows Server 2016 end-of-support (EOS) milestone. Microsoft’s lifecycle table lists January 13, 2027 as the end of extended support. Treat January 12 as the planning deadline; the two published dates should not be read as confirmation that standard support continues through all of January 13. See Microsoft’s Windows Server 2016 lifecycle page.
After standard support ends, a server without applicable ESUs is outside standard support and security-update servicing. Microsoft identifies increasing security, compliance, compatibility, and operational risks for unsupported environments. These are reasons to plan and test a transition, not a basis for predicting a particular breach, outage, or financial loss.
Choose a supported destination and migration route
Microsoft’s current upgrade-path table lists direct in-place upgrade routes from a nonclustered Windows Server 2016 system to Windows Server 2019, Windows Server 2022, and Windows Server 2025. A listed route is not a blanket guarantee: confirm the path for the specific build, edition, roles, and configuration, and check application-vendor support. Microsoft’s Windows Server upgrade overview and role migration guidance provide the relevant matrices and procedures.
#1 Best Overall
| Route | When it may fit | Important trade-off or check |
|---|---|---|
| In-place upgrade | The existing server and configuration are supported, and keeping its settings, roles, features, and data is desirable. | Requires a reboot and a supported role/configuration. Validate the exact version path and application support; back up and rehearse recovery first. |
| Migration to a new server | You are replacing hardware, refreshing the operating system, or want to move roles and workloads in stages. | Requires a destination and planned data or service cutover. Check role-specific migration support, dependencies, and rollback arrangements. |
| Clean install | You need a fresh operating system, commonly on new hardware, and can reinstall or migrate applications and data. | Plan configuration, application installation, data transfer, and service validation; do not assume the old server’s settings will carry over. |
| Cluster OS rolling upgrade | The server is part of a supported cluster workload for which Microsoft documents a rolling-upgrade path. | Follow the cluster-specific, version-by-version procedure and verify workload and role support; do not apply the nonclustered in-place path as a substitute. |
| Cloud or hybrid migration | The workload is suitable for a different operating model or hosting environment. | Assess application compatibility, connectivity, security and compliance requirements, operational ownership, costs, and any ESU eligibility separately. |
Compare routes against outage tolerance, hardware lifecycle, workload compatibility, recovery options, data movement, licensing, security and compliance needs, and who will operate the destination. Microsoft says migration is the better choice when moving to new hardware. Azure is an option for suitable workloads, not a universal destination.
Check in-place upgrade restrictions
- A 32-bit-to-64-bit architecture change and a language change are unsupported in-place upgrade paths.
- Server Core cannot be changed to Desktop Experience, or Desktop Experience to Server Core, during an in-place upgrade.
- Evaluation and prerelease installations have path limitations; verify their specific eligibility before planning an upgrade.
- In-place upgrades of VHD-boot systems and Windows Storage Server are unsupported.
- Disable NIC Teaming before an in-place upgrade; it can be re-enabled afterward.
- Confirm target licensing and activation. Each Windows Server upgrade requires a separate license.
These restrictions do not establish that a particular server must use one specific alternative. Check the current Microsoft guidance for its source edition, build, roles, target, and licensing position.
A practical migration playbook
- Inventory the workload. Record edition and build; physical or virtual host; hardware and firmware; roles and features; applications and vendor dependencies; identity, network, and storage dependencies; certificates and DNS; scheduled tasks and service accounts; backup and recovery; monitoring and integrations; owners; and criticality. For Essentials, also document each Essentials-specific workflow.
- Select a destination and route. Compare supported on-premises upgrade, new-server migration, and cloud or hybrid options against compatibility, downtime, licensing, security and compliance requirements, operating model, and cost. Choose a target version based on those constraints rather than using one target for every server.
- Verify technical and licensing prerequisites. Confirm the exact in-place path or role migration matrix, target media and build, application support, hardware readiness, backup capacity, activation method, and licensing. Ask a cloud provider to confirm its support for the specific upgrade or migration scenario.
- Back up and rehearse recovery. Microsoft’s Windows Server upgrade guidance says: “Always back up your system and important files before performing an in-place upgrade, clean install, or migration to a later version of Windows Server.” Confirm that recovery works and that backups meet organizational policy before changing production.
- Pilot and test. Validate application function, authentication and permissions, DNS, certificates, network and storage, backup and restore, monitoring, scheduled operations, and the documented failback or rollback process. For Essentials, test replacement remote access and client backup workflows, not just the new operating system.
- Cut over and close. Schedule a maintenance window where required, obtain service-owner acceptance, monitor the destination, and record rollback decisions. Decommission the old system only after dependencies have been checked and retention obligations are met.
This sequence is a practical synthesis of Microsoft’s upgrade, backup, and role-migration guidance; it is not a universal Microsoft-prescribed checklist. Adapt it to the workload and change controls in your environment.
Windows Server 2016 ESUs: a limited bridge
Microsoft offers ESUs for Windows Server 2016 Standard and Datacenter, but not Essentials. ESUs provide Critical and Important security updates for up to three years after EOS; they do not add features, provide customer-requested nonsecurity hotfixes, or include design changes. They can reduce one part of the transition risk for eligible deployments, but they do not put the server back into standard support or remove the need to select and fund a supported destination. See Microsoft’s ESU overview.
Recommended Free Tools
Rank #3
- Mastering Active Directory: Design, deploy, and protect Active Directory Domain Services for Windows Server 2022, 3rd Edition
- ABIS BOOK
- Packt Publishing
As of October 8, 2026, Microsoft says Azure Arc configuration for Windows Server 2016 ESUs became available on August 3, 2026. Billing for Azure Arc-enabled Windows Server 2016 ESUs begins January 13, 2027; Microsoft says licenses provisioned late can be back-billed to the EOS date. Do not assume a late enrollment delays the applicable charges.
Microsoft’s licensing guidance describes ESUs by Standard or Datacenter edition and physical-core or virtual-core basis. Physical-core licensing has a 16-core minimum per machine. The correct edition and core basis depend on deployment and license posture; confirm current official terms and get licensing advice for the environment rather than estimating a price from a generic server count.
Eligibility and treatment can differ for Azure-hosted, Azure Arc-connected, Azure VMware Solution, and Azure Local systems. Microsoft’s ESU preparation guidance says some Azure VMware Solution and Azure Local machines may qualify for free ESUs, subject to its conditions. Verify the current eligibility and billing rules for the exact hosting arrangement; cloud hosting alone does not establish free ESU coverage. See Microsoft’s ESU preparation guidance and ESU billing guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Windows Server 2016 Essentials needs a separate plan
Essentials is not covered by Windows Server 2016 ESUs. An OS upgrade alone may also leave replacement work for functions tied to Essentials. Inventory and explicitly replace or retire any use of Remote Web Access, remotewebaccess.com domain and dynamic DNS integration, client backup and restore, dashboard, connector, health monitoring, or related workflows.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesBefore cutover, test remote access, identity and permissions, backup and recovery, DNS, certificates, application connectivity, and administrative operations. Microsoft’s Windows Server Essentials end-of-support guidance describes these dependencies and the need to plan replacements. Verify each workflow with its users and owners; do not treat an operating-system installation as proof that it still works.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
