| Error Code | Error reason | Solution |
| 0x00000000 | Success | Device has reported in once completed, and marked as Success in SCCM Monitoring |
| 0x80070422 | Windows updates service is stopped and set to Disabled | Check Windows updates service is set to Automatic and can be started |
| 0x80073701 | The referenced assembly could not be found | Some files may be corrupt. Try logging on to the device and running sfc /scannow to repair any corrupt files |
| 0x80080100 | No signature was present in the subject | This issue will most likely resolve itself; if the issue persists, try the steps below On the device that has an issue stop the Windows Update service. Browse to and rename c:\windows\SoftwareDistribution to Softwaredistribution.oldBrowse to and rename c:\windows\system32\catroot2 to catroot2.old. Start the Windows Update service. Wait until the SoftwareDistribution folder is created again. Takes about 30 seconds.Refresh Software Center. It should show it installing again, and then Installed. It has since checked in with SCCM and registered as compliant. |
| 0x800F0902 | Unknown Error (-2146498302) | Check that the BITS (Background Intelligent Transfer Service) is running, and is not disabled. Check that’s Windows Update Service is running and is not disabled. |
| 0x8024001e | Operation did not complete because the service or system was being shutdown | This will rectify itself on its next Software Update evaluation cycle |
| 0x80244010 | OnSearch Complete = Failed to end search job. Error 0x80244010 The client is having issues contacting the WSUS service on the SCCM server | Check WSUS service is running. Open Internet explorer and type; http://[SCCM Server name]:8530 should display a page. If HTTP error 503. The service is unavailable. Then WSUS is currently down. Try rebooting the WSUS server first and if the issue continues, further investigation will be required. |
| 0x80244022 | Same as HTTP status 503 – the service is temporarily overloaded | Check WSUS service is running. Open Internet explorer and type; http://[SCCM Server name]:8530 should display a page. If HTTP error 503. The service is unavailable. Then WSUS is currently down. Try rebooting the WSUS server first and if the issue continues, further investigation will be required. |
| 0x87d0070c | Software update execution timeout | The update took longer than the default time. If this appears on the same software update on multiple devices then it may be worth updating the time in Software Library\Software Update\All Software updates\[Specific update]\Properties to a longer period of time. |
| 0x87d00200 | Name not found | This error should resolve itself and has been fixed in later versions of SCCM so can be ignored |
| 0x87d00310 | Failed to refresh Resync state message. This is due to the boundaries not being configured correctly | Check boundaries are configured correctly in SCCM for the network configuration of the problem device |
| 0x87d00651 | Post install scan failed | This issue will most likely resolve itself and can be due to large payloads , if the issue appears on multiple devices then check the link below for various resolution steps https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/ |
| 0x87d00656 | Update handler was unable to continue due to some generic internal error | This issue will most likely resolve itself; if the issue its not resolved try the steps below On the device that has an issue stop the Windows Update service. Browse to and rename c:\windows\SoftwareDistribution to softwaredistribution.old. Start the Windows Update service. Wait until the SoftwareDistribution folder is created again. Takes about 30 seconds.Refresh Software Center. It should show it installing again, and then Installed. It has since checked in with SCCM and registered as compliant. |
| 0x87d00664 | Updates handler job was cancelled | Device was most likely shut down whilst job was running. This will resolve itself on the next evaluation cycle |
| 0x87d00668 | Software update still detected as actionable after apply. The SoftwareDistribution folder has been corrupted | On the device that has an issue stop the Windows Update service. Browse to and rename c:\windows\SoftwareDistribution to softwaredistribution.old. Start the Windows Update serviceWait until the SoftwareDistribution folder is created again. Takes about 30 seconds. Refresh Software Center. It should show it installing again, and then Installed. It has since checked in with SCCM and registered as compliant. |
| 0x87d00692 | Job error (0x87d00692) received for assignment – Group policy conflict | This means that there is a GPO conflict where by the settings in HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate are being set elsewhere as if managed by another tool (like LANDesk). Check registry settings and determine which GPO is setting them. |
