Preview updating with Microsoft Update

[TravisEz13]

Please read the Preview updating with Microsoft Update blog for full details.

The blog gives details on how to opt-in and how we will notify you when the updates are available.

Thanks everyone for testing. An issue has been discovered, to work around, either install 7.1.3 or run the script below. We are working to resolve this issue as soon as we can. Thanks for all your help.

Update 6/30/2021:
The issue with the update where 7.1 had to be installed has been resolved and the workaround is no longer needed.

Update 11/1/2021:
Unfortunately, we found a bug in the update produced for 7.2.0-rc.1. It won't affect any other scenario, but we cannot fix it without delaying 7.2.0. Thanks for your understanding.

Update 11/5/2021

When the 7.2.0 update is available, if you have opt'ed in to updating and have MU enabled (or some other source of updates) the update will update 7.1 installs to 7.2.0. Windows determines the exact date of the update release. I'll try to update this when I know the exact date.

The script to opt-in to the clean install changes slightly for the non-preview package:

$pwshRegPath = "HKLM:\SOFTWARE\Microsoft\PowerShellCore"
$stablePath = Join-Path -Path $pwshRegPath -ChildPath "InstalledVersions\31ab5147-9a97-4452-8443-d9709f0516e1"
if (!(Test-Path -Path $stablePath)) {
    $null = New-Item -Path $stablePath -ItemType Directory -Force
}

Set-ItemProperty -Path $pwshRegPath -Name UseMU -Value 1 -Type DWord
Set-ItemProperty -Path $stablePath -Name Install -Value 1 -Type DWord

Update 11/21/2021

Create discussion dedicated for Microsoft Update release dates.:
#16459

work around script

$pwshRegPath = "HKLM:\SOFTWARE\Microsoft\PowerShellCore"
$stablePath = Join-Path -Path $pwshRegPath -ChildPath "InstalledVersions\31ab5147-9a97-4452-8443-d9709f0516e1"
if (!(Test-Path -Path $stablePath)) {
$null = New-Item -Path $stablePath -ItemType Directory -Force
}

[kasini3000]

1 which directory is powershell preview installed to byMU?
2 Can powershell preview be upgraded silently byMU?

[TravisEz13]

1. The update by MU only supports upgrades or installs when it is installed to the default directory.
   • default directory for preview: %ProgramFiles%\powershell\7-preview
2. MU only supports silent installs.

[MaximoTrinidad]

I reported this issue I'm experiencing after doing the WU update process from Preview.6 to 7: #15673
But, I've been experiencing this condition since Preview.6

[A55imilat0r]

It's been a week and I don't see it. Will this also target devices on Insider Dev ring?

[A55imilat0r]

Additional info is that, I'm in South East Australia region,
On Win 10 Dev Insider ring
I have set the reg key via the script and confirmed the key is in place with the correct value via regedit
Also have other Microsoft products set for updates in settings

[TravisEz13]

I've updated the main discussion with a workaround for a known issue. Can you please give this a try?

[A55imilat0r]

Interestingly the issue followed me over to Win 11 insider yesterday, but based on the reg workaround you supplied I can see why.

The workaround worked instantly.

Cheers for that :)

[stknohg]

For testing, I had tried it on only PowerShell 7.2.0-preview.5 installed environment but I never got an update.
However, I was able to get the update immediately after additional installing PowerShell 7.1.3 stable.

Is it intended behavior?

[TravisEz13]

Thanks for finding this issue.

I've updated the main discussion with a workaround for a known issue. Can you please give this a try?

[stknohg]

Thanks! This workaround works correctly.

[kasini3000]

For testing, I had tried it on only PowerShell 7.2.0-preview.5 installed environment but I never got an update.
i set regedit key already, i'm "zh-cn" user, i install 7.2.0-preview.7 manual today.

[ghost]

