Skip to main content
End-of-life dates, Microsoft

Windows Server 2012 R2 End of Support: ESU Year 3 Has Ended

Microsoft's dates for Windows Server 2012 and 2012 R2, including the three paid Extended Security Updates years, and what a business still running them can do now.

Servers and databasesMicrosoftDays Dynamics team. Dates checked against the vendor's own lifecycle page on November 13, 2026.

When Windows Server 2012 and 2012 R2 support ends

Windows Server 2012 and Windows Server 2012 R2 reached the end of extended support on October 10, 2023. Microsoft then offered paid Extended Security Updates for a maximum of three years, and Year 3 ended on October 13, 2026. Microsoft's lifecycle pages list no further year, so a server still on 2012 or 2012 R2 now has no Microsoft path for security updates and needs a migration or retirement plan.

Windows Server 2012 and 2012 R2 lifecycle dates

Each row uses Microsoft's own milestone name and the exact scope it applies to.

Milestone (vendor's term)Applies toDateStatus
Mainstream End DateWindows Server 2012 and Windows Server 2012 R2October 9, 2018Passed
Extended End DateWindows Server 2012 and Windows Server 2012 R2October 10, 2023Passed
Extended Security Update Year 1 endsStandard, Datacenter, and Embedded editions with ESUsOctober 8, 2024Passed
Extended Security Update Year 2 endsStandard, Datacenter, and Embedded editions with ESUsOctober 14, 2025Passed
Extended Security Update Year 3 endsStandard, Datacenter, and Embedded editions with ESUsOctober 13, 2026Passed

Microsoft lists the same dates for Windows Server 2012 and Windows Server 2012 R2. Its Extended Security Updates FAQ says ESUs for these versions covered updates rated critical and important for a maximum of three years after end of support.

Source: Microsoft Lifecycle: Windows Server 2012 R2 (opens in a new tab). Vendors move dates, so confirm on that page before a budget or purchase order depends on one.

What it means for a business

With ESU Year 3 over, Microsoft's lifecycle pages show nothing further for these versions. That changes the question from when to move to how fast.

No security updates from Microsoft

ESUs for Windows Server 2012 and 2012 R2 ran for a maximum of three years after end of support, and the last year ended October 13, 2026. New vulnerabilities found after that date are not patched for these versions.

The browser stopped earlier

Microsoft Edge version 109 was the last version supported on Windows Server 2012 and 2012 R2, and it received critical security fixes only until October 10, 2023.

The applications on top matter as much

Software installed on these servers, such as databases or line-of-business applications, has its own support terms. Ask each vendor whether it still supports its software on these versions.

Who is affected

Check for these, including servers nobody logs in to any more:

  • Physical and virtual servers on any edition of Windows Server 2012 or 2012 R2.
  • Organizations that bought ESUs: that coverage ended with Year 3 on October 13, 2026.
  • Older domain controllers, print servers, and application servers left running after a migration.
  • Servers that host SQL Server 2014 or older, which have their own end dates.

Your realistic paths

Microsoft lists no further coverage, so the options are about how to leave:

PathWhat it involvesUsually fits when
Rebuild on a supported releaseBuild a new server on Windows Server 2022 (extended support to October 14, 2031) or Windows Server 2025 (to November 14, 2034) and move the roles and dataThe workload is still needed and its software supports a newer Windows Server
Move the workload to Azure or a hosted serviceReplace the server's job with a cloud service or a hosted application versionThe server runs one application whose vendor offers a hosted or cloud option
Contain while you migrateRestrict network access to the server and plan its retirement on a fixed dateMigration needs more time and the server cannot be switched off yet; this lowers exposure but does not restore updates
RetireArchive the data and shut the server downThe role is no longer used or has already moved

See the Replace the server or move to Azure and how we approach windows server replacement.

What to check before you decide

  • Roles on each server. Domain controller, file, print, DHCP, DNS, or application: each role moves differently.
  • Application support. Ask each software vendor which Windows Server versions its current release supports.
  • Hardware. Check whether each server's hardware is still under a support contract before planning an in-place upgrade.
  • Microsoft's upgrade paths. Check Microsoft's documented in-place upgrade paths from your version before choosing an upgrade over a new build.
  • Network exposure. List which systems can reach each server and which it can reach, so you can restrict access while it remains.

How Microsoft's Fixed Lifecycle Policy works

Under Microsoft's Fixed Lifecycle Policy, Mainstream Support includes security updates and the ability to request non-security updates. Extended Support includes security updates at no additional cost, and Microsoft does not accept requests for warranty support, design changes, or new features in that phase. Microsoft shows each end date as 6:59:59 AM Pacific Time on the following morning, so the dates on this page are the last full day.

Frequently asked questions

Can I still get Extended Security Updates for Windows Server 2012 R2?

Microsoft's lifecycle pages list three ESU years for Windows Server 2012 and 2012 R2, the last ending October 13, 2026, and no fourth year.

Which editions were eligible for ESUs?

Microsoft says the Standard, Datacenter, and Embedded editions of Windows Server 2012 and 2012 R2 were eligible for ESUs.

Does Windows Server 2012 R2 stop working now?

Microsoft's pages describe the end of support and updates, not a shutdown. The server keeps running, but new security issues are not fixed for it.

Not sure which of your systems this affects?

Send the models and versions you run. A person at Days Dynamics matches each one to its vendor dates and tells you what likely needs a project. It is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.

Sources

Vendor pages checked on November 13, 2026. Dates and product status can change, so confirm on the source before you rely on them.

Planning around this date?

Find out which of your systems lose support

Send a list of servers, firewalls, and Windows 10 PCs. A person replies, usually within 2 business days, with what loses vendor support, when, and what likely needs a project. Free, with no obligation.