SFC found corrupt files after Windows update - never had any before

The same thing happened to me also. Microsoft needs to get their shit together.

nine9s said:

I also checked event viewer and found:

The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -1305.

It was timed stamped at same time as my uninstall of KB 3004394.

I had the same error, only 1 instance. Relevant info: https://www.virtualbox.org/ticket/13677

From what I can tell, the KB3004394 update does not install a catalog file on 64-bit windows 7. It does on Windows 8.1 (C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_1_for_KB3004394~31bf3856ad364e35~amd64~~6.3.1.0.cat), so VBox works fine there.

The result of the missing .cat file is that VBox (nor SysInternal's SigCheck.exe for that matter) is not able to verify the authenticity of c:\windows\system32\crypt32.dll and wintrust.dll. If we cannot find any valid signature for the files, we have to assume that they have been tampered with and are forced to abort application loading. These two dlls are important for validating other components, so there is absolutely no way we can ignore this.

Until Microsoft fixes the KB3004394 update on Windows 7, the only solution is to revert/uninstall it.

Even though I uninstalled the specific update, I decided to reinstall my last image. During its update, KB3004394 was no longer offered, but the same amount of Windows Security updates for x64 were offered. So I assume MicroSOft replaced the bad update with a different one (but if people cannot update with the bad one, I am not sure what will happen to people who did get the update and do not know to uninstall it.)

I want to say thanks to all who found that bad update

my problem started about 20h ago, when PC lost internet connection. when i tried to run troubleshoot it failed with error 0x800706f7
so i did some google-doodle and found may solutions to fix it (like CMD run, which failed to fix a found error or form "services" to set cryptographic service to automatic ,but as it happend, mine was on auto...) , but at the end all of those failed.
Somehow i stumbled on this topic and so i found a solution for my problem, just uninstalling a KB3004394 and voila, everything works well now.

Thank you all again.

klettr said:

I want to say thanks to all who found that bad update

my problem started about 20h ago, when PC lost internet connection. when i tried to run troubleshoot it failed with error 0x800706f7
so i did some google-doodle and found may solutions to fix it (like CMD run, which failed to fix a found error or form "services" to set cryptographic service to automatic ,but as it happend, mine was on auto...) , but at the end all of those failed.
Somehow i stumbled on this topic and so i found a solution for my problem, just uninstalling a KB3004394 and voila, everything works well now.

Thank you all again.

Usually you can get quick solutions to widespread problems, but this was new just yesterday, so nothing was out until later in the day. So I guess everyone was grasping for straws until the problem was isolated. I am glad I found solution from others in this thread.

Also, I guess it is a lesson not to update with Windows Updates until a day or two after they first appear. I always installed them as soon as I saw them, but I think I will wait a a day or two now, and search for each one to make sure no problems. Pain and will take time on large, in number, updates, but worth the time to prevent stuff like this.

I think this may be apart of my problem here. IE 11 stopped working for me. My last update included KB3004394.

Here's the error messages I get:

2014-12-13 12:27:26, Info CSI 000001fa [SR] Beginning Verify and Repair transaction
2014-12-13 12:27:26, Info CSI 000001fc [SR] Cannot repair member file [l:32{16}]"explorer.exe.mui" of Microsoft-Windows-explorer.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-12-13 12:27:27, Info CSI 000001fe [SR] Cannot repair member file [l:32{16}]"explorer.exe.mui" of Microsoft-Windows-explorer.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-12-13 12:27:27, Info CSI 000001ff [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"


2014-12-13 12:28:37, Info CSI 0000031a [SR] Beginning Verify and Repair transaction
2014-12-13 12:28:37, Info CSI 0000031c [SR] Cannot repair member file [l:32{16}]"explorer.exe.mui" of Microsoft-Windows-explorer.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-12-13 12:28:37, Info CSI 0000031e [SR] Cannot repair member file [l:32{16}]"explorer.exe.mui" of Microsoft-Windows-explorer.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-12-13 12:28:37, Info CSI 0000031f [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"

Do you guys think it's due to the bad windows update?