Windows Server 2019 End of Support: Plan Before January 9, 2029
Extended support for Windows Server 2019 ends January 9, 2029. What changed when mainstream support ended, Microsoft's upgrade paths to 2022 and 2025, the hardware changes in 2025, and how to plan so 2019 is not the next 2016 problem.
Windows Server 2019 extended support ends January 9, 2029
Microsoft ends extended support for Windows Server 2019 on January 9, 2029. Mainstream support already ended January 9, 2024, so 2019 still receives security updates but no non-security updates or feature changes. Microsoft supports in-place upgrades from 2019 to Windows Server 2022 or 2025. Mainstream support for 2022 ended October 13, 2026, which leaves 2025 with the longest runway, through November 14, 2034.
Windows Server lifecycle dates
The last day of each support phase as Microsoft lists it, checked November 2026. Microsoft's lifecycle tables show each end as 6:59:59 AM Pacific Time on the following morning, so the last day of support is the day before. Every version here follows the Fixed Lifecycle Policy.
| Version | Support starts | Mainstream support ends | Extended support ends |
|---|---|---|---|
| Windows Server 2016 | October 15, 2016 | January 11, 2022 | January 12, 2027 |
| Windows Server 2019 | November 13, 2018 | January 9, 2024 | January 9, 2029 |
| Windows Server 2022 | August 18, 2021 | October 13, 2026 | October 14, 2031 |
| Windows Server 2025 | November 1, 2024 | November 13, 2029 | November 14, 2034 |
What changed when mainstream support ended
When mainstream support for Windows Server 2019 ended on January 9, 2024, the product moved into the Extended Support phase of Microsoft's Fixed Lifecycle Policy. Security updates continue at no additional cost. Non-security updates, design and feature requests, and warranty claims stopped. The table shows what each phase includes as Microsoft publishes it.
| Type of support | Mainstream (through January 9, 2024) | Extended (through January 9, 2029) | After extended support ends |
|---|---|---|---|
| Security updates | Available | Available at no additional cost | Only through an Extended Security Update program |
| Non-security updates | Available | Not available | Not available |
| Requests to change design or features | Available | Not available | Not available |
| Warranty claims and incident support included with a license or Software Assurance | Available | Not available | Not available |
| Paid support | Available | Available | Requires an Extended Security Update program |
| Self-help online support | Available | Available | For at least 12 months after end of support |
Upgrade paths from Windows Server 2019
Microsoft's in-place upgrade matrix lists Windows Server 2022 and Windows Server 2025 as supported targets from Windows Server 2019. An in-place upgrade keeps settings, server roles, and data. The upgrade method, and whether the server is in a cluster, decide the route.
| Target | Installation media | Windows Update feature update | Cluster OS rolling upgrade |
|---|---|---|---|
| Windows Server 2022 | Supported | Not listed | Supported, one version at a time |
| Windows Server 2025 | Supported | Supported once the March 2026 cumulative update (KB5078752) or later is installed | Through 2022 first, one version at a time |
- Installation type stays the same. Switching between Server Core and Server with Desktop Experience during an in-place upgrade is not supported.
- Edition carries over. Standard can move up to Datacenter or Datacenter: Azure Edition during the upgrade, but Datacenter cannot move down to Standard.
- Domain controllers. Microsoft advises against upgrading servers that run Active Directory Domain Services in place. Promote new domain controllers on a clean install and demote the old ones.
- Clusters. Use Cluster-Aware Updating or a cluster OS rolling upgrade, which moves one version at a time.
- NIC Teaming and boot from VHD. Disable NIC Teaming before the upgrade and turn it back on after. Servers that boot from VHD cannot be upgraded in place.
- Virtual machines on the host. Shut down or migrate every VM before the upgrade starts.
Hardware requirements that change with Windows Server 2025
Microsoft's hardware requirements page sets higher minimums for Windows Server 2025 than for 2022, 2019, and 2016. Check each physical 2019 host against the 2025 list before you plan an in-place upgrade on it.
- Processor instructions. Windows Server 2025 adds SSE4.2 and POPCNT to the minimums all four versions share: a 1.4 GHz 64-bit processor with NX and DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, and Second Level Address Translation. Microsoft points to the Sysinternals Coreinfo tool to check a processor.
- Memory. The Server Core minimum rises from 1 GB to 2 GB. Server with Desktop Experience stays at 2 GB, with 4 GB recommended for 2025. Physical hosts need ECC memory or similar technology.
- Storage and network. These minimums do not change: at least 32 GB for the system partition, a PCI Express storage adapter with no PATA, ATA, IDE, or EIDE boot, page, or data drives, and a PCI Express Ethernet adapter of at least 1 gigabit per second.
- Secured-core server. These features are available on Windows Server 2022 and later, not on 2019. They need TPM 2.0, Secure Boot, virtualization-based security, DMA remapping (Intel VT-d or AMD-Vi), Kernel DMA Protection, and DRTM.
- TPM. A TPM is required only for certain features, such as BitLocker Drive Encryption. A hardware TPM must implement version 2.0 of the TPM specification.
- Manufacturer support. Microsoft's minimums are a floor. Confirm the server manufacturer supports the model, firmware, and drivers on the target release.
Your options for each Windows Server 2019 server
| Option | What it involves | Usually fits when |
|---|---|---|
| Upgrade in place to Windows Server 2025 | Run Setup from installation media or take the feature update in Windows Update; settings, roles, and data stay | The host meets the 2025 minimums, its manufacturer supports 2025 on it, and the applications are certified for 2025 |
| Upgrade in place to Windows Server 2022 | The same in-place process, to a version whose mainstream support ended October 13, 2026 | An application vendor supports 2022 but not 2025 |
| Clean install on new hardware, then migrate | Install the new version on a new host, move roles and data, and cut over | The host fails the 2025 checks or is near the end of its warranty, or the server is a domain controller |
| Move the workload to Azure | Run the workload on an Azure virtual machine or a managed Azure service | You are reducing on-premises hardware and the application supports it |
| Retire or consolidate | Archive the data and shut the server down, or move its roles onto a supported server | The server's role is no longer needed or is small enough to merge |
See the Server replacement in Las Vegas and the Replace the server or move to Azure.
How to keep 2019 from becoming the next 2016 problem
Windows Server 2019 extended support ends January 9, 2029, about two years after Windows Server 2016 extended support ends on January 12, 2027. Put both versions in one inventory so the 2019 work is scheduled while the 2016 work is underway.
- Inventory every Windows Server 2019 server: host model, warranty date, edition, installation type, roles, and applications.
- Check each physical host against the Windows Server 2025 processor and memory minimums. Mark the hosts that fall short as replacement candidates.
- Ask each application vendor which Windows Server versions they support. Default to 2025, and note the servers a vendor holds to 2022, since 2022 mainstream support ended October 13, 2026.
- Put domain controllers and clusters in their own workstream. Microsoft advises new domain controllers on a clean install, and clusters move one version at a time.
- Confirm licensing. Microsoft states that each Windows Server upgrade requires a separate license, with a valid product key and activation method for the target version.
- Before each upgrade, take a full backup, run a restore test, and book a maintenance window. Microsoft lists all three as prerequisites, and the upgrade requires downtime.
- Sequence the 2016 servers first, then set target dates for the 2019 servers well ahead of January 9, 2029.
See the Infrastructure End-of-Support Assessment and the Windows Server 2016 end of support guide.
Frequently asked questions
When does Windows Server 2019 support end?
Extended support for Windows Server 2019 ends January 9, 2029. Mainstream support ended January 9, 2024. The dates apply to the Datacenter, Essentials, and Standard editions, and containers released with Windows Server 2019 follow the same dates.
Is Windows Server 2019 still getting security updates?
Yes. During extended support, Microsoft provides security updates at no additional cost through January 9, 2029. Non-security updates and requests for design or feature changes are no longer available.
Can Windows Server 2019 upgrade directly to Windows Server 2025?
Yes. Microsoft's matrix supports it from installation media, and through the Windows Update feature update once the March 2026 cumulative update (KB5078752) or later is installed. A cluster OS rolling upgrade is the exception: it moves one version at a time, so a 2019 cluster goes to 2022 first.
Will Microsoft offer Extended Security Updates for Windows Server 2019?
As of November 2026, Microsoft's Extended Security Updates FAQ does not list Windows Server 2019. Plan to move the servers rather than count on a paid extension.
Does an in-place upgrade need its own license?
Yes. Microsoft states that each Windows Server upgrade requires a separate license, and you need a valid product key and activation method for the target version before you start.
Should a Windows Server 2019 domain controller be upgraded in place?
Microsoft advises against it. An in-place upgrade does not deliver the Active Directory improvements in Windows Server 2025 and later. Promote new domain controllers on a clean install and demote the old ones.
Plan Windows Server 2019 alongside your 2016 servers
Send us your server list with host models, warranty dates, and the applications on each server. We will mark each one upgrade, replace, migrate, or retire, pick the target version, and sequence the 2019 work behind the 2016 deadline. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.
Sources
Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.
- Microsoft Lifecycle: Windows Server 2019 (opens in a new tab)
- Microsoft Lifecycle: Windows Server 2022 (opens in a new tab)
- Microsoft Lifecycle: Windows Server 2025 (opens in a new tab)
- Microsoft Lifecycle: Windows Server 2016 (opens in a new tab)
- Microsoft Learn: Windows Server release information (opens in a new tab)
- Microsoft Lifecycle: Fixed Lifecycle Policy (opens in a new tab)
- Microsoft Lifecycle: Extended Security Updates FAQ (opens in a new tab)
- Microsoft Learn: Plan your Windows Server upgrade (opens in a new tab)
- Microsoft Learn: Upgrade Windows Server in place (opens in a new tab)
- Microsoft Learn: Hardware requirements for Windows Server (opens in a new tab)
Related services
Related resources
Turn the checklist into a plan
The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.
