SFC unable to repair Microsoft-Windows-NetFx4-Shared-Deployment

Meddlesom · 02 Aug 2011

I've been running disk and system maintenance on my computer, and sfc found some corruption it couldn't repair. It looks like it's .NET framework 4 that has the errors, so I uninstalled it and its updates, then reinstalled it and updated it, but the problem remains. Since that didn't solve it, I'm not sure if that's where the problem is or what to do about it. Anyone know which files I need to look at before I resort to doing an upgrade/repair installation?

2011-08-02 11:35:11, Info CSI 000002e3 [SR] Cannot verify component files for Microsoft-Windows-NetFx4-Shared-Deployment, Version = 6.2.7600.16513, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

Meddlesom · 07 Aug 2011

Anyone?

**cluberti** · 08 Aug 2011

It appears to be, from the error, that the SFC cache and the manifest for the installed app don't match during the scan (whether they actually do or not nonwithstanding, SFC says they do not), thus it thinks the files *could* be damaged (this is one of the ways SFC verifies files). You say you removed the files and then reinstalled, but I would question two things here - one, did you run SFC after removing .NET 4 before doing a reinstall (to make sure nothing else shows as failing verification), and did you re-download the files from Microsoft's downloads site before reinstalling (rather than re-using the previously downloaded package, which is now suspect)?

Meddlesom · 22 Aug 2011

I did the process again and ran SFC after uninstalling all the .net stuff, and the file was still there. I've also got some stuff in the event log that seems to be related...

an error 4107, CAPI2
Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

And this information event 1001, which should elaborate on the error 4107.

Fault bucket , type 0
Event Name: WindowsWcpStoreCorruption
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601
P2: FileHashMismatch
P3: \winsxs\manifests\wow64_microsoft-windows-n..4-shared-deployment_31bf3856ad364e35_6.2.7600.16513_none_6c7ed1397d9f6159.manifest