Loosely Decoupled
ComparisonUnattended

PowerShell LTS vs. Stable: Which Release to Install

LTS lets your scripts run for years on security fixes alone, while Stable trades that stability for new features and an upgrade every time a new LTS ships.

A woman works calmly at her desk under a plain cyan lamp. At the next desk a man in a hoodie, coffee in hand, unpacks another new lamp beside a heap of boxes and barely used lamps.
On this page

TL;DR

Install the LTS release for any script that runs unattended. Pick the Stable release only if you need a feature your LTS release lacks and you can upgrade on time. Stable support ends about six months after the next LTS release. Microsoft’s end-of-support table gives the date.

Microsoft sorts PowerShell 7 releases into two types, LTS and Stable. The difference decides what an update can change on a machine you don’t watch, and how soon you have to move to a newer release. The definitions here come from Microsoft’s PowerShell support lifecycle (opens in a new tab) page.

Release types

An LTS release of PowerShell is an LTS release of .NET. Microsoft’s page says “a stable release is a release that occurs between LTS releases.”

Find out which type you have

Microsoft’s page gives one command that shows the version of .NET your PowerShell was built on. In the PowerShell 7 session you want to check, run:

PowerShell
[System.Runtime.InteropServices.RuntimeInformation]::FrameworkDescription

Match the .NET version it prints against the .NET Version column of the two end-of-support tables on the lifecycle page, one for current versions and one for retired versions. A row marked LTS is an LTS release. A row marked preview is a preview release, which Microsoft doesn’t officially support. A row with neither mark is a Stable release. The same row gives the date its support ends.

Windows PowerShell 5.1 is neither type. Microsoft’s page says Windows PowerShell is a component of Windows and is subject to the Windows support lifecycle, so it has no row in these tables.

What an update contains

Updates to an LTS release contain only critical security updates and servicing fixes. Microsoft designs them to minimize the impact on existing workloads.

Stable releases can contain critical fixes, innovations and new features.

How long support lasts

An LTS release follows the .NET support policy for the version of .NET it was built on.

Microsoft supports a Stable release for about six months after the next LTS release.

The dates change with every release. Read them in the end-of-support table on Microsoft’s lifecycle page, not in a copy of it.

What you must do to stay supported

Apply updates to either type. Microsoft only supports the latest update of a release.

On LTS, that’s all you must do until the end-of-support date in the table.

On Stable, you must also plan a move to a newer release, because support ends about six months after the next LTS release.

Before either type reaches its end-of-support date, move to the current LTS release that Microsoft’s lifecycle page names. While the previous LTS release is still supported, the page names it too, with the date its support ends.

Choose LTS for scripts that run unattended

Choose LTS when a host should go untouched between updates. An update to an LTS release adds security updates and servicing fixes, not new features, so it changes as little as possible on a machine nobody watches. The catch is that a feature your release lacks doesn’t arrive until you move to the next LTS release.

Choose Stable when you need a new feature

Choose Stable when you need a feature your LTS release doesn’t have, and you can plan a move to a newer release. Stable support ends about six months after the next LTS release, so a host you rarely touch will outlive the support window.

Whichever type you pick, check what your caller sees after an upgrade. PowerShell -File vs. -Command: Which Exit Code Does the Caller Get? covers what a scheduled task receives from your script.

Sources

New articles, by email.

A short note when something new is published.