About

This guide can help find and fix common issues that can arise in the Windows Update Agent and the ConfigMgr client. To check for errors you will need to open a log file listed below on the device in question:

C:\Windows\CCM\Logs\WUAHandler.log

Error Messages

Feature Update Fails Immeditately Upon Starting Manually In Software Center

Cause

You have to cleanup the old installation attempt before trying again.

Solution

1. Clear the SCCM Cache

   ## Source: https://sccm-zone.com/deleting-the-sccm-cache-the-right-way-3c1de8dc4b48
   [__comobject]$CCMComObject = New-Object -ComObject 'UIResource.UIResourceMgr'
   $CacheInfo = $CCMComObject.GetCacheInfo().GetCacheElements()
   ForEach ($CacheItem in $CacheInfo) {
           $null = $CCMComObject.GetCacheInfo().DeleteCacheElement([string]$($CacheItem.CacheElementID))
   }

2. Delete the content of C:\WINDOWS\SoftwareDistribution\Download folder

   Get-ChildItem C:\WINDOWS\SoftwareDistribution\Download | Remove-Item -Recurse -Force

3. Delete the C:\$WINDOWS.~BT folder (hidden)

   Remove-Item 'C:\$WINDOWS.~BT' -Recurse -Force

4. Run ConfigMgr Actions - Software Update Deployment Evaluation Cycle and Software Update Scan Cycle

   Invoke-WMIMethod -Namespace root\ccm -Class SMS_CLIENT -Name TriggerSchedule "{00000000-0000-0000-0000-000000000113}"
   Start-Sleep -Seconds 180
   Invoke-WMIMethod -Namespace root\ccm -Class SMS_CLIENT -Name TriggerSchedule "{00000000-0000-0000-0000-000000000108}"

Failed to Add Update Source for WUAgent of type (2)

Cause #1

Most likely due to corrupt local group policy.

Solution

1. Rename or Delete File - C:\Windows\System32\GroupPolicy\Machine\Registry.pol

   Rename-Item -Path 'C:\Windows\System32\GroupPolicy\Machine\Registry.pol' -NewName 'Registry.pol.bak'

2. Restart the ConfigMgr Client Service

   Restart-Service -Name CcmExec

3. Run ConfigMgr Action - Software Update Scan Cycle

   Invoke-WMIMethod -Namespace root\ccm -Class SMS_CLIENT -Name TriggerSchedule "{00000000-0000-0000-0000-000000000113}"

Cause #2

You have a GPO applied that is setting a WSUS location for Windows Updates.

Solution

1. Unlink/Edit your WSUS GPO

Failed to run BeginSearch() on WUAgent. Error = 0x80080005.

Cause

Windows Update service is stuck starting/shutting down. 

Solution

1. Restart Computer

Installation job encountered some failures. Job Result = 0x80240022

Cause #1

If the update failing is a Feature Update then this error could mean you have application incompatibility.

Solution

1. Navigate and open file C:\WINDOWS.~BT\Sources\Panther\ActionableReport.html to determine what application is causing an issue.
2. Uninstall that application and try again.

Cause #2

If the update failing is a Feature Update, the device does may not have enough drive space. You can use Microsoft's SetupDiag can be used to confirm this.

Solution

1. Free up drive space.