Windows Server 2019 End of Life: Dates & Upgrade Paths

For teams that run Windows Server 2019 in production, the lifecycle position is this: mainstream support ended January 9, 2024, and extended support (end of life) ends January 9, 2029. The operating system currently receives security updates only. This page lists the verified dates, what the mainstream cutoff changed in practice, the supported upgrade paths to Windows Server 2022 and 2025, and how the planning window compares to Windows Server 2016.

Windows Server 2019 end of life: the dates

Windows Server 2019 follows the Microsoft Fixed Lifecycle Policy: five years of mainstream support followed by five years of extended support. The dates below apply to the Datacenter, Essentials, and Standard editions and are taken from the Microsoft Lifecycle page for Windows Server 2019.

Containers based on the Windows Server 2019 image follow the same lifecycle dates. Windows Server, version 1809 shared the same November 2018 re-release, but as a Semi-Annual Channel release it left support years ago; the fixed dates above apply to the Long-Term Servicing Channel product only.

What the end of mainstream support means now

Since January 9, 2024, Windows Server 2019 has been in the extended support phase. In practice:

• Security updates continue. Monthly security patches keep arriving through Windows Update, WSUS, and the Update Catalog until January 9, 2029. The system is not unpatched today.
• No feature updates or non-security fixes. Bugs that are not security vulnerabilities are no longer fixed. A reliability or performance defect in the 2019 codebase stays as it is unless it crosses into security territory.
• No design changes or new hardware enablement. Support for newer processors, drivers, and platform features lands in Windows Server 2022 and 2025, not in 2019.
• Paid support only. Free incident support ended with mainstream support. Extended-phase support requires a paid agreement, and non-security hotfix requests generally require Unified Support with an extended hotfix arrangement.

The compliance position is still clean: a Windows Server 2019 host receiving monthly security updates passes the vendor-supported-software test that PCI DSS and similar frameworks apply. That changes on January 9, 2029, when the product moves to the same unsupported category Windows Server 2012/R2 occupies today.

Microsoft 365 Apps support on Windows Server 2019 has ended

One deadline already passed and catches RDS and session-host deployments: support for Microsoft 365 Apps on Windows Server 2019 ended on October 14, 2025, per the Windows Server end of support and Microsoft 365 Apps article. Microsoft 365 Apps follows the Modern Lifecycle Policy, which requires a supported configuration independent of the operating system's own dates.

Microsoft added a security bridge: Microsoft 365 desktop apps on Windows Server 2019 continue to receive security updates until October 10, 2028, but feature updates stop at Version 2608, and the configuration is unsupported for anything else. A terminal server or Azure Virtual Desktop-adjacent farm on 2019 that serves Office to users is running an out-of-support Office configuration today, four years before the operating system itself reaches end of life. For those hosts, the migration deadline is effectively behind you, not in 2029.

Upgrade paths from Windows Server 2019

Windows Server 2019 has direct in-place upgrade paths to both current versions, per Plan your Windows Server upgrade:

Points that decide which target and method to use:

• Target 2025, not 2022, in most cases. Windows Server 2022 mainstream support ends in October 2026, and Microsoft 365 Apps support on 2022 ends with it. Upgrading from 2019 to 2022 in 2026 buys a short runway before the same exercise repeats. Windows Server 2025 resets the clock to October 2029 mainstream / October 2034 extended.
• Windows Update path exists for 2025. Windows Server 2019 and 2022 can take Windows Server 2025 as an optional feature update through Windows Update once the prerequisite cumulative update is installed, which removes the ISO-mounting step. Details are in Perform an in-place upgrade of Windows Server.
• Domain controllers: do not upgrade in place. Microsoft's guidance for AD DS is to install new domain controllers on the new version and demote the old ones, rather than in-place upgrading. An in-place-upgraded DC also keeps the legacy 8K database page size instead of the 32K format available on clean 2025 promotions.
• Role limits still apply. Some roles, RDS among them, keep the older two-version-hop restriction or require a controlled sequence. Check the role migration matrix before assuming the four-version jump applies to your workload.
• Licensing is per version. Each Windows Server upgrade requires a valid license and product key for the target version; Software Assurance provides new-version rights, but the 2019 key does not activate 2022 or 2025.

Planning window: 2019 versus the Windows Server 2016 deadline

The two versions are in different situations and should be scheduled differently. Windows Server 2016 reaches end of support on January 12, 2027, per the Windows Server 2016 lifecycle page; that migration is covered in Windows Server 2016 end of life. Windows Server 2019 has two additional years.

A reasonable sequence for a mixed estate: move 2016 hosts first against the January 2027 wall, move 2019 hosts that serve Microsoft 365 Apps next (their supported window already closed), and schedule the remaining 2019 hosts across 2027-2028 so nothing lands in the final quarter before January 2029. Version-by-version dates are in the Windows Server versions reference.

ESU expectations for January 2029

Microsoft runs a paid Extended Security Updates program for Windows Server versions that pass end of support. The established pattern, documented in the Extended Security Updates overview for Windows Server 2012/R2 and announced for 2016: up to three annual installments of security updates rated Critical and Important, purchased per core, with the price rising each year, plus free ESUs for instances running on Azure or connected through Azure Arc.

As of this writing, Microsoft has not published Windows Server 2019 ESU terms or pricing. Based on the pattern, the working assumptions are: an ESU bridge will likely exist from January 2029 to roughly January 2032, it will cost a significant fraction of the license price per year, it will cover security fixes only, and Azure-hosted or Arc-enabled machines will likely get it at no additional charge. ESU is a bridge for workloads that cannot move in time, not a plan; the three-year cost typically exceeds the cost of the upgrade it defers.

How to check what you are running

Run this on each host:

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

Windows Server 2019 reports OS version 10.0.17763. Any host showing build 17763 is on the security-only track described above; build 14393 is Windows Server 2016 and is against the nearer January 2027 deadline.

FAQ

When is the Windows Server 2019 end of life date?

Extended support ends January 9, 2029. Mainstream support already ended on January 9, 2024. Until 2029 the product receives security updates only.

Does Windows Server 2019 still get security updates?

Yes. Monthly security updates continue through January 9, 2029. Feature updates and non-security fixes stopped in January 2024.

Can I upgrade Windows Server 2019 directly to Windows Server 2025?

Yes. In-place upgrade from 2019 to 2025 is supported via installation media, and also via Windows Update as an optional feature update once the required cumulative update is installed. Direct upgrade to Windows Server 2022 is also supported, but its mainstream support ends in October 2026, so 2025 is the standard target.

Is Microsoft 365 Apps still supported on Windows Server 2019?

No. Support ended October 14, 2025. Security updates for Microsoft 365 desktop apps on 2019 continue until October 10, 2028, with features frozen at Version 2608, but the configuration is otherwise unsupported.