Core Infrastructure Software End of Life Calendar 2026–2036

The Looming Cliff: Why Enterprise Software EOL is a UK Boardroom Issue

In mid-2026, enterprise estate management across the UK has transitioned from an operational routine into an urgent boardroom governance priority. The convergence of operating system transitions, database retirements, and hypervisor policy changes between 2026 and 2030 requires substantial capital and operational alignment. Running unsupported enterprise platforms is no longer treated as simple IT debt; it introduces immediate compliance and audit exposure.

Under UK Cyber Essentials criteria and National Cyber Security Centre (NCSC) operational baselines, systems that no longer receive regular security updates are treated as insecure and fail certification audits unless strictly isolated. Organisations governed by UK GDPR face severe regulatory penalties if unpatched vulnerabilities lead to a breach. Compounding this risk, many UK estates quietly harbour already-expired predecessors: Windows Server 2016 reached extended support end in January 2022, Windows Server 2019 exited mainstream support in January 2024, and SQL Server 2014 lost all extended support in July 2024. Running these platforms unpatched represents an immediate, active vulnerability before the 2026–2036 deadlines even land.

• •Windows Server 2022 mainstream support ceases on 13 October 2026, shifting systems entirely to extended support.
• •SQL Server 2016 reaches the end of its 10‑year fixed support lifecycle in 2026, making database migration or use of short‑term bridging strategies (such as Extended Security Updates) an urgent priority.
• •RHEL 8 is already in its Maintenance Support phase, operating on a track to complete termination on 31 May 2029.
• •Unpatched enterprise software creates a high risk of non‑compliance with UK Cyber Essentials and regulatory data security frameworks.

Understanding 'End of Life': Decoding Vendor Support Terminology

Vendor support policies differ significantly across enterprise publishers. A widespread operational error is conflating the end of mainstream support with full platform abandonment. For Windows Server and SQL Server, Microsoft operates on a fixed 10‑year lifecycle model divided into two distinct 5‑year phases: mainstream support and extended support. During mainstream support, Microsoft provides functional updates, design changes, and security patches. When a platform enters extended support, new non-security hotfixes and design change requests cease, although critical security patches continue without extra licensing fees.

Red Hat adopts a split model across its major Enterprise Linux distributions. Red Hat Enterprise Linux (RHEL) features a Full Support phase followed by a Maintenance Support phase. In Maintenance Support, Red Hat issues only critical security advisories (RHSAs) and selected urgent bug fixes, while architectural enhancements and hardware enablement cease. Canonical separates Ubuntu LTS into a 5-year standard support cycle and an optional Extended Security Maintenance tier. Meanwhile, Broadcom defines VMware vSphere lifecycle in General Support and Extended Support phases, each with different technical scopes and, typically, differing commercial terms for virtualised data centres.

Consolidated Enterprise Software EOL Calendar: 2026–2030 and Beyond

Tracking diverse enterprise systems requires consolidating dates across Microsoft, Red Hat, Canonical, and VMware into an actionable roadmap. Infrastructure teams must evaluate each milestone against replacement schedules, software refactoring requirements, and bare-metal server replacement windows.

The table below consolidates every major infrastructure platform deadline into a single chronological view across operating systems, relational databases, and hypervisors through 2036. (Note that enterprise application tiers like SAP ERP, Oracle Database, and Java runtimes follow independent vendor lifecycles and should be mapped alongside this core infrastructure baseline.)

• •SQL Server 2016: Reaches extended support end in 2026, marking the termination of its 10-year lifecycle.
• •Windows Server 2022: Concludes 5 years of mainstream support on 13 October 2026; extended support continues through 14 October 2031.
• •Ubuntu 22.04 LTS: Standard support ends in April 2027, transitioning workloads to expanded security maintenance options.
• •RHEL 9: Full support ends on 31 May 2027; maintenance support continues until 31 May 2032.
• •VMware vSphere 8.0: General support concludes on 10 October 2027, with extended support available through 11 October 2029.
• •RHEL 8: Enters the tail end of its lifecycle, with maintenance support terminating on 31 May 2029 (full support ended 31 May 2024).
• •SQL Server 2019: Extended support expires in 2030, concluding its 10-year window.
• •RHEL 10: Full support concludes on 31 May 2030, with maintenance support running until 31 May 2035.
• •SQL Server 2022 and 2025: Extended support ends in 2033 and 2036, respectively, reflecting Microsoft's 5-year mainstream and 5-year extended support policy.

The Financial and Compliance Impact of Unsupported Systems in the UK

