SFC Found Corrupted Files but Cannot Fix Them

I know there were posts similar to this one already here but I know full well that not every computer and situation, regardless of how similar, is the same. I am currently running windows 7 home premium SP1. I had this laptop for approx. 4 years. Recently it's been lagging, freezing, and has even crashed once or twice. Thinking something went wrong with a system file I elected to run SFC /SCANNOW in the hopes of finding, and fixing of course, any corruptions. After several minutes, the cmd listed that corruptions were found but couldn't be fixed. I even tried SFC in safe mode thinking one of my programs may have been preventing it from fixing the files. My laptop didn't come with an installation disk so I can't extract healthy files from one to repair the corruptions. How can I go about fixing these files?

If you have applied all Windows updates/patches, then you will probably have SFC scan errors. See this post.

UsernameIssues said:

If you have applied all Windows updates/patches, then you will probably have SFC scan errors. See this post.

So if the 'corrupted files' being found by SFC are due to a misunderstanding involving an update what can I do to find out why my pc keeps freezing and lagging? I don't want to uninstall the update if it isn't actually a problem. Is there anyway to be sure the error with SFC IS indeed caused by the update and nothing else without removing the update?

"my pc keeps freezing and lagging"
go to: event log.

countzero said:

"my pc keeps freezing and lagging"
go to: event log.

OK I went to the Even Viewer since that came up when I type 'event log'. I managed to find my way to the 'windows Logs' tab. What should I look for exactly?

Gwen said:

UsernameIssues said:

If you have applied all Windows updates/patches, then you will probably have SFC scan errors. See this post.

So if the 'corrupted files' being found by SFC are due to a misunderstanding involving an update what can I do to find out why my pc keeps freezing and lagging? I don't want to uninstall the update if it isn't actually a problem. Is there anyway to be sure the error with SFC IS indeed caused by the update and nothing else without removing the update?

Sure there is a way

Please follow step 4 in this post:
Windows Update Posting Instructions

Attach the compressed file to your next post via these steps:
Screenshots and Files - Upload and Post in Seven Forums

And we will have a look for you

UsernameIssues said:

Gwen said:

UsernameIssues said:

If you have applied all Windows updates/patches, then you will probably have SFC scan errors. See this post.

So if the 'corrupted files' being found by SFC are due to a misunderstanding involving an update what can I do to find out why my pc keeps freezing and lagging? I don't want to uninstall the update if it isn't actually a problem. Is there anyway to be sure the error with SFC IS indeed caused by the update and nothing else without removing the update?

Sure there is a way

Please follow step 4 in this post:
Windows Update Posting Instructions

Attach the compressed file to your next post via these steps:
Screenshots and Files - Upload and Post in Seven Forums

And we will have a look for you

it wouldn't let me do the entire folder so I just zipped the log file. The other files in the folder had to do with my 7zip.

There is more going on in that file than I understand :-(

I have asked for help

NoelDP said:

There are no errors in the CBS.log - and no data from any SFC scan
If you'd followed the instructions given, then there should also have been a CheckSUR.log file in the CBS folder, and data from SFC in this log, as it goes back as far as 2015-08-03 22:05:18

I followed the directions as I could. I wonder if perhaps it was due to how long ago I initially ran the 'scannow' command. The most recent sfc I did was just a 'verifyonly'. As for the checkSUR.log you mentioned there isn't anything like that in my CBS folder. I have a 'CbsPersist_20150607033655.cab' 'CbsPersist_20150610082955.cab' 'CbsPersist_20150715073342.cab' 'CbsPersist_20150717081903.cab' 'CbsPersist_20150723092357.cab' and the Log file I attached. I can rerun the 'scannow' command and see if that changes anything. The compressed size of the folder with all the files is showing 58.6MB so it was well beyond the limit for posting.