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 for | Teams 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 get | Signed 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 cover | Windows PowerShell 5.1, Windows itself, and modules that ship outside the PowerShell package |
| How it is priced | Per application. Ask for a quote. |
| What happens next | You 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
Trusted globally by enterprises





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.
| Version | Released | .NET | End of support | Last release |
|---|---|---|---|---|
| PowerShell 7.2 (LTS) | 8 Nov 2021 | .NET 6 | 8 Nov 2024 | 7.2.24 (22 Oct 2024) |
| PowerShell 7.3 | 9 Nov 2022 | .NET 7 | 8 May 2024 | 7.3.12 (11 Apr 2024) |
| PowerShell 7.4 (LTS) | 16 Nov 2023 | .NET 8 | 10 Nov 2026 | 7.4.22 (25 Oct 2026) |
| PowerShell 7.5 | 23 Jan 2025 | .NET 9 | 10 Nov 2026 | 7.5.13 (25 Oct 2026) |
| PowerShell 7.6 (LTS) | 18 Mar 2026 | .NET 10 | 14 Nov 2028 | 7.6.10 (10 Nov 2026) |
| PowerShell 7.7 | 10 Nov 2026 | .NET 11 | No 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 →
Why a .NET end date ended PowerShell 7.4 and 7.5
PowerShell is a .NET application, and Microsoft ties its support dates to the runtime underneath. That is why a scripting tool lost support in a week that .NET teams already had marked.
- Microsoft's lifecycle page says the end-of-support dates follow the .NET support policy for the .NET version the PowerShell release was built upon. PowerShell 7.4 LTS is .NET 8 and PowerShell 7.5 is .NET 9.
- .NET 8 is a long-term support release and .NET 9 a standard-term release that Microsoft gave 24 months, so both ended on 10 November 2026. PowerShell 7.4 and 7.5 ended on the same day. The reasons are on the .NET 8 and .NET 9 end-of-life pages.
- The release build shows the link. The 7.4.22 release notes record a build update to .NET SDK 8.0.427, and the release carries standard builds next to separate framework-dependent (fxdependent) builds. Patching the .NET installed on a host therefore does not necessarily patch a standard pwsh, which brings its own runtime.
- A team that already planned .NET 8 and 9 patching has a PowerShell question as well. Look for pwsh in build agents, runbook hosts, container images and anything that shells out to it.
- PowerShell 7.6 LTS is built on .NET 10 and is supported to 14 November 2028. Upgrading is the permanent fix. Patching 7.4 and 7.5 covers the time it takes to retest scripts and roll 7.6 out.
Sources: Microsoft's PowerShell Support Lifecycle page, the PowerShell GitHub releases page and endoflife.date, read on 19 November 2026.
.NET end of life dates →.NET 8 end of life →.NET 9 end of support →.NET extended support →
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.
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.
| Version | Status | Active CVEs |
|---|---|---|
| 7.4 (LTS)(Support ended 10 Nov 2026. Last release 7.4.22) | EOL | See advisories |
| 7.5(Support ended 10 Nov 2026. Last release 7.5.13) | EOL | See advisories |
| 7.6 (LTS)(Microsoft support to 14 Nov 2028. Assessed case by case.) | Current | See advisories |
| 7.7(Released 10 Nov 2026. Assessed case by case.) | Current | See 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
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.
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.
Prefer to talk or read more first?