Preview updating with Microsoft Update #15510
Replies: 13 comments 31 replies
-
|
1 which directory is powershell preview installed to byMU? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I reported this issue I'm experiencing after doing the WU update process from Preview.6 to 7: #15673 |
Beta Was this translation helpful? Give feedback.
-
|
It's been a week and I don't see it. Will this also target devices on Insider Dev ring? |
Beta Was this translation helpful? Give feedback.
-
|
Additional info is that, I'm in South East Australia region, |
Beta Was this translation helpful? Give feedback.
-
|
I've updated the main discussion with a workaround for a known issue. Can you please give this a try? |
Beta Was this translation helpful? Give feedback.
-
|
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 :) |
Beta Was this translation helpful? Give feedback.
-
|
For testing, I had tried it on only PowerShell 7.2.0-preview.5 installed environment but I never got an update. Is it intended behavior? |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! This workaround works correctly. |
Beta Was this translation helpful? Give feedback.
-
|
For testing, I had tried it on only PowerShell 7.2.0-preview.5 installed environment but I never got an update. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
I've updated the main discussion with a workaround for a known issue. Can you please give this a try? |
Beta Was this translation helpful? Give feedback.
-
|
I have 7.1.3 already installed, and I have run: 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. |
Beta Was this translation helpful? Give feedback.
-
|
@TravisEz13 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I can now report back to say that PowerShell 7.2.0-preview.7 installed on my machine today via Microsoft Update. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
@TravisEz13 does the work around need to be reversed? I've not seen preview 8 come down from WU yet. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
I think there is a week delay on windows update, as I've not had preview 8 come down yet |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
preview8 installed for me on my devices yesterday so that tallies with what you've said @TravisEz13 |
Beta Was this translation helpful? Give feedback.
-
|
@TravisEz13 is there a similar registry key for installing the stable version or should this just happen when 7.2.0 goes GA |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
@kilasuit Actually, I had to make last minute fixes to the 7.2.0 update and I change the logic. I have added an |
Beta Was this translation helpful? Give feedback.
-
|
To clariify my ask the scenarios I was thinking of are
|
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
|
This might not be the right area first time using github for posting. 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. 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? |
Beta Was this translation helpful? Give feedback.
-
|
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. If you want a feature to enable MU via registry, you must ask Windows. |
Beta Was this translation helpful? Give feedback.
-
|
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.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi all |
Beta Was this translation helpful? Give feedback.
-
|
From recent conversations I've seen I believe that we are to expect this to be available until early-mid January |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
Still waiting on this from what I know am afriad |
Beta Was this translation helpful? Give feedback.
-
|
The "Powershell - x64" product listing is now present on our WSUS environment with the 7.2.1 update available |
Beta Was this translation helpful? Give feedback.
-
|
Seems this installed for me on the 11th and I had not yet noticed
|
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I see the product now... but why only the x64 version? |
Beta Was this translation helpful? Give feedback.
-
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:
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
}
Beta Was this translation helpful? Give feedback.
All reactions