ConfigMgr / MECMdecimal -2016409966
Fix Intune Error 0x87D00692: A higher authority, normally a domain Group Policy, overrides the Windows Update settings ConfigMgr tries to apply, so software update scans fail.
Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.
WUAHandler.log
Folder: C:\Windows\CCM\Logs\
Also check: WindowsUpdate.log · UpdatesDeployment.log · ScanAgent.log
Root causes
- A domain GPO sets "Specify intranet Microsoft update service location" and points the device at a different WSUS server than the ConfigMgr software update point.
- Local policy in registry.pol holds Windows Update settings that no longer match what ConfigMgr configures.
- The Windows Update workload is split between ConfigMgr and Intune, and the two sources set conflicting scan sources.
Step-by-step remediation
- In WUAHandler.log find the line "Group policy settings were overwritten by a higher authority" and note the server it names.
- Run gpresult /h gpresult.html and find which GPO sets the Windows Update server policy.
- Remove or filter that GPO for ConfigMgr-managed devices so the software update point is the only source.
- If local policy is the cause, back up and rename C:\Windows\System32\GroupPolicy\Machine\registry.pol, then run gpupdate /force.
- Restart the SMS Agent Host service and run the Software Updates Scan and Deployment Evaluation cycles.
- For co-managed devices, check the Windows Update policies workload slider and whether Intune also sets a scan source.
For the full diagnosis around this error, read Prove which service owns Windows Update on a co-managed device.
Keep patching failures out of the queue
Repeat update and client failures are cheaper to prevent than to chase. Compare the options that take app packaging and upkeep off your task list, from Enterprise App Management to PSADT.
Compare Win32 packaging toolsRelated Error Codes in This Category
Other ConfigMgr / MECM errors with their own runbooks.
- 0x87D00321The install did not finish inside the "Maximum allowed run time", so Configuration Manager timed it out and failed the deployment.
- 0x87D00607The client could not find the application content on any distribution point it can reach (content not found).
- 0x8004100EA WMI namespace the client needs is missing (WBEM_E_INVALID_NAMESPACE), typically root\ccm, so the ConfigMgr client is broken.