POWERSHELL 7 COVERAGE

PowerShell 7.4 and 7.5 reached end of support on 10 November 2026. Your patching does not have to.

PowerShell 7.4 LTS and 7.5 reached end of support on 10 November 2026, the same day as .NET 8 and .NET 9, because each PowerShell release ends when its .NET runtime does. The last releases are 7.4.22 and 7.5.13 (25 October 2026). OSSeva patches PowerShell 7.4 and 7.5, with Critical fixes within 48 hours.

Who it is forTeams running PowerShell 7.4 or 7.5 in CI agents, container images, automation runbooks or inside a product, that cannot move to 7.6 yet
What you getSigned patched builds on the line you run, with scripts, modules and the .NET runtime version unchanged. Assure adds an inventory of pwsh installs and a 7.6 upgrade plan.
What it does not coverWindows PowerShell 5.1, Windows itself, and modules that ship outside the PowerShell package
How it is pricedPer application. Ask for a quote.
What happens nextYou send your work email, we confirm your PowerShell version and how it is installed, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

PowerShell 7 support status by version, read on 19 November 2026

Dates are from Microsoft's PowerShell support lifecycle page. The end date of each PowerShell release is the end date of the .NET release it is built on.

VersionReleased.NETEnd of supportLast release
PowerShell 7.2 (LTS)8 Nov 2021.NET 68 Nov 20247.2.24 (22 Oct 2024)
PowerShell 7.39 Nov 2022.NET 78 May 20247.3.12 (11 Apr 2024)
PowerShell 7.4 (LTS)16 Nov 2023.NET 810 Nov 20267.4.22 (25 Oct 2026)
PowerShell 7.523 Jan 2025.NET 910 Nov 20267.5.13 (25 Oct 2026)
PowerShell 7.6 (LTS)18 Mar 2026.NET 1014 Nov 20287.6.10 (10 Nov 2026)
PowerShell 7.710 Nov 2026.NET 11No date on Microsoft's table (listed as preview)7.7.0 (10 Nov 2026)

Last-release dates are from endoflife.date and the GitHub releases page. Microsoft's table lists PowerShell 7.7 as a preview with no dates; endoflife.date lists it with the .NET 11 line.

Microsoft: PowerShell Support Lifecycle →endoflife.date PowerShell data →PowerShell releases on GitHub →

What is and is not covered

PowerShell the name covers two products with different owners and lifecycles. OSSeva covers one of them.

  • Covered: PowerShell 7, the open-source, cross-platform shell from github.com/PowerShell/PowerShell, released under the MIT licence.
  • Not covered: Windows PowerShell 5.1. Microsoft's page states it is a component of the Windows operating system and subject to the Windows support lifecycle. OSSeva does not patch Windows.
  • Not covered: modules that ship outside the PowerShell release package. Microsoft's page gives the ActiveDirectory module that ships with Windows Server as an example.
  • Not a replacement for the platform: a supported PowerShell build does not change whether the operating system it runs on is supported. Microsoft ties PowerShell support to both the PowerShell version and the OS version.

Source: Microsoft's PowerShell Support Lifecycle page, read on 19 November 2026.

.NET support →.NET lifecycle hub →

Why now

7.4 and 7.5 ended on 10 November 2026, with .NET 8 and .NET 9

Microsoft's PowerShell lifecycle page lists 10 November 2026 as end of support for both PowerShell 7.4 LTS and 7.5. After end of life, the page says, no further updates, including security updates, are provided. The last releases are 7.4.22 and 7.5.13, both published on 25 October 2026.

The date comes from .NET, not from PowerShell

Each PowerShell release is built on a .NET runtime and ends when that runtime does. 7.4 is built on .NET 8 and 7.5 on .NET 9, and Microsoft ended both .NET lines on 10 November 2026. PowerShell 7.6 LTS is built on .NET 10 and runs to 14 November 2028.

Pipelines, images and runbooks pin an old pwsh

PowerShell 7 is often installed once into a CI agent image, a container base image or an automation runbook and then left alone. Those pins are the copies that stay on 7.4 or 7.5 after the end date, and the ones a vulnerability scanner flags first.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
7.4 (LTS)(Support ended 10 Nov 2026. Last release 7.4.22)EOLSee advisories
7.5(Support ended 10 Nov 2026. Last release 7.5.13)EOLSee advisories
7.6 (LTS)(Microsoft support to 14 Nov 2028. Assessed case by case.)CurrentSee advisories
7.7(Released 10 Nov 2026. Assessed case by case.)CurrentSee advisories

Running a PowerShell version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for PowerShell 7.4 and 7.5 after end of life.

  • Backported security fixes for PowerShell 7.4 and 7.5
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and a PowerShell 7.6 upgrade plan.

  • Everything in Patch
  • Inventory of pwsh installs across images, agents and runbooks
  • PowerShell 7.6 upgrade path assessment and script compatibility review
  • SOC 2 / HIPAA attestation package
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 application and runtime monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Is PowerShell 7.4 end of life?

Yes. Microsoft ended support for PowerShell 7.4 LTS on 10 November 2026, the same day as .NET 8, the runtime it is built on. The last release is 7.4.22, published on 25 October 2026.

When does PowerShell 7.5 reach end of life?

PowerShell 7.5 reached end of support on 10 November 2026, together with .NET 9. The last release is 7.5.13, published on 25 October 2026. PowerShell 7.6 LTS is supported until 14 November 2028.

Why do PowerShell 7.4 and 7.5 end on the same day?

Microsoft's lifecycle page says PowerShell's end-of-support dates follow the .NET support policy for the .NET version each release was built on. 7.4 uses .NET 8 and 7.5 uses .NET 9, and Microsoft ended both .NET lines on 10 November 2026.

Which PowerShell versions does OSSeva patch?

PowerShell 7.4 and 7.5 after end of life. Other versions are assessed case by case through a version coverage check. OSSeva covers the open-source PowerShell 7 only.

Does OSSeva patch Windows PowerShell 5.1?

No. Windows PowerShell 5.1 is a component of Windows and follows the Windows support lifecycle, as Microsoft's PowerShell lifecycle page notes. OSSeva patches the open-source PowerShell 7 from github.com/PowerShell/PowerShell, not Windows or its components.

Who provides PowerShell support after end of life?

Microsoft's page says that after a version reaches end of life no further updates, including security updates, are provided, and that PowerShell is MIT-licensed with community support unless you hold a paid support agreement. Third-party providers, OSSeva among them, patch the ended lines. Ask each which versions it covers.

Should I upgrade to PowerShell 7.6 instead of buying patches?

If scripts run unchanged on 7.6 and you can roll it out to every agent, image and runbook, upgrade; 7.6 LTS runs to 14 November 2028. Patching helps where a pinned version cannot move yet, for example a validated image or a product that bundles pwsh.

How is OSSeva PowerShell support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get PowerShell patched and supported?

Tell us your PowerShell versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call