What to do if SFC /SCANNOW cannot repair corrupt files

[John Gray]

As part of my IE11 REGEDIT problems, documented elsewhere, I have run SFC /SCANNOW on 60 PCs, and found three where "Windows Resource Protection found corrupt files but was unable to fix some of them."

One PC has so many errors (but none on CHKDSK) that it will probably need a re-image, and both the others contain, in their CBS.LOG files:

Code: Select all

2016-03-21 20:30:30, Info    CSI    000001eb [SR] Cannot repair member file [l:16{8}]"dw20.exe" of NetFx-DW, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-03-21 20:30:30, Info    CSI    000001ec [SR] Cannot repair member file [l:14{7}]"csc.exe" of NetFx-CSharp_Compiler_csc, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-03-21 20:30:30, Info    CSI    000001ed [SR] Cannot repair member file [l:16{8}]"dw20.exe" of NetFx-DW, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-03-21 20:30:30, Info    CSI    000001ee [SR] This component was referenced by [l:152{76}]"Package_1_for_KB2937610~31bf3856ad364e35~x86~~6.1.1.3.2937610-80_neutral_GDR"
2016-03-21 20:30:30, Info    CSI    000001ef [SR] Could not reproject corrupted file [ml:520{260},l:98{49}]"\??\C:\Windows\Microsoft.NET\Framework\v2.0.50727"\[l:16{8}]"dw20.exe"; source file in store is also corrupted
2016-03-21 20:30:30, Info    CSI    000001f0 [SR] Cannot repair member file [l:14{7}]"csc.exe" of NetFx-CSharp_Compiler_csc, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2016-03-21 20:30:30, Info    CSI    000001f1 [SR] This component was referenced by [l:152{76}]"Package_1_for_KB2937610~31bf3856ad364e35~x86~~6.1.1.3.2937610-96_neutral_GDR"
2016-03-21 20:30:30, Info    CSI    000001f2 [SR] Could not reproject corrupted file [ml:520{260},l:98{49}]"\??\C:\Windows\Microsoft.NET\Framework\v2.0.50727"\[l:14{7}]"csc.exe"; source file in store is also corrupted

What would you say was the best way of sorting out these problems?

It would seem that removing .NET Framework v2.0 and reapplying it should work - but https://support.microsoft.com/en-us/kb/908077" onclick="window.open(this.href);return false; seems a bit hairy...

[Rudi]

    
My

You can give the advice in this link a try.
Hopefully one of the methods described will help to repair or remove .Net.

[John Gray]

Thanks, Rudi - I will try your suggestion first, bearing in mind that I apparently don't have a 'clean' copy of .NET v2 anywhere on those two PCs...

[Rudi]

If an app gives me grief, I often skip the repair options and just wipe it from the system (usually with Revo) to remove all traces, and then reinstall. I'm not saying that you should do this; that's just my solution on problem software. Aaron's .NET Framework Setup Cleanup Utility seems to be a good tool to completely remove all traces of .Net. Once it is removed you can do a clean install after downloading it here.

[John Gray]

Thank you again - I won't be able to get at the offending PCs until the weekend, unfortunately...

[John Gray]

Well, that was an exercise in futility!

* I tried the three .NET Fx tools linked from Rudi's post, and found that they either said there was nothing wrong or did not include .NET Fx 2.0 [SP 2] in their list.
* Revo Uninstaller couldn't do anything since .NET Fx 2.0 doesn't appear in Programs and Features.
* Just trying to reinstall .NET Fx 2.0 SP2 fails because it says that you need to turn off the tick box in the "Turn Windows features on or off" link in Programs and Features, and the only one there is for .NET Fx 4.5.1...

So I am just going to leave things as they are, and if anything other than SFC /SCANNOW raises any objection to the errors, I will re-image both PCs.