Windows 7 Update fails with error code C000000D - Windows Update encountered an unknown error

Anonymous
2014-08-05T15:18:32+00:00

I tried running windows update from the action center today and now get this error message.   Last successful update was a couple of weeks ago. Rebooting the computer makes no difference. I have run the windows update troubleshooter found on the update error window available under the "Get help with this error" link and it says that it fixed two problems (Service registration is missing or corrupt - Fixed,  Problems installing recent updates - Fixed) but windows update still refuses to run.  The troubleshooter did return one puzzling piece of information; it said  "Windows Version: 6.1, Architecture: amd64" when in fact Windows, when asked, will say that it is a "Intel Core i7-2600k" (3.4GHz quad core sandy bridge to be specific).

Are there any suggestions how I might troubleshoot or fix the update failure?

In the WUDiagTempFolder\windowsupdate.log file I did find this section that referred to this error:

2014-08-03    19:21:53:067    1184    2208    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]

2014-08-03    19:21:53:067    1184    2208    Agent    *********

2014-08-03    19:21:53:067    1184    2208    Agent      * Online = Yes; Ignore download priority = No

2014-08-03    19:21:53:067    1184    2208    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"

2014-08-03    19:21:53:067    1184    2208    Agent      * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service

2014-08-03    19:21:53:067    1184    2208    Agent      * Search Scope = {Machine}

2014-08-03    19:21:53:069    1184    2208    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:

2014-08-03    19:22:13:089    1184    2208    Misc     Microsoft signed: NA

2014-08-03    19:22:13:113    1184    2208    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPE82E.tmp with dwProvFlags 0x00000080:

2014-08-03    19:22:28:138    1184    2208    Misc    FATAL: Error: 0xc000000d when verifying trust for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPE82E.tmp

2014-08-03    19:22:28:138    1184    2208    Misc    WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPE82E.tmp are not trusted: Error 0xc000000d

2014-08-03    19:22:28:138    1184    2208    WuRedir    FATAL: Quorum check failed: c000000d

2014-08-03    19:22:35:522    1184    2208    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194

2014-08-03    19:22:35:522    1184    2208    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194

2014-08-03    19:22:35:522    1184    2208    Misc    WARNING: DownloadFileInternal failed for http://ds.download.windowsupdate.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab: error 0x80190194

2014-08-03    19:22:42:807    1184    2208    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194

2014-08-03    19:22:42:807    1184    2208    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194

2014-08-03    19:22:42:807    1184    2208    Misc    WARNING: DownloadFileInternal failed for http://download.microsoft.com/v11/2/windowsupdate/redir/v6-win7sp1-wuredir.cab: error 0x80190194

2014-08-03    19:22:50:247    1184    2208    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\v6-win7sp1-wuredir.cab with dwProvFlags 0x00000080:

2014-08-03    19:22:50:262    1184    2208    Misc     Microsoft signed: NA

2014-08-03    19:22:50:263    1184    2208    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab with dwProvFlags 0x00000080:

2014-08-03    19:22:50:267    1184    2208    Misc     Microsoft signed: NA

2014-08-03    19:22:50:270    1184    2208    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP7947.tmp with dwProvFlags 0x00000080:

2014-08-03    19:22:50:276    1184    2208    Misc    FATAL: Error: 0xc000000d when verifying trust for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP7947.tmp

2014-08-03    19:22:50:276    1184    2208    Misc    WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP7947.tmp are not trusted: Error 0xc000000d

2014-08-03    19:22:50:276    1184    2208    WuRedir    FATAL: Quorum check failed: c000000d

2014-08-03    19:22:50:277    1184    2208    Agent    WARNING: Failed to obtain the authorization cab URLs, hr=0xc000000d

2014-08-03    19:22:50:277    1184    2208    Agent      * WARNING: Online service registration/service ID resolution failed, hr=0xC000000D

2014-08-03    19:22:50:277    1184    2208    Agent      * WARNING: Exit code = 0xC000000D

2014-08-03    19:22:50:277    1184    2208    Agent    *********

2014-08-03    19:22:50:277    1184    2208    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

It looks like a file is not trusted by the machine.  How might this be fixed?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-08-14T22:20:32+00:00

In the end I just rolled the system back to a restore point that corresponded with the last successful Microsoft Update and that fixed whatever was causing the problem. New updates load fine now.

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments

47 additional answers

Sort by: Newest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2015-03-24T14:51:53+00:00

    I had the same error. I uninstalled the Entrust products and now the Updates are successful.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-03-13T20:49:09+00:00

    I never post in these forums.  I have same issue in Windows7 x64 VM environment.  Entrust was the culprit.

    I installed update from 9.1 to 9.2 and this did the trick.

    Other issue this was causing me was when VM would reboot, it would corrupt the machine cert, and deny RDP or any other access to machine. We would need to remove from 1) remove from domain, 2) rename machine, and then re-rename back and join domain.  This has been for long time.  Only two machines this occurs on in the enterprise are the two machines with Entrust 9.1 installed. Update to 9.2.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-10-01T14:39:49+00:00

    Hello Xiaofeng,

    Thank you for posting your query.

    • Have you tried all the suggestions provided earlier in this thread?

    If not, please try the suggestions provided earlier and check.

    The issue may have been caused due to third party software conflict. Perform clean boot and check if the issue still persists.

    Putting your system in Clean Boot state helps in identifying if any third party applications or startup items are causing the issue. You need to follow the steps from the article mentioned below to perform a Clean Boot.

    Refer to the link to perform clean boot.

    How to perform a clean boot in Windows

    Note: Refer "How to reset the computer to start normally after clean boot troubleshooting" to reset the computer to start as normal after troubleshooting.

    Hope this information is helpful. Please do let us know the result, we’ll be glad to assist you.

    Thank you.

    Was this answer helpful?

    0 comments No comments