I set the registry entries in advance for fresh install (I don't currently have PowerShell Preview installed) and have been occasionally checking MS Update. I saw that the Twitter announcement has gone out and still nothing.

See below, registry set, manually rechecking MS Update and seeing nothing, no pwsh-preview.

[TravisEz13]

I've updated the main discussion with a workaround for a known issue. Can you please give this a try?

[ghost]

I have 7.1.3 already installed, and I have run:

PS> New-Item -Path HKLM:\SOFTWARE\Microsoft\PowerShellCore\InstalledVersions\31ab5147-9a97-4452-8443-d9709f0516e1 -ItemType Directory -Force

After several minutes this has not affected the results in Windows Update. I have submitted #15692 following your other requested steps, in case they are still useful. When possible, I will try a reboot, check updates again, and report back.

[ghost]

@TravisEz13
I have rebooted after doing as stated above and unfortunately Windows Update still does not show any PowerShell-related options, and PowerShell Preview has not been installed. I can conduct additional troubleshooting as needed tomorrow.

[ghost]

This has been explained for this specific case by organizational policy in Endpoint Manager that defers non-security updates. For that reason, I don't believe I'm able to be helpful for testing of this functionality.

[ghost]

I can now report back to say that PowerShell 7.2.0-preview.7 installed on my machine today via Microsoft Update.

[TravisEz13]

The issue with the update where 7.1 had to be installed has been resolved and the workaround is no longer needed.

Thanks again for everyone that reported the issue and @stknohg for finding the work around which pointed to the problem in Microsoft Update.

[A55imilat0r]

@TravisEz13 does the work around need to be reversed? I've not seen preview 8 come down from WU yet.

[TravisEz13]

You don't have to reverse the work around but you can.

The preview.8 update should have become available on Tuesday. There will be a significant delay from the release on GitHub and when the update become available on MU as we must create the update after we have built the product and work through the process of getting an update available on MU.

[Jaykul]

For what it's worth, it worked perfectly just now on a Windows 10 (10.0.19043) system (that already had PS 7.1.3) just now -- except that it installed 7.2.0-preview.7 not preview.8 ... was this a one-time thing?

[A55imilat0r]

I think there is a week delay on windows update, as I've not had preview 8 come down yet

[TravisEz13]

The preview.8 update should have become available on Tuesday. There will be a significant delay from the release on GitHub and when the update become available on MU as we must create the update after we have built the product and work through the process of getting an update available on MU.

[kilasuit]

preview8 installed for me on my devices yesterday so that tallies with what you've said @TravisEz13

[kilasuit]

@TravisEz13 is there a similar registry key for installing the stable version or should this just happen when 7.2.0 goes GA

[TravisEz13]

There will be a delay after 7.2 goes GA because we have to on-board each new version we release.

There is an issue here with the documentation about the feature: MicrosoftDocs/PowerShell-Docs#7787
Currently, only one registry is needed to opt-in to updates for all versions and the MSI adds it for you.

[TravisEz13]

Additionally, the 7.2.0 update will only work in the install scenario, because it won't have an MSI with all the features needed to update. 7.2.1 will be the first update to actually update the stable MSIs.

[TravisEz13]

@kilasuit Actually, I had to make last minute fixes to the 7.2.0 update and I change the logic. I have added an Update 11/5/2021 to the description of this discussion, with instructions on how to opt-in to both the update and the install scenario. Update will only be support from 7.1 to reduce the test matrix.

[kilasuit]

To clariify my ask the scenarios I was thinking of are

1. I have a new os install and as part of setting up that os I can make sure I have the right Reg Keys in place and it will install both the stable & preview versions of PowerShell via Windows Update.
2. I have a new os install and as part of setting up that os I can make sure I have the right Reg Keys in place and it will install only the latest stable version of PowerShell via Windows Update.

[TravisEz13]

@kilasuit for clean install, as you seem to be asking, this has been asked and answered. Please read the update in the description of the discussion from 11/5/2021 or clarify what you are asking for.

As for updating, as opposed to clean install, is controlled by a single registry key for both preview and stable.

[CSBlazingDragon]

@TravisEz13

This might not be the right area first time using github for posting.
I am trying to install Powershell 7.2.0 in our test environment to use only WSUS/SCCM disabling Microsoft updates.

Using the 2 new Parameters to the msi

msiexec.exe /I PowerShell-7.2.0-win-x64.msi "ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1", "ENABLE_PSREMOTING=1", "REGISTER_MANIFEST=1", "ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1", "USE_MU=1", "ENABLE_MU=0"

However, when I do this I get the attached picture.

It acts like it is disabling MU as the warning pops into play but the installer still shows it as checked.
I tried to dig around in the registry and no matter what option I chose I do not see a key that was created either way for EnableMU.
There is one created for USE_MU only if it is enabled, if enabled creates and sets the key to 1.

Installing manually I don't see anything created for EnableMU, I guess ultimately I just want to confirm it will not use MU and only our SCCM/WSUS Setups. Is there a way to do this in the registry?

Thoughts?

[TravisEz13]

Correct, EnableMU isn't a registry key, it's implemented in COM.

EnableMU =0 does not disable MU. EnableMU=1 enables it. You must disable it yourself. So, it depends on your original state. This is the behavior we are asked to have by Windows.

There is a DSC resource to configure MU.
Here is an example on how to check in MU is enable programmatically from the resource (this is a little complex, concept): https://github.com/dsccommunity/xWindowsUpdate/blob/6aab96e94e4a53b817e9f9b7cc403b8036c8b93f/source/DSCResources/MSFT_xWindowsUpdateAgent/MSFT_xWindowsUpdateAgent.psm1#L596

If you want a feature to enable MU via registry, you must ask Windows.

[TravisEz13]

I am thinking about producing a module to do these actions (set Use_MU, setup the clean install registry, and enable MU). I we could consider also adding the feature to disable MU in that module. I would not be something quite as complete about dealing with WUA as the DSC Resource, but it would cover the PowerShell Install Scenarios.

Here are the scenarios.

1. Get the state for a package (PowerShell-Preview vs PowerShell)
2. Set the state for a package.
   • (optionally) Opt-in to Update for the packages
   • (optionally) Opt-in to having MU/WU/WSUS install the package if it's not already there
   • (optionally) Opt-in to MU
   • (very explicitly) opt-out of MU

[ClientAdmin]

Hi all
There is still no product category in SCCM Software Update Point for stable PowerShell releases. Is that right or are we missing anything? Please help. Thank you.
Kind regards

[kilasuit]

From recent conversations I've seen I believe that we are to expect this to be available until early-mid January

[EmeraldFlame]

Looking in my WSUS environment, it doesn't look it's currently pulling in these new powershell updates.

I currently have both the "PowerShell" and "PowerShell Preview - x64" products selected. Are we still waiting for a stable channel to be pushed to WSUS, or is there any guidance on possibly which classifications we need to enable?

[kilasuit]

Still waiting on this from what I know am afriad

[thlac]

The "Powershell - x64" product listing is now present on our WSUS environment with the 7.2.1 update available

[kilasuit]

Seems this installed for me on the 11th and I had not yet noticed

[EmeraldFlame]

Just wanted to come back and follow up that the new "Powershell - x64" product listing is now showing up in my own WSUS environments as well.

[ClientAdmin]

I see the product now... but why only the x64 version?

[pomu0326]

• [ ]