Solved SFC scan log does not show files that cannot be fixed in log

[w7bill]

Hello everyone,

First my SFC scan was done after image (just as a caution) I am not experiencing any problems (it had been a very long time since I did one).

I used the sfc /scannow command from an elevated cmd in normal mode and it completed fine (I did re-run it several times as in tutorial) but indicated it could not fix some items. So I ran the command to save log to desk top and in review there are no entrees showing any flagged files (what files it could not fix).

As a note: I don't remember running the utility since changing over to Kaspersky Internet security last year. I also recently removed EMET 3.0 being carful to ensure default settings with re-boot before removal via add and remove.

I am just wondering if this is of any concern for further investigation, again everything seems to be working fine at this point.

Many thanks to all on the forum -- Bill

 

[Brink]

Hello Bill,

If you like, go ahead and place a copy of your CBS.log file in a ZIP, and upload it. I'll be happy to take a look at to see if there may be any SFC details in it to report back to you with.

 

[w7bill]

Brink,

Thank you so much for your reply and taking the time to look at my file. I suspect sfc is flagging something changed by Kaspersky but having a second opinion is great. I searched on the topic and could not find a conclusive answer.

Note: The log only will show two runs, I did delete previous logs.

View attachment wbill_sfcdetails.zip

Thank you for your valuable time -- Bill

 

[Brink]

Yep, this sfcdetails.txt log doesn't show anything that was not able to be repaired.

Since you are not having any issues, then you could probably not have to worry about it. Otherwise you could download and run the 64-bit (x64) System Update Readiness Tool for your 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again to see if it finishes without finding anymore issues.

 

[w7bill]

Brink,

Thanks for having a look I really appreciate it! It makes me feel better having your expert eyes giving it a look over. Your tutorial is quite sound and easy to understand so I didn't think I was missing something. I may give the readiness tool a go when time permits.

Thanks and great day to you -- Bill

 

[Brink]

You're welcome Bill. Please let us know if you have any questions.

 

[w7bill]

Brink,

Some additional findings I think are very interesting.

I did run the readiness tool and had the same SFC result in normal mode, it found things as before it could not repair but the list was clean.

I ran the SFC /verifyonly command on our lap-top (it has same AV and similar programs but is win 7 Home premium 64bit) and it was clean so that ruled out Kaspersky blocking activity.

Now for some reason I got the idea to run SFC at boot using the tutorial here http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

I used my repair CD so I started at step #3 and ran the tool at boot, much to my surprise it completed with a clean result listing "no integrity violations"

Now I find comfort in this but I am still a little confused, I wish I knew what caused this activity.

I wanted to post this as it may be of aid to someone finding similar issues

All the best -- Bill

 

[Brink]

Yeah, it will be hard to ID what it says it cannot repair if it doesn't get logged in the SFC logs.

You might give it a few days and run the SFC scan in Windows again, then check the log to see what it shows for that timestamp.