> ## Content Index > Fetch the complete content index at: https://stackurity.ai/blog/llms.txt > Use this file to discover other available public pages before exploring further. # Windows Server 2012 R2 end of life: dates and what to upgrade to - URL: https://stackurity.ai/blog/windows-server-2012-r2-end-of-life/ - Published: 2026-11-10T05:05:05.000Z - Updated: 2026-11-10T05:05:05.000Z - Description: Windows Server 2012 R2 extended support ended October 10, 2023 and its last updates ended October 13, 2026. See every date and what to upgrade to. - Author: Stackurity Research Team - Tags: End of Life, #eol-guide ## TL;DR - **End date:** extended support for Windows Server 2012 R2 ended on October 10, 2023, and the last Extended Security Updates period on Microsoft's lifecycle page ended on October 13, 2026. - **Already ended:** mainstream support ended on October 9, 2018, and every date listed for this release is now in the past. - **What stops:** the page shows no later support phase, so new vulnerabilities in the operating system should be treated as permanent. - **Upgrade to:** Windows Server 2025, supported until November 14, 2034, or Windows Server 2022, supported until October 14, 2031. - **Do now:** find every remaining 2012 R2 machine, isolate the ones you cannot move yet and schedule the migration. ## What reaches end of life and when Windows Server 2012 R2 was released on November 25, 2013\. Microsoft's lifecycle page says it follows the Fixed Lifecycle Policy, which gives a release a mainstream phase and an extended phase with fixed end dates, and it lists the editions Datacenter, Essentials, Foundation, Standard and the version for Embedded Systems. Both Microsoft's page and endoflife.date show the same dates: - **Mainstream support** ended on October 9, 2018\. This is the phase in which a release receives new features and design changes alongside fixes. - **Extended support** ended on October 10, 2023\. In this phase the release received security fixes but no new features. This is the date that is normally called end of life. - **Extended Security Updates** were a further paid arrangement. The page lists its third year as ending on October 13, 2026, and it lists nothing after that. Microsoft shows its dates in Pacific Time, so a server in another time zone may cross a line a few hours earlier or later. ## What end of life means A server that is out of every support phase no longer receives security updates for vulnerabilities found afterwards. Each new flaw in the operating system or in its built-in components stays open for good, which makes the machine a stable target for anyone who can reach it. - **Security:** new vulnerabilities are not fixed, so the only protection left is isolation, tight network rules and monitoring. - **Compliance and audits:** an unsupported operating system is a common audit finding, and it can block a certification or a cyber insurance renewal. - **Application vendors:** software vendors stop supporting operating systems that Microsoft no longer supports, so a database or business application may refuse to install, or refuse to give you help, on this server. ## What to upgrade to The release with the longest support is Windows Server 2025\. It was released on November 1, 2024, its mainstream support runs until November 13, 2029 and its extended support until November 14, 2034\. Windows Server 2022 is the second choice: it was released on August 18, 2021, left mainstream support on October 13, 2026 and has extended support until October 14, 2031\. Choose 2025 unless an application you depend on does not support it yet. Moving off a release this old is usually a migration rather than an in-place upgrade, because the jump crosses several versions. Follow these steps: 1. Inventory every Windows Server 2012 R2 machine, including virtual machines, test systems and servers that host only one forgotten application. Record the roles, applications and who owns each one. 2. Check that each application and driver supports the target release, and decide between an in-place upgrade and, better, a clean installation on a new server with the data migrated. 3. Build and test the new server, move the workload during a maintenance window, and keep the old machine offline but intact until the new one has proved itself. 4. For anything you cannot move yet, restrict network access to the minimum, keep it off the internet and record an owner and a retirement date. 5. Retire the old machine, remove it from your inventory, and confirm that no end-of-life finding remains for it. ## How to check one server by hand On the server, open a PowerShell window and read the operating system name and version: ``` Get-ComputerInfo | Select-Object WindowsProductName, OsVersion (Get-CimInstance Win32_OperatingSystem).Caption systeminfo | findstr /B /C:"OS Name" /C:"OS Version" winver ``` The first three commands print the product name and version in the console, and winver opens a small window with the same information. A server that reports Windows Server 2012 R2 in its name is in scope. To check the whole estate, run the same command remotely or through your management tool, and do not forget machines in cloud accounts and lab networks. ## How Stackurity flags it Stackurity keeps one live inventory of your servers, deployed applications, repositories and container images. Its agent also inventories Windows hosts and raises end-of-life findings for the Windows Server or Windows release they run. End-of-life data is synced and matched against that inventory every day, and each finding goes onto a short list of upgrades, most urgent first. To be plain about what Windows coverage means: Windows servers are checked for end of life only, with no vulnerability matching of the operating system or its programs. A host that is already out of support will therefore show up as an end-of-life finding, but the list of open flaws on it is something you have to judge from Microsoft's own security updates and your isolation rules. The [compatibility guide](https://stackurity.ai/docs/compatibility) lists what each platform supports. The core is open source, and Stackurity Cloud has a 14-day free trial without a card: [start a free trial](https://app.stackurity.dev/signup?utm%5Fsource=blog&utm%5Fmedium=referral&utm%5Fcampaign=end-of-life&utm%5Fcontent=windows-server-2012-r2-end-of-life). For the same approach on newer releases, see our guides to [Windows Server 2016](https://stackurity.ai/blog/windows-server-2016-end-of-life/) and [Windows Server 2019](https://stackurity.ai/blog/windows-server-2019-end-of-life/). ## FAQ ### When does Windows Server 2012 R2 reach end of life? Extended support for Windows Server 2012 R2 ended on October 10, 2023\. The paid Extended Security Updates listed by Microsoft ran until October 13, 2026, so the release is past every support date on the lifecycle page. ### Is Windows Server 2012 R2 still getting security updates? No. Microsoft's lifecycle page lists the last Extended Security Updates period as ending on October 13, 2026 and shows no later phase, so assume newly found vulnerabilities will not be fixed. ### What should I upgrade Windows Server 2012 R2 to? Windows Server 2025 has the longest support, with mainstream support until November 13, 2029 and extended support until November 14, 2034\. Windows Server 2022 is supported until October 14, 2031. ### What was the Windows Server 2012 R2 mainstream support end date? Mainstream support ended on October 9, 2018\. After that the release was in extended support, which covered security fixes but no new features. ### Does Stackurity check Windows Server 2012 R2 for end of life? Yes. Stackurity's agent inventories Windows hosts and raises an end-of-life finding for the Windows Server release they run. End-of-life data is matched against your inventory every day. Windows servers are checked for end of life only, not for vulnerabilities in installed programs. ## Sources Dates come from [Microsoft's lifecycle page for Windows Server 2012 R2](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2012-r2) and [endoflife.date](https://endoflife.date/windows-server). Upgrade targets: [Windows Server 2025](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2025) and [Windows Server 2022](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2022). Product facts: [Stackurity](https://stackurity.ai/llms.txt).