-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Update issue #13
Comments
if we add following entry - if ($.Title -notmatch "24H2") { [void]$WUUpdates.Add($) } |
One way of solving it may be to use the 1.6 version of the script which included the PS Modules, and use the hide option Opt into Microsoft UpdateAdd-WUServiceManager -ServiceID "7971f918-a847-4430-9279-4a52d1efe18d" -AddServiceFlag 7 -Confirm:$False Install all available updates$ts = get-date -f "yyyy/MM/dd hh:mm:ss tt" #Hide 24H2 KB hidelist format "kbxxx","kbxxx" Install-WindowsUpdate -NotTitle "preview" -AcceptAll -IgnoreReboot -Verbose | Select Title, KB, Result | Format-Table Instead of the hidelist, you may also just include the -NotKBArticleID variable in install-windowsupdate. I'm not experienced in Powershell, but it worked for us at least. |
@JanVidarA we already tried several variations - if we add -NotKBArticleID KB5044284 -NotTitle "preview" we only get updates for Defender and not the latest CU. Btw KB5044284 ist not the "Windows 11, version 24H2" upgrade |
@hacklhar, this is the v1.6 script I'm using. It installs "everything" except for the 2024-10 update KB5044285, and some minor defender updates which comes afterwards. I'm satisfied with that, as it doesn't affect user too much. https://powershellisfun.com/2024/01/19/using-the-powershell-pswindowsupdate-module/ says something about that. Adding Install-WindowsUpdate -KBArticleID KB5044285 Might solve it. I don't know. That's all I got :-) Install command for win32 app: ... <#PSScriptInfo .VERSION 1.6 .GUID 07e4ef9f-8341-4dc4-bc73-fc277eb6b4e6 .AUTHOR Michael Niehaus .COMPANYNAME Microsoft .COPYRIGHT .TAGS Windows AutoPilot Update OS .LICENSEURI .PROJECTURI .ICONURI .EXTERNALMODULEDEPENDENCIES .REQUIREDSCRIPTS .EXTERNALSCRIPTDEPENDENCIES .RELEASENOTES #> <# [CmdletBinding()] Process If we are running as a 32-bit process on an x64 system, re-launch as a 64-bit processif ("$env:PROCESSOR_ARCHITEW6432" -ne "ARM64") Create a tag file just so Intune knows this was installedif (-not (Test-Path "$($env:ProgramData)\Microsoft\UpdateOS")) Start loggingStart-Transcript "$($env:ProgramData)\Microsoft\UpdateOS\UpdateOS.log" Main logic$needReboot = $false Load module from PowerShell Gallery$ts = get-date -f "yyyy/MM/dd hh:mm:ss tt" Opt into Microsoft UpdateAdd-WUServiceManager -ServiceID "7971f918-a847-4430-9279-4a52d1efe18d" -AddServiceFlag 7 -Confirm:$False Install all available updates$ts = get-date -f "yyyy/MM/dd hh:mm:ss tt" #Hide 24H2 KB hidelist format "kbxxx","kbxxx" Install-WindowsUpdate -NotTitle "preview" -AcceptAll -IgnoreReboot -Verbose | Select Title, KB, Result | Format-Table Specify return code$ts = get-date -f "yyyy/MM/dd hh:mm:ss tt" For whatever reason, the reboot needed flag is not always being properly set. So we always want to force a reboot.If this script (as an app) is being used as a dependent app, then a hard reboot is needed to get the "main" app toinstall.$ts = get-date -f "yyyy/MM/dd hh:mm:ss tt" } |
@JanVidarA thanks for providing your version of ps, but it still is not loading the latest CU for 23H2. No clue what´s going wrong |
@mtniehaus do you have any suggestions to prevent the Feature Update 24H2 from being installed which gets us stuck in ESP? |
on version 1.10, I changed the part that sets the criteria to avoid titles containing "24H2" to avoid update to 24h2. $WUUpdates = New-Object -ComObject Microsoft.Update.UpdateColl |
So you guys experienced the tool doing feature upgrades? |
@swissbuechi we encounter issues that we get the feature update for 24H2 offered each time we are running UpdateOS |
@hacklhar Thank you for clarification. I have the requirement to completely disable the installation of any feature upgrades. I'll try to implement this and report it back here if I succeed. |
By filtering on CategoryID you can block Feature Updates (Feature Updates use CategoryID 3689BDC8-B205-4AF4-8D4A-A63924C5E9D5). I think this is a cleaner approach than trying to filter on title. The below snippet fixes issue #9. I do not have experience working with COM objects, so there is likely a much more optimized way to do this. Some updates may be a member of multiple categories, so I have included logic to account for that. This snippet additionally includes a logic check for the 'EulaAccepted' property as requested in issue #12.
|
Hi Michael,
it seems the latest feature update to 24h2 will be downloaded which stuck the update process during Autopilot.
Did try some exclusion options but no one was working.
Maybe you´ve an idea to implement a workaround.
UpdateOS.log
thx & regards,
Harald
The text was updated successfully, but these errors were encountered: