Solved Windows Resource Protection found corrupt files but was unable to fix

[tsilva]

Hello!

Last month something happenned to my pc that i'm not really sure about what happenned. My pc was fine one day, i went to sleep, and the next day it wouldn't boot. In the "Starting Windows" it gave me a quick BSOD and my pc would restart. But eventually after searching the web i found a solution, a guy told me to go to the BIOS and change the disk mode from IDE to AHCI, and that worked! But then, i ran the "sfc /scannow" just to make sure that everything was ok, and gave me the message "Windows Resource Protection found corrupt files but was unable to fix some of them". Later on, i found another forum, where a guy would analyze my CBS.log that the "sfc /scannow" would make after analising my computer, and he would give a script to correct the errors every time i ran the "sfc /scannow". We were working this out at a good pace, but then he said he had an assignment to make and it's been a month since the last time we spoke. I wouldn't mind waiting because my computer was working fine. But a few days ago my computer started "misbehaving" again. Now, everytime i boot up my computer starts analising my disk (i think) through CHKDSK. This happens everytime! The CHKDSK says i have some bad files and such, but it doesn't do anything to them, it's like it removes the same files in every analysis. I have to skip the CHKDSK to get to Windows, and if i didn't do that, i would be stuck in a loop between CHKDSK and restart (the computer restarts in the end of the CHKDSK analysis, if you don't know). And when i get to Windows it gives me two errors saying "C:\Windows\Fonts\upcli.ttf" and "C:\Windows\Fonts\upclbi.ttf" are illegible. And today, my computer couldn't even find my router, but i fixed that by uninstalling the wireless controller and install it again. And right now, my computer is really really slow! Writing something on google it freezes or opening a folder, i have to wait a few seconds! It's like it slows down for a few minutes. Everything is really slow and a few minutes later it's everything with the normal speed, but this keeps happening. The "sfc /scannow" know stucks at 18% and says it couldn't finish. I'm really frustated, it's like everytime i fix something a new problem will appear at some point in time. I could really use your help.

Sorry for the enormous post and sorry if this is not the correct topic for Windows Update, i wasn't sure.

Best regards

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data

 

[tsilva]

Sorry, didn't notice that. I'm already runninf SURT but it's taking too long to update, is it normal? And where do i have to "Leave it to run uninterrupted." ?

 

[NoelDP]

It often takes anywhere from 15 minutes to 3 hours - I think the record for a successful run is about 6 hours, but much depends on the computer's specs, and the number of problems it finds.

Please be patient.

 

[tsilva]

Oh, thank you. I thought it was my computer's fault, because like i told you earlier, i don't know what's happening to my computer because from time to time it really slows down and i have to wait a few minutes for him to get back to normal speed. Is it better to leave the computer alone to do the update or can i continue to do my stuff?

 

[NoelDP]

Keep on working - but be prepared for it to slow down occasionally as it goes through its cycles.

 

[tsilva]

Okay, thank you I'll post everything after i finish doing everything in the Posting Instructions.

 

[tsilva]

Hello again.

So, i executed the SURT, and that completed well and didn't me give any error.
Next, i executed the "sfc/ scannow", but like i told on my first post it gets stuck, but this time it was at 20%, and says "windows resource protection could not perform the requested operation".
I tried to update but gave me an error. The image is in Portuguese, if you want any translation, tell me please.
View attachment 298765
And here's the CBS log:
View attachment 298766

 

[NoelDP]

Please post the CheckSUR.log file as well - that's necessary to establish the results of the tool's scan.

The SFC scan broke down with the following error...

2013-12-25 23:46:28, Info                  CSI    0000011f [SR] Beginning Verify and Repair transaction
2013-12-25 23:46:36, Error                 CSI    00000120 (F) STATUS_FILE_CORRUPT_ERROR #1838374# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound|AllowSharingViolation|AllowAccessDenied), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES|FILE_READ_DATA), oa = @0xa7ce40->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[128]"\SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-lilyupc_31bf3856ad364e35_6.1.7600.16385_none_767d64eb7a9abcc4\upcll.ttf"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa7cef0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000102]
2013-12-25 23:46:36, Error                 CSI    [EMAIL="00000121@2013/12/25:23:46:36.973"]00000121@2013/12/25:23:46:36.973[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_FILE_CORRUPT_ERROR originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2013-12-25 23:46:37, Error                 CSI    00000122 (F) STATUS_FILE_CORRUPT_ERROR #1838373# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000102]
2013-12-25 23:46:37, Error                 CSI    00000123 (F) STATUS_FILE_CORRUPT_ERROR #1838372# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = (MissingFileIsOk|SharingViolationIsOk|AccessDeniedIsOk), da = (SYNCHRONIZE|FILE_READ_DATA), oa = @0xa7d4e8->SIL_OBJECT_ATTRIBUTES {s:40; on:"upcll.ttf"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE), file = NULL, disp = Invalid)
[gle=0xd0000102]

I suspect that this may be the result of filesystem problems rather than actual file corruptions - please run a CHKDSK and see what it has to say - followed by another SFC scan...

Please run a full CHKDSK and SFC scan....

Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -
then run the SFC.

SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.


Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your reply

 

[tsilva]

Ok, i'll do that. Sorry, heres the "CheckSUR.log".
View attachment 298810
Tell me if that's the only file you need, because, there's other files that i don't know if you need, like, "CheckSUR.persist" and some Winrar files that say "CbsPersist_(random huge number)"

 

[NoelDP]

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

Summary:
Seconds executed: 5056
 [B]Found 350 errors
[/B] 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
[B]  CSI Payload File Missing Total count: 294
[/B]  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]

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]

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

 

[tsilva]

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

 

[NoelDP]

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]

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]

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]

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]

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]

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?