Windows 7: SFC /SCANNOW Command - System File Checker

Frank,

Try running the sfc /scannow command at boot in OPTION ONE to see if that may be able to fix them.

If not and you are having issues in Windows 7, then you might consider doing a repair install to fix them instead. If you are not having any problems in Windows 7 though, then I wouldn't worry about trying to fix the files then.

That's what bothers me, Brink,
The fact that after our earlier discussions in this thread, last weekend I did a repair install on my machine, did not reinstall all the apps i previously had, and yet this 'corrupted system file' recurrence.
Is it possible that I am starting from a position of file corruption in my 'family pack' DVD?
Can I use a friend's Windows 7 Home Premium (same edition) to repair install my machine and use 'my license' to validate?
Or can I extract the system files from my friend's OS and use that to repair mine.
Will still try your suggestion of trying option one of your tutorial, though.
These are the problems I'm currently having with my machine:
1. Unable to create system image backups
2. Of late, unable to update Win 7
3. Repeated intermittent crashing of all browsers (IE, Chrome, Opera, Firefox)
4. Crashing Windows Explorer, Com Surrogate etc.
5. Intermittent BSOD's (like clicking on a link in open web-pages)
6. Repeated 'corruption' of system files.
Appreciate your advice
Frank

Frank,

Sorry, I missed what we already did last week.

At this point, I would say that it may be time to consider doing a custom install of Windows 7 if you do not have backups, or a clean install if you do. It looks like your current installation is to corrupted to be repaired.

Does anybody know what "PublicKeyToken = {l:8 b:31bf3856ad364e35}" is? Looking through Henfracar's attachment I noticed most of the troublesome files mention that particular item. I googled it, and it looks like it is tied into WMP and the Vista sidebar, but I don't really know what it is or what it does.

Hi,
Thanks for all the great info. I ran scannow a couple of times from within Windows 7 and twice more at the boot prompt. In all cases, scannow reported that it could not repair some of the files. I've extracted the cbs.log file to sfcdetails.txt as shown in the tutorial and was hoping someone more knowledgeable than me could help decipher it. BTW, I deleted all old entries in the file prior to today.

Thanks,
Mitchell

Hello Mitchell,

Luckily, you only have the file below that needs to be replaced according to your CBS.log.

C:\Windows\System32\tcpmon.dll


If you have a retail copy Windows 7 installation DVD, then you can use the tutorial below to help extract the file above from the DVD to save it to your desktop. Afterwards replace the file above with the extracted copy as in the yellow TIP box at the bottom of the turtorial below.

Extract Files from Windows 7 Installation DVD


Hope this helps,
Shawn

Hey Shawn,

Thanks for the quick response.

I followed the instructions on the link you included and made it to step 12 (copying the file from desktop to system 32 folder). I restarted the computer in Safe Mode with command prompt and entered the appropriate command to copy the dll file. Unfortunately, I received an error message "access is denied" when I tried to copy the file from the desktop to the system32 folder. I tried copying the file to another location successfully, so this tells me the problem is the system 32 destination folder.

I'm probably doing something stupid, but any help would be appreciated it.

Thanks again,
Mitchell

Mitchell,

Did you take ownership and set permissions to "Allow" your account "Full Control" of the C:\Windows\System32\tcpmon.dll file in your current installation before you tried to replace it with the extracted and unblocked copy on your desktop?

After the above, were you not able to just copy the file on the desktop, then paste it directly into the C:\Windows\System32 folder from within Windows 7 to replace it?

Hi Shawn,

Well, I did take ownership and set permissions, but for the wrong file. I did it for the file I extracted--not the file I was replacing. Duh. So, I did it for the correct file and was able to copy it using the command prompt at boot. Scannow produced another error, but this time I was able to decipher it and found it to be tcpmon.ini, so I went through the copy procedure again and finally was able to run scannow with no errors. Yay! Again, thanks for all your help.

Mitchell

You're most welcome Mitchell. I'm happy to hear that there are no more errors showing in SFC.