Solved Windows File Checker - Corrupt Files Message

[Uplander]

I am a mature (and decidedly not-technical) user running W7 on a Dell Latitude 3540 (2 years old) for which I do not have a Windows disc. The laptop is running fine and I am pretty careful about what I use it for.

Having elected to not upgrade to W10 I decided to improve my regime of maintenance and after Googling around, one of the things I did was a system file check. This ran and the result was a message saying there were corrupt files that couldn't be fixed. More Googling suggested that I should locate the corrupt file and I duly typed in:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" but when I hit return it goes back to the command prompt without doing anything.

I know that this area has had posts before but I wondered, am I stupid to ignore this message? As mentioned above, I am not a technical person.

Thanks for any help.

 

[Uplander]

Responding to my own post, I have now realised (through viewing another W7F thread) that it posts the log to the desktop. So I now have a log and can see some files that could not be repaired but they are meaningless to me. I wonder if anybody could suggest the best way forward.

Thanks.

2016-03-31 19:42:34, Info CSI 00000028 [SR] Verifying 100 (0x0000000000000064) components
2016-03-31 19:42:34, Info CSI 00000029 [SR] Beginning Verify and Repair transaction
2016-03-31 19:42:35, Info CSI 0000002a [SR] Cannot verify component files for 3fd1e93bc780eeeee34119ce58f41fc4, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2016-03-31 19:42:35, Info CSI 0000002c [SR] Verify complete
2016-03-31 19:42:36, Info CSI 0000002d [SR] Verifying 100 (0x0000000000000064) components
2016-03-31 19:42:36, Info CSI 0000002e [SR] Beginning Verify and Repair transaction
2016-03-31 19:42:37, Info CSI 0000002f [SR] Cannot verify component files for 4778319a65034bbbd50fd99390c3c2d8, Version = 6.1.7601.18606, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2016-03-31 19:42:37, Info CSI 00000031 [SR] Verify complete

2016-03-31 19:53:38, Info CSI 00000373 [SR] Repairing 2 components
2016-03-31 19:53:38, Info CSI 00000374 [SR] Beginning Verify and Repair transaction
2016-03-31 19:53:38, Info CSI 00000375 [SR] Cannot verify component files for 3fd1e93bc780eeeee34119ce58f41fc4, Version = 6.1.7601.18719, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2016-03-31 19:53:38, Info CSI 00000376 [SR] Cannot verify component files for 4778319a65034bbbd50fd99390c3c2d8, Version = 6.1.7601.18606, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
2016-03-31 19:53:38, Info CSI 00000378 [SR] Repair complete
2016-03-31 19:53:38, Info CSI 00000379 [SR] Committing transaction
2016-03-31 19:53:38, Info CSI 0000037d [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

 

[torchwood]

No need to worry about those Uplander, there all Tagged as >> info <<, and concluding False.

Roy

 

[whs]

The usual course of action (if you want to repair them) would be a repair/install

How to Repair a Corrupt Windows 7 Installation | PCWorld

 

[Uplander]

Many thanks for both the posts. The PCWorld article is helpful but as it says, "you'll need a Windows 7 installation disc that matches the version of Windows already installed on your system" - all I got with the Dell was a W8 upgrade disc.

Your guidance Torchwood is reassuring; I am happy to leave alone if this is a non-issue. In that vein and in the spirit of (maybe) helping others who are not experts but want to maintain their computer, I did find a useful article at:

scannow sfc - LEARN how to use SFC.EXE (system file checker)

The key paragraph seems to be:

The main reason for using this utility is when you suspect there may be a problem with a Windows system file. Perhaps you get a dialog box appear informing you of a problem with a .dll file, or your program will just not load! It is therefore worth checking to see if there are any corrupt system files using scannow sfc.

So, I think I am reassured. Thanks again.