Operating systems and databases past their support dates generates steep direct and indirect expenses for UK organisations. From a commercial standpoint, attempting to maintain legacy environments without vendor backing often demands bespoke premium support contracts or expensive vendor uplifts. When extended security patches must be sourced as a stopgap, software publishers charge substantial premiums that escalate on an annual basis. In practice, UK buyers must align end-of-support calendars with procurement lead times, datacentre exit plans, Extended Security Updates (ESU) or vendor uplift costs, and sterling-based budget approval well before the final support deadline to ensure estates do not strand supported software on unsupported hardware.

Beyond commercial uplifts and recurring ESU licensing bills, the governance exposure detailed earlier carries direct legal liability. UK regulatory bodies evaluate whether organisations took reasonable technical measures to secure customer data; running unpatched operating systems or databases past vendor support without compensating controls severely undermines any defence during an Information Commissioner's Office (ICO) inquiry. Mitigating these exposures requires calculating projected Windows Server EOL costs early to justify modernisation budgets before security audits turn into formal compliance actions.

A Practical Decision Framework for UK IT Leaders

Managing software lifecycles across mixed estates requires a systematic decision framework. Rather than reacting as deadlines arrive, IT leaders should assess platforms according to workload criticality, regulatory exposure, and technical dependency.

First, audit all running installations against vendor lifecycle databases. Second, establish whether the workload requires functional innovation or purely security maintenance; platforms entering extended support, such as Windows Server 2022 in October 2026, can continue operating securely if no new features are needed. Third, evaluate dependencies on underlying server platforms. Checking your estate against server end-of-life dates ensures you do not migrate modern software onto legacy hardware nearing vendor abandonment. Finally, evaluate whether to upgrade in-place, replatform to a newer release line such as RHEL 9 or 10, or transition virtual workloads to alternate hypervisors.

Hybrid Infrastructure and Infrastructure Modernisation

Modern infrastructure planning spans both on-premises data centres and cloud hosting providers. When managing lifecycle transitions in hybrid environments, teams must factor in vendor-specific hosting rules. Certain public cloud providers offer distinct Extended Security Update (ESU) support agreements for legacy Windows Server workloads running natively within their hypervisors, whereas on-premises deployments require distinct licensing mechanics.

Hypervisor refresh cycles add an extra layer of complexity. With VMware vSphere 8.0 general support running until 10 October 2027 and extended support extending to 11 October 2029, infrastructure teams must determine whether their existing physical host estate can support vSphere upgrades. Deployments utilising open platforms such as Proxmox VE 8 and 9 provide alternative virtualisation roadmaps, with current release‑line support horizons extending into 2028 and 2029, giving engineering teams viable paths to modernise their computing layers alongside their base operating systems.

Long-Term Lifecycle Strategy and Bridging Solutions

Proactive planning means maintaining continuous visibility over software horizons 3 to 5 years in advance. Organisations that delay migrations often find themselves struggling with talent and resourcing constraints. Engineers with deep expertise in legacy systems become scarce, while modern engineering talent prefers working with contemporary distributions such as RHEL 9/10, modern Ubuntu LTS releases, and current database engines.

When business-critical applications cannot be refactored before an operating system or hypervisor support cutoff, bridging strategies must be deployed. Segmenting legacy systems into isolated network enclaves with restricted ingress and egress can temporarily reduce security exposure. Concurrently, evaluating third-party maintenance options for physical infrastructure ensures that bare-metal systems remain stable and covered while software transformation projects run their course.

Methodology

This data study compiles verified enterprise software lifecycle dates for major server operating systems, relational database management systems, and hypervisors. Information was gathered directly from official vendor support portals, including Microsoft Learn lifecycle directories, Red Hat Enterprise Linux lifecycle documentation, Canonical Ubuntu release cycle disclosures, and Broadcom VMware support roadmaps.

All lifecycle milestones and support policies cited here reflect vendor information audited and verified as of September 2026. The analysis strictly distinguishes between support tiers—such as mainstream support, extended support, full support, maintenance support, and standard LTS horizons—to prevent conflation between functional feature retirement and complete security patch termination.

UK regulatory context was cross-referenced with operational guidance published by the National Cyber Security Centre (NCSC) and UK Cyber Essentials requirements regarding software vulnerability management and vendor patch availability.

Sources

Every figure in this article traces to the sources below.

• •Microsoft — Windows Server 2022 Support Dates
• •Microsoft — Lifecycle End of Support 2026 Directory
• •Microsoft — SQL Server End of Support Lifecycle Overview
• •Microsoft — Fixed Lifecycle Policy Specification
• •end-of-life.org — Red Hat Enterprise Linux Lifecycle Tracker
• •Canonical — Ubuntu Release Cycle and Maintenance Roadmap
• •Broadcom — VMware vSphere Lifecycle and Support Policies