Monday, September 7, 2015

Software Update Error 0x80004005 on client systems

Just when you thought you've seen all known issues, you get another one. This time a client didn't get updates for several months. In almost all Software Update logfiles (UpdatesDeployment.log, WindowsUpdate.log, WUAHandler.log) the error message is the same: Software Update Error: 0x80004005. In the CCMCache no updates where found for several months. This for both Windows updates and Endpoint Protection (SCEP) updates.

The UpdatesDeployment.log shows:
Job error (0x80004005) received for assignment ({<?>}) action
Updates will not be made available


The WindowsUpdate.log shows:
WinHttp: SendRequestToServerForFileInformation failed with 0x801901f7
WinHttp: ShouldFileBeDownloaded failed with 0x801901f7


The WUAHandler.log shows:
Unable to find or read WUA Managed server policy.
Unable to read existing WUA Group Policy object. Error = 0x80004005.
Enabling WUA Managed server policy to use server: <?>
Failed to Add Update Source for WUAgent of type (2) and id ({<?>}). Error = 0x80004005.

Lucky me I found the following blogpost: Microsoft TechNet
It mentions: Had the same issue.  Issue appears to be with corrupt policy info locally on the machine. Typically going to C:\Windows\System32\GroupPolicy\Machine and delete Registry.pol  As soon as I do that I can tell the client to perform an updates scan and all is well. More than likely there is a more elegant solution, but that resolves this error message for me.

I did found indeed a Registry.pol file, which was updated several months ago. I deleted the file, and did a GPUpdate /force after that. When starting Machine policy retrieval after that you will see that the error is gone. I installed 1GB on updates after that :-)

22 comments:

  1. Thanks!! This was driving me nuts. Really appreciate you posting this, worked like a charm...
    Dave

    ReplyDelete
  2. This solution worked me for as well. Thank You.

    ReplyDelete
  3. Just wondering if deleting of registry.pol could remove some specific local policy?

    ReplyDelete
  4. Thanks Worked for me

    ReplyDelete
  5. Still valid. Worked like a charm. Thanks!

    ReplyDelete
  6. I have a compliance baseline that checks for corrupt registry.pol file and deletes it. HMU russ@russ.net.

    ReplyDelete
    Replies
    1. How do you check to see if it's corrupt?

      Delete
    2. I am very interested in how you set this up. Please send instructions. Thank You

      Delete
  7. how to follow the same procedure on no of systems ..Kindly provide d any scripts

    ReplyDelete
  8. How to fix the below mentioned

    Scan failed with error = 0x80240440.

    ReplyDelete
  9. Fixed one rogue system here, thank for the tip!

    ReplyDelete
  10. Wow. Still works in 2020. You are the man!

    ReplyDelete
  11. Worked on 2021.

    ReplyDelete
  12. Thanks, still works in 2021!

    ReplyDelete
  13. Our sys admin has pushed out some vulnerability updates/fixes for Firefox, Adobe Reader, etc and not all computers are getting the update. They get stuck in Unknown Client check passed/Inactive. I looked for a Registry.pol but did not find one. Not sure what causes these same computers to not get these updates and how to fix this in SCCM from continuing to happen. Any suggestions?

    ReplyDelete
  14. Worked for 1 server for me too. :)

    ReplyDelete