Issues installing 2022-04 LCU Windows 10 (KB5012599) via SCCM

Question

Hi - we deploy Windows Updates via SCCM to around 5000 endpoints. Generally we have no problems. A handful of machines might occasionally fail to install updates and we can manually repair or reimage these. However with the 2022-04 LCU (KB5012599) things are a lot worse.

We've initially installed this on our usual "Sample" group, before the main "Production" deployment next week. So far this has succeeded on 30 endpoints, and failed on 61. This is obviously a huge failure rate but also the fact that a third of machines succeeds suggests it might not be an SCCM problem itself, and thus is making it difficult to troubleshoot.

On one test machine I've tried every fix I can think of but cannot get it to install the update. It tries and fails. The fixes I've tried are:

• Running the Reset-WindowsUpdate.ps1 script from here
• Stopping the Windows Update service, and renaming the C:\Windows\SoftwareDistribution folder
• Renamed the Registry.pol file to Registry.old
• Ran "SFC -SCANNOW" and allowed it to repair issues
• Ran "DISM.exe /Online /Cleanup-image /Restorehealth" and allowed it to repair the Component Store

Some Windows Updates are applying. But not the LCU.

I've tried manually installing the LCU using the following command. This also fails to install.
"wusa C:\temp\windows10.0-kb5012599-x64_bc0efec7eb2782ac45b1749fb902a80e16832c4a.msu /log:C:\temp\kb5012599.log"

I've attached the log file for the manual install via command line since that's probably the best place to start!

Any ideas chaps?
193134-kb5012599.log
Thanks,
FF

Answer 1

From a reddit-Post I also followed regarding this issue, I got the information, that the Update seems to list correct packages it wants to modify in CBS.log, but it tries to modify other packages afterwards.

Referring to the post on reddit, the following PowerShell-Lines fix the issue for most of the clients in my environment:

CD HKLM:\
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB3186568~31bf3856ad364e35~amd64~~10.0.1.1044*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4033393~31bf3856ad364e35~amd64~~10.0.1.1549*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4054855~31bf3856ad364e35~amd64~~10.0.1.1554*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4054590~31bf3856ad364e35~amd64~~10.0.1.2072*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4486153~31bf3856ad364e35~amd64~~10.0.1.3106*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4486129~31bf3856ad364e35~amd64~~10.0.1.3106*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB3186574~31bf3856ad364e35~amd64~~10.0.1.1044*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4033399~31bf3856ad364e35~amd64~~10.0.1.1549*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4054596~31bf3856ad364e35~amd64~~10.0.1.2053*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4486159~31bf3856ad364e35~amd64~~10.0.1.2752*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\' | Where-Object { $_.Name -like '*Package_*_for_KB4486135~31bf3856ad364e35~amd64~~10.0.1.2752*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

Answer 2

I can confirm this issue.
We also use SCCM to deploy Windows-updates to endpoints.
We get the same errors in the log as @Fishburn, Allan .

Answer 3

same issue here, we have only 39% compliance rate according to the console