Windows Resource Protection found corrupt files but was unable to fix

NoelDP · 26 Dec 2013

Ouch!
Here's the summary of the CheckSUR findings - note the parts I've highlighted....

Code:

Summary:
Seconds executed: 5056
 Found 350 errors
 Fixed 49 errors
  CSI Manifest Missing Total count: 50
  Fixed: CSI Manifest Missing.  Total count: 43
  CSI Manifest All Zeros Total count: 1
  CSI Manifest Failed Catalog Check Total count: 2
  Fixed: CSI Manifest Failed Catalog Check.  Total count: 2
  CSI Catalog Corrupt Total count: 1
  Fixed: CSI Catalog Corrupt.  Total count: 1
  CSI Payload File Missing Total count: 294
  Fixed: CSI Payload File Missing.  Total count: 1
  CBS MUM Missing Total count: 1
  Fixed: CBS MUM Missing.  Total count: 1
  Fixed: CBS Paired File.  Total count: 1
  CSI Store Directory Missing Total count: 1
  Fixed: CSI Store Directory Missing.  Total count: 1
Unavailable repair files:
 winsxs\manifests\amd64_ac631f8336a26a14ce02142ae08331fe_31bf3856ad364e35_10.2.9200.20848_none_f2053ea7a3c9abf3.manifest
 winsxs\manifests\x86_microsoft-windows-i..tacontrol.resources_31bf3856ad364e35_11.2.9600.16428_pt-pt_2e91116562af0532.manifest
 winsxs\manifests\x86_microsoft-windows-ie-infocard.resources_31bf3856ad364e35_11.2.9600.16428_pt-pt_045d35f66df1909f.manifest
 winsxs\manifests\x86_microsoft-windows-i..collector.resources_31bf3856ad364e35_11.2.9600.16428_pt-pt_830afc4d70d12008.manifest
 winsxs\manifests\x86_microsoft-windows-ie-devtools.resources_31bf3856ad364e35_11.2.9600.16428_pt-pt_e436d65572cf9ed1.manifest
 winsxs\manifests\x86_microsoft-windows-ie-f12tools.resources_31bf3856ad364e35_11.2.9600.16428_pt-pt_335f63a67dc54707.manifest
 winsxs\manifests\x86_microsoft-windows-ie-controls.resources_31bf3856ad364e35_11.2.9600.16428_pt-pt_369f956080b76197.manifest
 winsxs\manifests\x86_microsoft-windows-i..rolviewer.resources_31bf3856ad364e35_11.2.9600.16428_pt-pt_2b2a965f85722827.manifest

The basic CheckSUR results are fixable fairly easily - but the underlying 'Missing Payload File' problems are huge, as it's likely that CheckSUR only found a fraction of the problems that really exist.

I can only recommend backing up your data to external media, and then attempting a repair install of the OS.

See what the CHKDSK results are like first - the problem may be a dying hard drive, in which case there is no point in attempting a repair install on the same drive.

tsilva · 26 Dec 2013

Wel, after two hours and something doing six auto-reboots i had to skip it to come here. It was like i described on my first post here. It's like the CHKDSK it's doing the same thing over and over again and doesn't do anything. I see the CHKDSK analysing the same files and saying (at the same percentage of analysis) that they are illegible. Between 0 and 10% it's where it gives me lots of illegible files. Sometimes it removes some files. At the end of the analysis he recovers some files, but after every analysis, it's the same files that are recovered at the same percentage. And well, when it gets to 17% and it says the analysis it's over and it's going to reboot.
Do you think that this has to do with the thing i told you on my first post? "a guy told me to go to the BIOS and change the disk mode from IDE to AHCI"

And like i told you on my first post, the "sfc /scannow" doesn't work, i tried it again and it gets to 18% and says "windows resource protection could not perform the requested operation". The stupid thing is, last month it worked fine, but now it doesn't god knows why.

tsilva · 26 Dec 2013

So, my only solution is to do a repair install?

tsilva · 26 Dec 2013

Could it be because i changed in the bios from IDE to AHCI?

NoelDP · 26 Dec 2013

Changing the interface from IDE to AHCI would not cause this type of corruption.

From the sounds of your CHKDSK, your disk is corrupted and possibly damaged - but it also sounds as if you ran it in 'View' mode rather than the requested 'retest' mode. You MUST use the /R switch if you hope to correct the errors.

tsilva · 26 Dec 2013

Yes, i did like you said, in the command prompt i did "chkdsk c:/r" and then i rebooted, and the computer did the chkdsk analysis and after it finishes he reboots and does another chkdsk analysis, and this happen in an infinite loop.

NoelDP · 26 Dec 2013

If it's in an infinite loop like that, then you need to reset the chkdsk flag.

It may also means that the disk is close to failure.

escape the boot chkdsk - hit any key in the 10-second wait period.

In an Elevated Command Prompt, run the following command

CHKNTFS /D
FSUTIL DIRTY QUERY C:

(note the response to the second command)

close the window and reboot - what happens now?

tsilva · 26 Dec 2013

Ok, i'll do that tomorrow, i'm busy right now. Maybe it's the HDD that is malfunctioning, maybe that's the cause of my computer being slow? Like i told you earlier, it has cycles, sometimes it's okay and a few minutes later it's really slow. Searching the web, opening folders, right-clicking on something, basically everything. And a few minutes later, it's back to normal speed.

NoelDP · 27 Dec 2013

Certainly, hard drive problems could account for that type of behaviour - and with the messages you say it's giving you your first priority has to be backup to external media, as soon as possible.

Once that's done, come back and we'll work through your options.

tsilva · 27 Dec 2013

After 4 hours backing up my things, i did what you asked and after the second command said, the C harddrive had errors. Then, i rebooted like you said, and let the chkdsk analysis do his thing to see if anything changed. And to my suprise, it did new things. Started recovering lots of files, correcting some other things and it got to 100% and rebooted. But this time, for the first time in a long time, windows started normally without doing the chkdsk analysis. :)

Oh, i forgot to tell you, i have Linux Ubuntu installed in my computer as well. A good way to see if my harddrive is faulty, is to see if ubuntu is slow like windows?