Solved SFC results - need help manually fixing

Need some help understanding/fixing some files SFC reported but could not fix. (see attached)

These are the steps I have taken so far:

1. SFC /scannow, and extracted "SR" data from CBS.log

2. Downloaded ISO of win 7 ultimate from Digital River (http://msft.digitalrivercontent.net/win/X17-59465.iso)

3. Extracted ISO with 7-zip, and source "4" data for Win 7 Ultimate

4. Navigated around to make sure extractions looked "familiar", all ok

- - - - - - - - - - - -

I can find the files on ISO data (extracted on external drive) and the files in c:\windows\system32,
but they all seem to be "hardlinks" on C:, but actual files on ISO data. Is the last enumeration listed in the link properties the actual file?

Is this where I copy/replace from ISO data?

I am ok up to this point, just not sure at all WHAT gets copied WHERE!

I WILL, of course, make a zillion backup copies and restore points before trying to fix.

Any help and/or guidance is muchly appreciated! I feel kinda lost on this one...

Thanks!

It is very tedious and labor intensive to manually fix allegedly "corrupt" files that SFC reports.

If they are very minor stuff, like speech and font files; don't bother. They won't affect day to day operation at all.

You have to extract from the iso, and then put the clean file in its' true location AND in its' location in the huge Winsxs folder (not fun to navigate)(have to do a search to find it). To do that you have to change permissions, which is complicated, in order to delete and replace. When you are finally done (maybe 3-4 hours later), you have to change permissions back and hope you don't screw it up.

All of this one file at a time.

When SFC finds "corruption", you should run it three times with reboots in between.

Please list the files still not repaired after that.

I'll try that and get back to you. Thanks....

pscowboy said:

It is very tedious and labor intensive to manually fix allegedly "corrupt" files that SFC reports.

If they are very minor stuff, like speech and font files; don't bother. They won't affect day to day operation at all.

You have to extract from the iso, and then put the clean file in its' true location AND in its' location in the huge Winsxs folder (not fun to navigate)(have to do a search to find it). To do that you have to change permissions, which is complicated, in order to delete and replace. When you are finally done (maybe 3-4 hours later), you have to change permissions back and hope you don't screw it up.

All of this one file at a time.

When SFC finds "corruption", you should run it three times with reboots in between.

Please list the files still not repaired after that.

Click to expand...

I'll try that and get back to ya... I'll do it at least 3 times, to separate CBS logs and reboot in between. Also, will wait for the Mystery User "TrustedInstaller" to have his say! Maybe Redmond will re-engineer SFC to allow for use of installation cd, or maybe like some virus scanners to do the on-line "heuristics" look-up for corrupt backup files. HHHmmmnnnn.....

Thanks.

f14tomcat said:

pscowboy said:

It is very tedious and labor intensive to manually fix allegedly "corrupt" files that SFC reports.

If they are very minor stuff, like speech and font files; don't bother. They won't affect day to day operation at all.

You have to extract from the iso, and then put the clean file in its' true location AND in its' location in the huge Winsxs folder (not fun to navigate)(have to do a search to find it). To do that you have to change permissions, which is complicated, in order to delete and replace. When you are finally done (maybe 3-4 hours later), you have to change permissions back and hope you don't screw it up.

All of this one file at a time.

When SFC finds "corruption", you should run it three times with reboots in between.

Please list the files still not repaired after that.

Click to expand...

I'll try that and get back to ya... I'll do it at least 3 times, to separate CBS logs and reboot in between. Also, will wait for the Mystery User "TrustedInstaller" to have his say! Maybe Redmond will re-engineer SFC to allow for use of installation cd, or maybe like some virus scanners to do the on-line "heuristics" look-up for corrupt backup files. HHHmmmnnnn.....

Thanks.

Click to expand...

Here are the results of SFC... One not listed here I fixed manually (What a PITA!) and it did not show up again (FDEPLOY.DLL).

COMPMGMT.msc runs fine. This is the one I Tried to "author" and change layout. Apparently it works, but SFC doesn't like it!

Thanks for any next suggestions, comments, warnings, etc.

fde, gpedit, & gptxt are part of the Group Policy Editor package. If you never use it, then just ignore the SFC findings. That stuff is usually invoked by an IT guy in a business setting.

You've already determined that compmgmt is working, even with the SFC "corruption".

If it's burning in your gut to try to fix this stuff, I'll repost. But my advice is, let it go. Trust me, it's a half a nightmare to accomplish. So, good luck and be well.

pscowboy said:

fde, gpedit, & gptxt are part of the Group Policy Editor package. If you never use it, then just ignore the SFC findings. That stuff is usually invoked by an IT guy in a business setting.

You've already determined that compmgmt is working, even with the SFC "corruption".

If it's burning in your gut to try to fix this stuff, I'll repost. But my advice is, let it go. Trust me, it's a half a nightmare to accomplish. So, good luck and be well.

Click to expand...

I'll leave the Momma Bear be.... don't want to get between her and her cubs! Thanks for the help and advice.