Another weird one – KB4457144 was deployed to a collection of computers. On those that said it was still required, if you forced Software updates evaluation, it would error in the event log with
Package KB4457144 failed to be changed to the Installed state. Status: 0x80070017
A weird one – KB3114874 was deployed to a collection of computers. On those that said it was still required, if you forced Software updates evaluation, it would not show in the windows update log as being installed, or failing to install. Nothing, nada, zip! If you check what updates were installed , it was not listed. If I used my Get-UpdatesAvailableOnServer.ps1 script , it showed me what SCCM thought there was still outstanding.
Computername ArticleID Name URL ------------ --------- ---- --- Computer1 3114874 Security Update for Microsoft Office 2010 (KB3114874) 32-Bit Edition https://support.microsoft.com/kb/3114874
There was a disconnect between the SCCM Client and Windows Update
So I used my SCCM Client Sledgehammer to reset the SCCM Client and low and behold the KB now installed fine!
The following is a SCCM Client Health Checklist that I run through.
The following code forces a reset/repair of the Windows Update Client on a device. It is based on https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors
Fixes errors in WindowsUpdate.log
0x80070002
0x8024400D
0xc80003f3
0x8024000b
0x8024001E
0x800706B5
hr=8024AFFF
Windows Cumulative Updates require that you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). This helps to mitigate potential issues while installing the LCU.
Answers to what versions of ADK, MDT, SCCM, ADMX, RSAT and VSLC that I need for Windows 10 Version 1809 Continue reading…
SCCM – Windows update log error 0x8024800a correlates to SCCM Client Error 25140, Event ID 10005 . Typically when I find updates failing and errors in the WindowsUpdate.Log, I use my Sledgehammer to reset Windows Update.
After that , I start suspecting a SCCM client issue
Good demo on using Credential Guard to mitigate Pass the hash attacks
The following code forces a reset/repair of the SCCM Client on a device. It is very basic, but it succeeds where Install-CMClient fails even if you force the uninstall before installing Continue reading…
Probably the best explanation I have understood, without getting into too much technical or code specific explanation, so have a listen Continue reading…