PowerShell 7.4 End of Life: November 10, 2026, Same Day as 7.5
PowerShell 7.4 reaches end of life (EOL) on November 10, 2026. That is the end-of-support date in the table on Microsoft's PowerShell support lifecycle page, and PowerShell 7.5 ends on the same day, November 10, 2026. The two releases end together because PowerShell's support dates follow the .NET each release is built on: 7.4 runs on .NET 8 and 7.5 on .NET 9, and both of those reach end of support on November 10, 2026, as covered in our .NET 8 and .NET 9 end of life guide. PowerShell 7.4 shipped on November 16, 2023 as a Long Term Servicing (LTS) release; 7.5 shipped on January 23, 2025 as a Stable release. The upgrade target is PowerShell 7.6, the current LTS release, which Microsoft lists as supported until November 14, 2028.
What ends on the day
Microsoft's lifecycle page is direct about what end of support means for PowerShell: "After a version of PowerShell reaches end-of-life, no further updates, including security updates, are provided. Microsoft encourages customers to upgrade to a supported version of PowerShell to continue receiving updates and support." Until the end date, the page says "Both LTS and Stable releases of PowerShell receive security updates and bug fixes." It also says "Microsoft only supports the latest update version of a release", so a 7.4 or 7.5 installation that is behind on its own updates is not supported even before November 10, 2026.
PowerShell follows the Microsoft Modern Lifecycle Policy. There is no extended-support phase on the page and no paid extension listed for a PowerShell release: the table gives one end-of-support date per version, and that is the whole lifecycle. Support for a given installation also ends earlier if the operating system under it ends first: the page says "Support for PowerShell ends when either of the following conditions are met: The target platform reaches end-of-life as defined by the platform owner; The specific version of PowerShell reaches end-of-life."
The dates, in one table
The three current releases from Microsoft's end-of-support table, with the .NET each one is built on. Status badges are recomputed from our data at every build.
| Version | Released | Track | End of support | .NET | Status |
|---|---|---|---|---|---|
| PowerShell 7.6 | March 18, 2026 | LTS | November 14, 2028 | .NET 10 | Supported |
| PowerShell 7.5 | January 23, 2025 | Stable | November 10, 2026 | .NET 9 | Approaching |
| PowerShell 7.4 | November 16, 2023 | LTS | November 10, 2026 | .NET 8 | Approaching |
Microsoft's page also lists PowerShell 7.7 as a preview release built on .NET 11, with no release or end-of-support date. The page says "Preview versions aren't officially supported" and that "you shouldn't use them in production environments", so 7.7 is not an upgrade target today.
LTS and Stable: what the two tracks mean
Microsoft defines the two tracks on the lifecycle page. An LTS release "is an LTS release of .NET. Updates to an LTS release only contain critical security updates and servicing fixes that are designed to minimize impact on existing workloads." A Stable release "is a release that occurs between LTS releases. Stable releases can contain critical fixes, innovations, and new features. Microsoft supports a Stable release for about six months after the next LTS release."
That last sentence is why 7.5 ends when it does. PowerShell 7.6, the next LTS after 7.5, shipped on March 18, 2026; about six months later would put the Stable release's end in the autumn of 2026, and the table pins it to the .NET 9 date, November 10, 2026. On the LTS side, the page names 7.6 as the current LTS release and says the previous LTS release, 7.4, "is still supported until" November 10, 2026. The current patch level of each release is on our PowerShell page.
Why 7.4 and 7.5 end together: the .NET dependency
Microsoft's page states the rule in one sentence: "The end-of-support dates follow the .NET Support Policy for the version of .NET that the release of PowerShell was built upon." The table repeats it: "The PowerShell support lifecycle follows the support lifecycle of .NET." PowerShell 7.4 is built on .NET 8.0 and PowerShell 7.5 on .NET 9.0.
.NET 8 is a .NET LTS release that shipped on November 14, 2023 and ends on November 10, 2026. .NET 9 is a standard-term release that shipped on November 12, 2024 and ends on November 10, 2026, the same day. Because each PowerShell release inherits its .NET's end date, the PowerShell LTS and the Stable release that followed it end on the same day. The .NET side of this is in our .NET 8 and .NET 9 end of life guide; the next .NET LTS, .NET 10, is the runtime under PowerShell 7.6 and ends on November 14, 2028, which is also the PowerShell 7.6 date.
What to do before the date
- Find every 7.4 and 7.5 install. Run
$PSVersionTable.PSVersionon each host, and check build agents, containers and the PowerShell inside automation tools, not only interactive shells. Microsoft's page gives[System.Runtime.InteropServices.RuntimeInformation]::FrameworkDescriptionto show the .NET version a given PowerShell is running on. - Move to PowerShell 7.6. It is the current LTS release, built on .NET 10, and Microsoft lists its end of support as November 14, 2028. Install the newest 7.6 update: Microsoft only supports the latest update version of a release.
- Check the operating system in the same pass. Support for a PowerShell install also ends when its platform does. Microsoft's page lists the supported macOS, Alpine, Debian, RHEL and Ubuntu releases with their own end dates, and for Windows it says Microsoft supports PowerShell until PowerShell reaches end of support or the version of Windows does.
- Leave Windows PowerShell 5.1 out of this plan. Microsoft's page says: "This document is about support for PowerShell, not Windows PowerShell. Windows PowerShell is a component of the Windows operating system and is subject to the Windows support lifecycle." Scripts on Windows PowerShell 5.1 follow the dates of the Windows release they run on, not the November 10, 2026 date.
- Plan the .NET move alongside it. If your own applications run on .NET 8 or .NET 9, they end the same day. Our .NET 8 and .NET 9 guide covers that side; our EOL Checker and API answer the rest of the stack.
Frequently Asked Questions
When is PowerShell 7.4 end of life?
PowerShell 7.4 reaches end of support on November 10, 2026, per Microsoft's PowerShell support lifecycle page. Microsoft's page says that after a version of PowerShell reaches end-of-life, no further updates, including security updates, are provided.
Is PowerShell 7.5 end of life on the same day?
Yes. PowerShell 7.5 reaches end of support on November 10, 2026, the same day as PowerShell 7.4. Microsoft's table lists 7.5 as a Stable release built on .NET 9.0 and 7.4 as an LTS release built on .NET 8.0.
Why do PowerShell 7.4 and 7.5 end on the same day?
Because Microsoft ties each PowerShell release to the .NET it is built on. Microsoft's page says the end-of-support dates follow the .NET Support Policy for the version of .NET that the release of PowerShell was built upon. PowerShell 7.4 runs on .NET 8 and PowerShell 7.5 runs on .NET 9, and both of those .NET releases reach end of support on November 10, 2026.
What should I upgrade PowerShell 7.4 or 7.5 to?
PowerShell 7.6, the current LTS release. It shipped on March 18, 2026, is built on .NET 10, and Microsoft's table lists its end of support as November 14, 2028. Microsoft only supports the latest update version of a release, so install the newest 7.6 update.
Does this affect Windows PowerShell 5.1?
No. Microsoft's page states that it covers PowerShell, not Windows PowerShell: Windows PowerShell is a component of the Windows operating system and is subject to the Windows support lifecycle. Support for Windows PowerShell 5.1 is provided through Windows support channels, so its dates are those of the Windows release it ships with.
Related
- PowerShell 7.4 — the live status page with its EOL Risk Score
- PowerShell — every version's release and end-of-support dates
- .NET 8 and .NET 9 End of Life — the runtimes under 7.4 and 7.5, ending the same day
- How we verify our dates — the rules every number on this site is held to