Hello. Today i was performing a disk check error on my pc with windows 7 64 bits installed. At the final, i saw something strange, it said: "windows resource protection found corrupt files but was unable to fix some of them", and the error was saved in cbs.log. Could you please check this one and tell me what is wrong? Thanks in advance!
Yours, emilyan2010
I'm not a cbs.log expert. In fact, I'm not an expert in anything. Sorry.
The "windows resource protection found corrupt files but was unable to fix some of them" message is quite often seen after a System File Checker scan. So until a cbs.log expert comes along, I'd suggest running a System File Checker scan from an elevated command prompt (option two, this tutorial.) If SFC isn't able to fix the problems with the first scan, it's recommended to run the scan 3 times, rebooting in between each scan.
SFC /SCANNOW Command - System File Checker
This is the command i used in command prompt to get the disc check.I'm not a cbs.log expert. In fact, I'm not an expert in anything. Sorry.
The "windows resource protection found corrupt files but was unable to fix some of them" message is quite often seen after a System File Checker scan. So until a cbs.log expert comes along, I'd suggest running a System File Checker scan from an elevated command prompt (option two, this tutorial.) If SFC isn't able to fix the problems with the first scan, it's recommended to run the scan 3 times, rebooting in between each scan.
SFC /SCANNOW Command - System File Checker
Checkdisk and the System File Checker are two completely different things. Follow Marsmimar's advice and run SFC three more times, with reboots inbetween each scan.
There's a separate utility called chkdsk that can be run from the drive's properties page or from an elevated command prompt. Depending on which options are selected, chkdsk can scan for and attempt recovery of bad sectors only, or scan for and attempt to fix file errors and recovery of bad sectors. It wouldn't hurt to run a separate chkdsk after running the SFC scan.
Disk Check
On this new computer, i installed windows 7 64 bits 3 days ago, after i have formatted the hard disk. After running several system updates, i started to experience moments when updates would run, but never finish. Even if i waited one hour for 1 update having less than 10 mb, it would not install. So, i ran this sfc /scannow, and i found those problems( that is what i meant by disk scanning, i am sorry for being so vague). Now, i ran sfc /scannow for 3 times, with reboots between them, also i introduced windows DVD then ran a startup scan, also another cmd / scannow by using the command
sfc /scannow /offbootdir=c:\ /offwindir=c:\windows but with no success. It always stucks at 51% and i get the "windows resource protection found corrupt files but was unable to fix some of them" error. Thank you for future replies!
Yours, emilyan2010
It sounds like some files were corrupted while installing Windows Updates; it is a rare occurance but does happen. You can either do another clean install and start from scratch or try a repair install. Also, when installing updates it is recommended to do only a few at a time. This reduces the chance of anything going wrong. I usually do 5-10, but some recommend only 1 at a time.
Repair Install
I agree with Petey7. Something probably happened during the installation of Windows 7, or perhaps during the Windows Updates, that damaged some system files. I'd go with another clean install. When it's time to install all those Windows Updates, I'd change my settings from "Install updates automatically (recommended)" to "Never check for updates (not recommended)". Then I'd manually install updates just a few at a time (maybe 5 or 10 at the most.)
Updates are classified as Critical/Important, Recommended, and Optional. Start with the critical/important. Keep track of the KB numbers. Install the first group of 5 or 10. Reboot the computer. If everything seems OK, install the next group. But if the computer starts acting up you'll know exactly which group of updates needs to be uninstalled. Then install the updates one at a time. They'll either install correctly or you'll know which update is the problem and you can leave that update for last. It's a lot slower this way but I've had good success with all my machines.
Quote