How-To

PowerShell 7.4 and 7.5 both stop getting fixes on 10 November: moving to 7.6

AusGeek · · 6 min read

If you've got scheduled tasks, backup scripts or a homelab box running PowerShell 7, check the version this week. On 10 November 2026 PowerShell 7.4 reaches end of support, and so does 7.5. That leaves 7.6 as the only supported PowerShell 7 release. The upgrade is quick on most machines. Finding every machine that needs it is the slow part.

This isn't a big dramatic deadline. Scripts won't stop running on the 11th. They just won't get security fixes any more, and a shell that runs unattended with admin rights is exactly the thing you want patched.

Why two versions end on the same day

PowerShell 7 doesn't have its own support calendar. Microsoft's support lifecycle page says its end-of-support dates "follow the .NET Support Policy for the version of .NET that the release of PowerShell was built upon". 7.4 is built on .NET 8 and 7.5 on .NET 9, and the .NET team's announcement puts both of those runtimes out of support on 10 November 2026. (.NET 9's support window was stretched from 18 months to 24, which is how it ended up on the same date as .NET 8.)

Microsoft's lifecycle listing for PowerShell shows both 7.4 (LTS) and 7.5 ending together, and 7.6 (LTS) running to November 2028. PowerShell 7.6 went GA on 18 March 2026 on .NET 10.

The bit worth noticing: plenty of people moved from 7.4 to 7.5 because it was newer, and reasonably assumed that bought them time. It didn't. If you're on 7.5, you're on the same clock as 7.4.

One thing this doesn't touch is Windows PowerShell 5.1, the blue powershell.exe that ships with Windows. The lifecycle page is explicit that 5.1 is a Windows component and follows the Windows support lifecycle. This is only about pwsh.

Step one: find out what you're running

In each PowerShell 7 session (or as the first line of a script's log output), check the version:

$PSVersionTable.PSVersion

$PSVersionTable is a built-in variable, and PSVersion is the field you care about. Anything starting 7.4 or 7.5 needs moving. At the time of writing the current LTS patch is 7.6.6.

Then work out how it was installed, because the docs are clear that you should upgrade using the same method you installed with. The Windows install page gives a neat trick for this: look at $PSHOME.

The ZIP installs are the ones I'd hunt for first. Nothing updates them, and they're usually on the machine someone set up once and never looked at again.

Upgrading on Windows

If WinGet is available (it ships with Windows 11 and Windows Server 2025 with Desktop Experience, but not Server 2022 or earlier, per the docs), check for an upgrade:

winget list --id Microsoft.PowerShell --upgrade-available

And then:

winget upgrade --id Microsoft.PowerShell

Per the docs, WinGet keeps the package format you already have, MSI or MSIX. There's a change worth knowing about for fresh installs, though: starting with the 7.6.0 WinGet package, a plain winget install gives you the MSIX by default. If you want the MSI, ask for it:

winget install --id Microsoft.PowerShell --source winget --installer-type wix

This matters more than it looks. The docs list real limits on the MSIX build: it installs per user, can't be used as a target for PowerShell remoting, and can't run commands that need write access to $PSHOME, such as Set-ExecutionPolicy -Scope LocalMachine or Update-Help -Scope AllUsers. For a desktop that's fine. For a server or a machine running scheduled jobs under a service account, I'd pick the MSI without thinking about it. The same page also notes that from 7.7 there won't be an MSI at all, so this choice has a shelf life.

The MSI can also opt in to updates through Microsoft Update (USE_MU=1 and ENABLE_MU=1 are the defaults in the docs' silent-install example). If you've got machines you'd rather not visit again, that's the option that saves you doing this whole exercise next time.

Upgrading on Linux and macOS

On Ubuntu and Debian, Microsoft's preferred route is its own package repository at packages.microsoft.com. The Ubuntu install page registers that repo and then installs the powershell package with apt. If you're already set up that way, the docs' final step is the one you need:

sudo apt-get update
sudo apt-get install -y powershell

If a machine set up from that repo is somehow still on 7.4, something is holding it back (a hand-installed .deb, or a pinned version), and that's worth understanding before you force it. For a manual install, the same page links the 7.6 .deb straight from the GitHub releases (powershell_7.6.6-1.deb_amd64.deb at the time of writing) and installs it with dpkg -i followed by apt-get install -f to sort out dependencies.

The Ubuntu page also flags a gotcha that has nothing to do with PowerShell: adding Microsoft's repo means you now have two sources of .NET packages, which can cause problems if you also install .NET for other things. The docs link to guidance on setting repo priority. Worth a read if that box also runs .NET apps.

On macOS, the install page recommends the PKG from the releases page (notarised and signed by Microsoft since the May 2026 releases), with Arm64 and x64 builds of 7.6. If you installed through Homebrew originally, the docs point you to their alternate-install page instead.

On every platform, a newer PowerShell 7 replaces the older one in place. If you genuinely need 7.4 and 7.6 side by side while you test, the docs say to put the old one in a separate folder using the ZIP or tarball method.

What might break

Not much, by the look of the release notes. I haven't run anyone's scripts against it, so here's what the docs flag.

From the 7.6 release notes:

If you're jumping straight from 7.4, the 7.5 release notes apply too. The two I'd look for: Test-Path used to ignore -OlderThan when you also passed -NewerThan with -PathType (so a date-range check may start returning different results now that it's fixed), and ConvertTo-Json now writes a BigInteger as a number rather than an object.

My approach would be boring: upgrade one machine, run the scheduled jobs by hand, read the logs, then do the rest. And grep your scripts for ThreadJob\ and Test-Path with -OlderThan before you start, because that's a two-minute check that covers the likely trouble.

The short version

On most machines this should be a short job. The hard part is remembering the Raspberry Pi in the cupboard that runs one PowerShell script at 3am.