Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x87D00692

0x87D00692 and 0x87D00664: Configuration Manager update deployments fail

10 min read Updated October 5, 2026 Windows Update & Setup

Fix it now

0x87D00692 has a published remediation and it is short: a Group Policy object has overwritten the Windows Update settings the Configuration Manager client wrote for itself. Microsoft’s own fix is to confirm it in WUAHandler.log, rename registry.pol, restart the client agent and run the update cycles. The other three codes in this article are much less well documented.

Run these on an affected client, in an elevated Command Prompt

ren C:\Windows\System32\GroupPolicy\Machine\registry.pol registry.pol.old
gpresult /h C:\gpreport.html /f
  1. First confirm the diagnosis. Open C:\Windows\CCM\Logs\WUAHandler.log and look for ‘Group policy settings were overwritten by a higher authority Error Code 0x87d00692’. Without that line you are looking at something else.
  2. Rename registry.pol as above, then restart the Configuration Manager agent service.
  3. In Control Panel, Configuration Manager, Actions, run the Software Updates Scan Cycle, then the Software Updates Deployment Evaluation Cycle.
  4. Read the report you generated and find which Group Policy object is setting Windows Update values. That object is the actual fault; renaming registry.pol only clears the symptom locally.
  5. Remove the intranet update service settings from that object, or scope it away from Configuration Manager-managed machines, so the policy does not simply come back at the next refresh.

If Group Policy has to keep setting a software update point, it must name exactly the same server and port that Configuration Manager sets. Two different values for the same client is what produces this code in the first place.

If the scan and deployment cycles now complete against the software update point, you are done. If not, read on: the remaining codes point somewhere completely different.

Why it happens

The Configuration Manager client does not use its own update channel. It configures the Windows Update agent on the machine – writing the local policy that names the software update point – and then drives that agent. This works exactly as long as nothing else writes the same values. When a Group Policy object also sets the intranet update service location, Group Policy wins, and the client finds itself scanning against a server it was not told about.

0x87D00692 is what that looks like from the client. Microsoft’s remediation for it is unusually concrete: check WUAHandler.log for ‘Group policy settings were overwritten by a higher authority Error Code 0x87d00692’, rename C:\Windows\System32\GroupPolicy\Machine\registry.pol, restart the Configuration Manager agent service, and start the software update scan and deployment cycles. Renaming registry.pol discards the cached machine policy so it is rebuilt at the next refresh – which is why it is a diagnostic step as much as a fix. If the conflict returns, the object is still applying.

0x87D00664 is the code this article used to build a whole section on, and it has no published meaning at all. Searching Microsoft’s documentation for it returns nothing. The reading it used to carry – that the update was still detected as needed after installing – belongs to a different code: Microsoft publishes 0x87D00668 as ‘Software update still detected as actionable after apply’. If your deployment reports success at the client and failure in the console, that is the code to look for, and it is a real and specific thing.

0x87D0027E appears in Microsoft’s documentation in exactly one place, and it is not about software updates at all. It is documented against a cloud management gateway connection point that cannot validate the certificate revocation list for its client authentication certificate, with the CAPI2 log recording 80092013, ‘The revocation function was unable to check revocation because the revocation server was offline’. If you see it in a co-managed environment, look at certificate revocation checking on the CMG connection point rather than at your deployment.

A Group Policy object is overwriting the client’s update settings

You have this one if 0x87D00692, and WUAHandler.log records the local policy being replaced by a domain policy naming a server that is not your software update point.

  1. Run gpresult /h C:\gpreport.html /f and identify which object sets the Windows Update values.
  2. Remove the intranet update service location settings from that object, or scope it away from managed machines.
  3. Rename registry.pol, restart the Configuration Manager agent service, and run the Software Updates Scan Cycle and Software Updates Deployment Evaluation Cycle.
  4. Confirm WUAHandler.log now shows the client scanning against the software update point without the overwrite line.

Fix the object rather than the client registry. Anything you clear locally is written back at the next policy refresh, which is why this looks intermittent.

The update installs but is still reported as needed

You have this one if 0x87D00668: the client appears to apply the update and the deployment is recorded as failed.

  1. Run the Software Updates Scan Cycle again, then the Software Updates Deployment Evaluation Cycle, and allow time for the state message to reach the site.
  2. Check whether the machine still owes a restart. An update that is staged but not completed stays applicable.
  3. Read UpdatesHandler.log for the individual update’s own result, which is more specific than the deployment result.
  4. If one update behaves this way across many machines, check whether it has been superseded and whether the superseding update is deployed.

The client cannot obtain the content

You have this one if The scan succeeds and the deployment fails, and ContentTransferManager.log shows jobs that never complete.

  1. In the console, check content status for the deployment package and confirm distribution completed to every relevant distribution point.
  2. Validate the content on the distribution point and redistribute if validation fails.
  3. Confirm the client’s boundary group includes a distribution point that actually holds the content.
  4. Read LocationServices.log on the client to see which distribution point it was offered and whether it could reach it.

The client’s own update state is inconsistent

