Microsoft Ships Three PowerShell Updates in One Evening, but the Real Story Is a November 10 Deadline
Microsoft's PowerShell team rolled out three servicing updates on the same night. PowerShell 7.6.7, 7.5.12, and 7.4.21 all dropped on October 13, 2026, carrying essentially the same pair of fixes. The news isn't the patches, though. It's that two of these branches are about to age out completely, and the clock is ticking down to roughly four weeks.
The timing is what makes this batch worth a look. Both the previous LTS, 7.4, and the stable line, 7.5, lose all support, including security updates, on November 10, 2026. That means anything still running 7.4 or 7.5 goes unserviced less than a month away, and Microsoft only officially supports the latest patch of a given branch anyway.
The releases landed late in the evening, UTC. 7.4.21 came out first at 20:03, followed by 7.5.12 at 20:05, and the current LTS, 7.6.7, at 20:37. All three were published by maintainer jshigetomi, and the user-facing changes were backported across every actively supported line, which is standard servicing practice. You're getting the same resilience and corrections whether you're on the old LTS or the newest one.
The shared fixes are deliberately small. Both are the kind of thing you rarely notice when they work, and only care about when they break.
The two changes, spelled out
The first is a tolerance improvement for the per-user powershell.config.json file. That's the settings file that lives in your profile area, not the system-wide $PSHOME. Before this patch, PowerShell could fail hard if that file had a corrupt or half-written copy, the sort of thing that happens with roaming profiles, network-shared home directories, or sync tools that leave files mid-write. Now it tolerates the I/O and JSON errors instead. It's a meaningful real-world improvement, though Microsoft stopped short of saying exactly which errors are swallowed and whether they're now logged, ignored, or flagged as a warning. This isn't the first time the team has touched this area either, with 7.5.7 making a related change earlier this year.
The second fix lands in Show-Command, the Windows-only cmdlet that opens a graphical form for building a command line. It adds a GetImportModuleCommand method plus a session-restriction check. The notes don't spell out which restriction modes are affected, so if you run constrained sessions or JEA-style endpoints and anything depends on Show-Command, test it before rolling this out broadly.
What to actually do
If you're on 7.4 or 7.5, treat these updates as a stopgap, not a solution. They don't extend the November 10 deadline, and there's no CVE attached here, so this isn't a security release in the way people usually mean. The migration to PowerShell 7.6 LTS is the actual move. 7.6 runs on .NET 10 and stays supported until November 2028, which is a far healthier place to be when 7.4 and 7.5 are already looking over their shoulders.
Figuring out how PowerShell was installed is straightforward. Run $PSHOME in a pwsh session and see what comes back. ProgramFiles\PowerShell\7 means an MSI install, a WindowsApps path points to the MSIX or Store package, .dotnet\tools signals a .NET global tool, and anything else is probably a ZIP extract. Upgrade using whatever method you installed with, since newer builds replace the older ones in place.
WinGet is the path of least resistance for most people, though there's a wrinkle worth knowing. The default WinGet package follows the current channel, so it'll happily drop you onto 7.6. If you need to stay on 7.4, grab the 7.4.21 MSI directly from GitHub instead. Enterprise and Windows Server environments should stick with the MSI for now, since Store-based MSIX installs don't support remoting into the machine, a limitation that's been around for a while.
Verify after updating by opening a fresh session and running $PSVersionTable.PSVersion. To confirm the underlying runtime, check [System.Runtime.InteropServices.RuntimeInformation]::FrameworkDescription. And before you push anything out, verify checksums. Each release page publishes a hashes.sha256 file alongside per-asset hashes. A SHA-256 value for the ZIP or the ARM64 MSI tells you nothing about the x64 MSI, so match the hash to the exact filename you're deploying.
The version picture
7.6.7 is the current LTS, built on .NET 10, and it picked up a few extras beyond the shared fixes, WPF key gesture localization, an AutoSize formatting option, and special MSIX handling when prepending to PATH. 7.5.12 stays on the .NET 9 runtime, though the build SDK was bumped. 7.4.21 is the most surgical of the three: two behavioral fixes plus some release-pipeline cleanup, including moving to a newer native package and dropping Windows PowerShell 5.1 from its own CI.
One thing worth flagging, even though it's a bit of a tangent. The public trackers haven't caught up yet. endoflife.date as of September 9 still showed the pre-October builds, and Microsoft's own support page, last touched in August, still lists 7.4.20 and 7.5.11 as the latest. Expect both to update. If you're relying on those tools to tell you you're current, you might be wrong for a while.
Also, don't read these patches as any kind of signal that Windows PowerShell 5.1 is changing. The "stop using 5.1" note applies only to the PowerShell project's build pipeline. 5.1 still ships inside Windows, and it's governed by the Windows lifecycle, not by PowerShell 7's calendar.
Release v7.6.7 Release of PowerShell · PowerShell/PowerShell
7.6.7 Engine Updates and Fixes Tolerate IO/JSON errors reading the per-user powershell.config.json (#28084) General Cmdlet Updates and Fixes Prevent localization of WPF key gesture strings (#280...
Release v7.6.7 Release of PowerShell · PowerShell/PowerShell
Release v7.5.12 Release of PowerShell · PowerShell/PowerShell
7.5.12 Engine Updates and Fixes Tolerate IO/JSON errors reading the per-user powershell.config.json (#28070) General Cmdlet Updates and Fixes Add GetImportModuleCommand method and session restri...
Release v7.5.12 Release of PowerShell · PowerShell/PowerShell
Release v7.4.21 Release of PowerShell · PowerShell/PowerShell
7.4.21 Engine Updates and Fixes Tolerate IO/JSON errors reading the per-user powershell.config.json (#28048) General Cmdlet Updates and Fixes Add GetImportModuleCommand method and session restri...
Release v7.4.21 Release of PowerShell · PowerShell/PowerShell
