Windows Update Fails with error C000000D

fhealy · 02 Sep 2014

Windows Update on my Windows 7 64 bit system is failing with error C0000000D. the last update that was applied was Windows Update Agent 7.6.7600.320 on ‎7/‎31/‎2014 7:46. the update services are all there an running. I have tried all of the fixes to windows update problems in the help forums. I have McAfee antivirus that is up to date and finds no malware. I have heard that there was recently a broken update that got out for a few days and I have seen a very similar problem on a few Vista systems. Any Ideas?

NoelDP · 03 Sep 2014

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

bozocv · 05 Sep 2014

Try uninstalling Entrust client if you are using one.

fhealy · 05 Sep 2014

I had followed the posting directions and was about to upload my log files when I saw the reply from bozocv. I have been running Entrust 9.1 on Windows 7 64 bit for over two years. I uninstalled it (fortunately I no longer need it since my work changes to a virtual desktop for remote access) and update started working. I searched and found an article that Entrust 9.2 exhibited the behavior on Windows 8, but apparently a Windows update issued late in july also breaks update if Entrust is installed on Windows 7. Thanks for the help, I had three systems down with this problem.

NoelDP · 05 Sep 2014

Good to know!

Thanks for the report.

bozocv · 08 Sep 2014

Glad I could help! I had problem with this also. If you need encryption and windows update at same time DELETE this reg key and restart PC:

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CryptDllFindOIDInfo\2.16.840.1.101.3.4.2.1!1]
"Name"="SHA-256"
"Algid"=dword:0000800c
"Flags"=dword:00000001

winhelpme · 22 Sep 2014

Can you please say what this registry entry does? I need both encryption and windows updated but am weary of making registry updates without knowing what they do. Thanks.

bozocv said:

Glad I could help! I had problem with this also. If you need encryption and windows update at same time DELETE this reg key and restart PC:

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CryptDllFindOIDInfo\2.16.840.1.101.3.4.2.1!1]
"Name"="SHA-256"
"Algid"=dword:0000800c
"Flags"=dword:00000001

NoelDP · 22 Sep 2014

Assuming I've got the right end of the stick... (I suggest that you fully research it for yourself first!)

Basically, it tells Windows which encryption Algorithm to use when creating/evaluating Hash values for files to assess against known values in places like the Components Registry hive, and the winsxs and servicing folders.

Beware that removing this value may reduce the security of your system, as Windows will no longer be able to do normal crosschecks.

wmassey · 23 Sep 2014

bozocv said:

... DELETE this reg key and restart PC:

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CryptDllFindOIDInfo\2.16.840.1.101.3.4.2.1!1]
"Name"="SHA-256"
"Algid"=dword:0000800c
"Flags"=dword:00000001

A similar discussion on this problem is going on over here and a pointer to this discussion was just added there and I'm finally glad to say that here is something (deletion of a reg key controlling encryption) that finally works for me as well. I don't think that it is truly a "fix"; that will need to wait for MS & Entrust to sort out their differences.

My system is also a company machine so I'm somewhat limited in what I can and cannot do with it, but I do have admin rights so I'm better off than some. Entrust had been installed on the system but was uninstalled long before the offending MS update was delivered, yet that update still seemed to have caused MS update to break. After reading here about how Entrust seemed to be involved, I went through the system and removed every remaining file and registry key with "entrust" in the name (there were still quite a few despite it having been uninstalled) but even doing that did not allow the MS update to work. Finally today I see Jose's pointer to this other forum that suggests the deletion of this registry key, so I export it, delete it, reboot and retry MS update and it is working! Yea!

Now I just need to hear that MS has come up with a fix for the root cause of the problem so I can replace the cryptography key and I'll mark this one as answered ...