You have this one if One machine fails while identical machines succeed, and its logs disagree with the console.

  1. Stop the Windows Update service, rename C:\Windows\SoftwareDistribution, and start it again so the agent rebuilds its store.
  2. Restart the Configuration Manager agent service.
  3. Run the Machine Policy Retrieval, Software Updates Scan and Software Updates Deployment Evaluation cycles in that order.
  4. If it stays inconsistent, repair or reinstall the Configuration Manager client rather than continuing to troubleshoot the agent.

Certificate revocation checking on a CMG connection point

You have this one if 0x87D0027E in a co-managed or internet-based client scenario, with 403 responses and CAPI2 logging 80092013.

  1. Check the CAPI2 event log on the CMG connection point server for the revocation server offline entry.
  2. Confirm the client authentication certificate’s CRL distribution point is reachable from that server.
  3. Fix revocation checking rather than reflexively disabling it; Microsoft’s guidance is to make it work first and only disable CRL checking for CMG connection points if you cannot.

Full reference

Which log answers which question

Log file What it covers
WUAHandler.log The Windows Update agent as Configuration Manager drives it, including the policy overwrite line
UpdatesDeployment.log Deployment evaluation, enforcement and the result of each update
UpdatesHandler.log Download and install of the individual updates
ScanAgent.log Scan requests and which source they were pointed at
ContentTransferManager.log Content location requests and transfer jobs
LocationServices.log Which distribution point or management point the client was told to use
CcmMessaging.log Client to management point communication errors
PolicyAgent.log Whether the client is receiving policy at all

What the four codes are worth

Code Documentation status
0x87D00692 Published with a full remediation: registry.pol, agent restart, update cycles
0x87D00664 Not published anywhere by Microsoft
0x87D00668 Published as ‘Software update still detected as actionable after apply’
0x87D0027E Published only against CMG connection point certificate revocation failures

Making Group Policy and Configuration Manager coexist

They can coexist, but only on one condition: if a Group Policy object sets the intranet update service location on a Configuration Manager-managed client, it must name the identical server and port that the site assigns, including the scheme. Any difference, including a missing port, produces the overwrite. The simpler arrangement is to let Configuration Manager own that setting entirely and scope the Group Policy object away from managed machines, which also removes the class of problem where someone edits the object years later and nobody connects the two.

Resetting a client’s update state, in order

  1. Stop the Windows Update service.
  2. Rename C:\Windows\SoftwareDistribution so the agent rebuilds its datastore.
  3. Start the Windows Update service.
  4. Restart the Configuration Manager agent service.
  5. Run the Machine Policy Retrieval and Evaluation Cycle so the client has current policy.
  6. Run the Software Updates Scan Cycle.
  7. Run the Software Updates Deployment Evaluation Cycle and watch UpdatesDeployment.log.

When the whole estate fails at once

  • Check the software update point: whether the WSUS application pool is running rather than stopped on its memory limit.
  • Check that synchronisation is completing, and look at the site’s component status for software update point errors.
  • Test the client web service URL from a client to confirm the server answers.
  • Fix the server before retrying clients. Retrying against a broken server produces the same result more often, which is not progress.

Every code this article covers

Code What it points at Source
0x87D00692 Group Policy settings were overwritten by a higher authority: a domain policy replaced the update settings the ConfigMgr client set Microsoft Learn
0x87D00664 Seen on failed software update deployments; no acceptable source publishes a meaning, and the ‘still actionable after apply’ reading belongs to 0x87D00668 not published by the vendor
0x87D00668 Software update still detected as actionable after apply Microsoft Learn
0x87D0027E Documented only against a cloud management gateway connection point that cannot validate the certificate revocation list for its client authentication certificate Microsoft Learn

Confirm the fix worked

  1. WUAHandler.log on a test client no longer carries the ‘overwritten by a higher authority’ line.
  2. The stale WUServer value is absent from the policy branch after a full policy refresh, not just after the rename.
  3. The Software Updates Scan Cycle completes and the client reports compliance state to the site.
  4. The deployment moves to compliant on that client in the console rather than staying at error.
  5. A second machine in the same organisational unit behaves the same way, which is what proves the object was fixed rather than the client.

Questions people ask about this

Do I need to buy anything to resolve this?

No. It is a policy conflict and a log read. Every step is inside Configuration Manager, Group Policy or the client itself.

Can ConfigMgr and a WSUS Group Policy coexist?

Only if the policy names the identical software update point, including the port. Anything else produces the overwrite that 0x87D00692 reports. Scoping the object away from managed machines is the cleaner arrangement.

What does 0x87D00664 mean?

Nothing that Microsoft publishes. A search of Microsoft’s documentation returns no result for it. The ‘still detected as actionable after apply’ text that gets attached to it belongs to 0x87D00668.

Which log should I open first?

WUAHandler.log. It answers the question that decides everything else: is this client scanning against the source you intended, and did something overwrite the setting.

Is renaming registry.pol safe?

Yes, and Microsoft publishes it as the remediation. The file is the cached machine policy; it is rebuilt at the next Group Policy refresh. If the conflicting setting comes back, that tells you the object is still applying and the real fix is upstream.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix 0x80070017 and 0x8007045D: install media read errors during Windows Setup License Error 0x80073BC3 – 0x20009: Setup cannot find a single system partition License Error 0x800B0100 and 0x800B0109: update signature and certificate failures Free Fix 0x800F0831 CBS_E_STORE_CORRUPTION: the component store itself is damaged
โ† Back to Knowledge Base