I had asked about remembering how to run sfc /scannow to make sure it was working on the new computer and it ran but it says windows resource protection found corrupt files but was unable to fix some of them. Here is a screen shot of the whole thing. Should I be concerned about this? I have no clue how to get to the log file the screen says.
I realize I am under warranty so if it's serious I plan on calling HP but if not then can get help here on what to do. Mary
To be double-sure, it's probably a good idea to cross-reference that message by looking at the CBS.log details. Your goal, is to see if you are able to find matching errors applicable to outcome of that SFC scan.
My problem is I don't know how to find the CBS log. Mary
SFC appends its results to a log file named CBS.log, which is located in the \Windows\Logs\CBS folder. Use Notepad to read it (you may need to run Notepad as the Administrator). To find the errors, go to the end of the file (Ctrl + End) then use ‘Find’ (Ctrl + F) to check for the words 'cannot repair', use search ‘Up’ to search upwards.
Write down the names of the corrupted files and go here http://www.vistax64.com/tutorials/8... which shows you how to copy any system files that SFC could not repair.
Ok, I found the CBS file in windows and it's a notepad file but when I click to open it says access denied. Home computer and I am the only user. Mary
Never mind I got it open. I clicked copy to put it on the desktop then when I went to open it from the desktop it said I would have to provide administrative privelages and I said yes and then it opened. Off to see what's in there. Mary
Ok it appears it's one file related to the windows side bar. I went to the link but I don't have a vista DVD, the recovery is partitioned on the hard drive. I don't use the side bar and I know when I had it on the screen it seemed fine so should I just leave this?
2008-07-30 22:17:00, Info CSI 00000110 [SR] Cannot repair member fil
[l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9),
Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35},
Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatchAlso can you delete the contents of that log file so if you have to run it again you will get just the current info? Mary
You could look in other folders for other occurrences of the missing file and copy it. In \Windows\Logs\CBS there are two files named CBS.log and CBS.persist.log. The CBS.persist.log is generated when CBS.log gets to be about 50MB in size. CBS.log is copied to CBS.persist.log and a new CBS.log file is started when certain programs are run, e.g. sfc. It should be safe to delete the CBS.persist.log as it is probably at least a couple of weeks old and is no longer useful. Also, remove some of the CBS.log but leave the end bit as it's the most recent.
Ok I found a ton of people on the net with the same question and found this . I don't use the sidebar so have added nothing to it so will leave the file alone. Mary
Mary Thank you for that, I'll write it down now.
Ok, I don't have a CBS.persist log in there just the CBS log. I ran the scan now on my sons HP laptop that is 1yr. old and got the same message. Now when I go into the windows folder on his computer he has the cbs and cbs persist log and he has vista also. I had to copy the cbs log to the desktop to then give permission to open it and when I do the CTRL stuff it says it can't find cannot repair on his, strange. Mary
As I said above “The CBS.persist.log is generated when CBS.log gets to be about 50MB in size”. Perhaps his message was slightly different, look for words with a similar meaning, e.g. corrupt, missing.
yeah I will have to check it better. I have to say I don't like the new format here on the boards. The yellow bakcground with the black text was much better for my eyes to see, getting old I guess. Mary!
