Microsoft Replace modifications for PowerShell 7

It has been some time since we’ve up to date of us on the newest behaviors for Microsoft Replace! This
publish provides some background on Microsoft Replace, explains our replace guidelines, and pronounces our plans
for updating your installs of PowerShell 7.2.

About Microsoft Replace

Microsoft Replace (MU) is a service that gives automated updates for Microsoft services and products. We first began utilizing MU in PowerShell 7.2. MU supplies a handy option to routinely replace PowerShell 7, which ensures you possibly can management your replace schedule, check it towards your atmosphere, and scale throughout your enterprise with ease.

Enabling MU

Throughout MSI set up, two checkboxes management replace settings:

• Allow updates for PowerShell by means of Microsoft Replace or WSUS (beneficial)
  Permits the system to obtain updates for PowerShell 7 by means of Microsoft Replace, Home windows Server
  Replace Providers (WSUS), or System Middle Configuration Supervisor (SCCM).
• Allow Microsoft Replace once I verify for updates (beneficial)
  Permits the system to obtain updates for all supported Microsoft software program, not simply Home windows.

We suggest that you choose each choices to make sure complete replace protection.

If you wish to set these choices whereas putting in PowerShell from the command line, you will discover
detailed directions within the PowerShell documentation.

Replace Availability

After we launch a brand new PowerShell model, it may well take as much as two weeks earlier than the replace is
obtainable by means of Microsoft Replace. We try to publish the replace no later than 2 weeks after the
GitHub launch, however there is no such thing as a assure. There could also be circumstances that delay the replace. If you happen to
want the replace earlier than it’s obtainable by way of MU, you possibly can obtain it immediately from the
PowerShell Releases web page on GitHub.

What’s the anticipated conduct of MU?

We outlined the foundations for updates in an intentional means to make sure that customers who’re utilizing LTS
variations keep on LTS variations. Which means that you won’t be up to date to the newest model of
PowerShell 7 whenever you anticipated.

These are the foundations for updates:

• In case you are operating 7.4 (LTS), you’ll obtain updates to 7.4 (LTS)
• In case you are operating 7.5 (secure), you’ll obtain updates to 7.5 (secure)
• In case you are operating any preview or launch candidate (rc) model, you’ll obtain updates to subsequent
  newest preview model as they arrive out.

We’ll by no means replace an LTS model to a secure non-LTS model, like 7.4 to 7.5. Nevertheless, a secure
non-LTS launch WILL be upgraded to the upper LTS launch when assist for the secure launch
ends. The one time we replace an LTS model to a distinct model could be when an LTS model is
out of assist. For instance, we are going to replace 7.4 to 7.6 (subsequent LTS) as soon as 7.4 goes out of assist.

Preview variations won’t ever be up to date to the newest secure model. As a substitute, we are going to replace you to
the newest preview launch. This implies if you’re on 7.5-rc.1 you can be up to date to 7.6-preview.2
(since preview.1 was skipped) as a substitute of seven.5.