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

Question

question

FishburnAllan-7020 asked Apr 14, '22 RobertRo-0293 commented Apr 27, '22

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

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

windows-10-general mem-cm-updates

kb5012599.log (31.3 KiB)

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SimonSanders-3709 · Apr 21 at 05:05 AM

I'm having the same issue. Also using SCCM to deploy to 2,000 Win10 machines. I tried all the same steps as @FishburnAllan-7020 including the manual install of the LCU, with the same negative results.

2 ·

ChristophKfer-8406 · Apr 21 at 06:02 AM

We're also having the same issue. Also using SCCM to deploy to 6,000 Win10 machines, with a error rate of over 20%. I tried all the same steps as @FishburnAllan-7020 including the manual install of the LCU, with the same negative results. I also tried everything dism and sfc had to give me, with no success.

1 ·

Amrit-7993 · Apr 27 at 10:08 AM

Found a similar thing for some of my end-users - the update is being deployed via InTune (Windows Update for Business) albeit at a much smaller scale, the update consistently downloads and then tries to install - it fails, and lo and behold InTune redeploys the update. Have a handful of users who are getting this but I'm thinking it's about a quarter of them who are having this death-loop of an update which installs, reverts while installing and then tries again.

Thanks for this post - it's helped us pin it down to the update (we're running a pretty vanilla build all things considered) to my mind.

0 ·

Answer 1 · 2022-04-19T08:42:02.21Z

MartinJensen-5236 answered Apr 19, '22

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

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2022-04-21T13:27:24.15Z

RobertRo-0293 answered Apr 21, '22

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

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 3 · 2022-04-22T19:10:14.107Z

ChristophKfer-8406 answered Apr 22, '22 RobertRo-0293 commented Apr 27, '22

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 }

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RobertRo-0293 · Apr 27 at 10:41 AM

thank you, this worked for us - tested on 5 machines.
not sure about the side effects of this script, so we're hesitant to do a full roll-out.

0 ·

question