Thread: Windows Resource Protection found corrupt files but was unable to fix some of

C

chester_mand

Member
Joined
Mar 1, 2014
Posts
18
Please help:

My laptop is currently running on Windows Visa Home Premium SP2. My computer cannot run windows update with an error code c800064. I ran sfc/scannow in cmd and when it gets to 68% this message popped up:
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

I have exported my CBS file and uploaded in here please help people!!!

Thank you very much.

View attachment 7212
 
Did you make your recovery disc's when received your laptop? Is so, use those to do a system repair that way.
 
bassfisher6522 said:
Did you make your recovery disc's when received your laptop? Is so, use those to do a system repair that way.
Click to expand...

Please can you, in the future, wait at least a couple of days before recommending a reinstall, to give us a chance to fix the system first. This machine looks to only have a couple of missing winsxs folders. (root cause is concerning though). Thank you :)


@chester_mand:

I need to see exactly which folders are missing in order to begin considering a fix.

Please download the System Update Readiness Tool from Microsoft ->here<-. Save the tool to a convenient location as it may be necessary to run it again.After the download has completed, double-click the file and wait while it initializes.
Click Yes to begin installation.


Then, once it has completed installing (please be patient, it may take up to an hour (or very occasionally longer) to complete):

please upload your C:\Windows\Logs\CBS\CheckSUR.persist.log file just as you did with CBS.log.

Thank you!

Richard
 
niemiro said:
bassfisher6522 said:
Did you make your recovery disc's when received your laptop? Is so, use those to do a system repair that way.
Click to expand...

Please can you, in the future, wait at least a couple of days before recommending a reinstall, to give us a chance to fix the system first. This machine looks to only have a couple of missing winsxs folders. (root cause is concerning though). Thank you :)


@chester_mand:

I need to see exactly which folders are missing in order to begin considering a fix.

Please download the System Update Readiness Tool from Microsoft ->here<-. Save the tool to a convenient location as it may be necessary to run it again.After the download has completed, double-click the file and wait while it initializes.
Click Yes to begin installation.


Then, once it has completed installing (please be patient, it may take up to an hour (or very occasionally longer) to complete):

please upload your C:\Windows\Logs\CBS\CheckSUR.persist.log file just as you did with CBS.log.

Thank you!

Richard
Click to expand...

Thank you very much for the reply! Ok I will follow your instruction and upload the CBS file again!

Regards,
Chester
 
Hello again Chester :)

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


Then re-run SFC & Windows Update and let me know if there's been any improvement.

Thank you.

Richard
 

Attachments

Please can you, in the future, wait at least a couple of days before recommending a reinstall, to give us a chance to fix the system first. This machine looks to only have a couple of missing winsxs folders. (root cause is concerning though). Thank you :)
Click to expand...

I wasn't suggesting or recommending a reinstall...if you can read, I said a system repair...meaning the repair of the system files, which you can do with the recover disc's . Maybe I should have been a little more specific when I wrote that.
 
niemiro said:
Hello again Chester :)

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


Then re-run SFC & Windows Update and let me know if there's been any improvement.

Thank you.

Richard
Click to expand...

Code:

SFCFix version 2.1.1.0 by niemiro.
Start time: 2014-03-02 23:02:41.497
Using .zip script file at C:\Users\user\Desktop\SFCFixScript.zip








PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-n..ion_service_iassvcs_31bf3856ad364e35_6.0.6002.18005_none_e4680adfbcddcca2
Successfully took permissions for file or folder C:\Windows\servicing\packages


Successfully copied file \\?\C:\Users\user\AppData\Local\niemiro\Archive\iassvcs.dll to \\?\C:\Windows\winsxs\x86_microsoft-windows-n..ion_service_iassvcs_31bf3856ad364e35_6.0.6002.18005_none_e4680adfbcddcca2\iassvcs.dll.
Successfully copied file \\?\C:\Users\user\AppData\Local\niemiro\Archive\package_for_kb978207_client~31bf3856ad364e35~x86~~6.0.1.0.mum to \\?\C:\Windows\servicing\packages\package_for_kb978207_client~31bf3856ad364e35~x86~~6.0.1.0.mum.


Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-n..ion_service_iassvcs_31bf3856ad364e35_6.0.6002.18005_none_e4680adfbcddcca2
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-n..ion_service_iassvcs_31bf3856ad364e35_6.0.6002.18005_none_e4680adfbcddcca2
Successfully restored ownership for C:\Windows\servicing\packages
Successfully restored permissions on C:\Windows\servicing\packages
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.1.1.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2014-03-02 23:02:44.685
----------------------EOF-----------------------
 
bassfisher6522 said:
Please can you, in the future, wait at least a couple of days before recommending a reinstall, to give us a chance to fix the system first. This machine looks to only have a couple of missing winsxs folders. (root cause is concerning though). Thank you :)
Click to expand...

I wasn't suggesting or recommending a reinstall...if you can read, I said a system repair...meaning the repair of the system files, which you can do with the recover disc's . Maybe I should have been a little more specific when I wrote that.
Click to expand...

thank you veery much anyway!!!!
 
niemiro said:
Hello again Chester :)

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


Then re-run SFC & Windows Update and let me know if there's been any improvement.

Thank you.

Richard
Click to expand...


Hi Richard:

I have followed the instructions you gave, the good news was that the sfc/scannow could complete, however, the windows update is still working with the same error code c800064
 
chester_mand said:
Hi Richard:

I have followed the instructions you gave, the good news was that the sfc/scannow could complete, however, the windows update is still working with the same error code c800064
Click to expand...

That's a good step. Can you please try Windows Update one more time, then upload a new set of C:\Windows\Logs\CBS folder. The current set of logs have the root cause masked by the couple of side-errors I've already fixed, and it's difficult to see what's actually going on underneath. A new set will help.

Thank you.

Richard
 
niemiro said:
chester_mand said:
Hi Richard:

I have followed the instructions you gave, the good news was that the sfc/scannow could complete, however, the windows update is still working with the same error code c800064
Click to expand...

That's a good step. Can you please try Windows Update one more time, then upload a new set of C:\Windows\Logs\CBS folder. The current set of logs have the root cause masked by the couple of side-errors I've already fixed, and it's difficult to see what's actually going on underneath. A new set will help.

Thank you.

Richard
Click to expand...

Dear Richard,

I am sorry there was a typo from my last reply, I actually wanted to say that the windows update is still not working, instead of still working. Anyway I have ran the windows update again and here is the new set of CBS log.

Thank you very much.

Chester

View attachment 7231
 
Hello again Chester :)

Now there are no failures showing in the logfile at all... (that just means that it's not a CBS related error, so it's been logged elsewhere)

Please copy to desktop, zip up and upload C:\Windows\WindowsUpdate.log.

If it doesn't show there, I'll start testing hardware. Unfortunately, your error code commonly results from hardware failure, but I'll see if WU.log shows anything first.

Richard
 
niemiro said:
Hello again Chester :)

Now there are no failures showing in the logfile at all... (that just means that it's not a CBS related error, so it's been logged elsewhere)

Please copy to desktop, zip up and upload C:\Windows\WindowsUpdate.log.

If it doesn't show there, I'll start testing hardware. Unfortunately, your error code commonly results from hardware failure, but I'll see if WU.log shows anything first.

Richard
Click to expand...

Oh no not a good sign..... ok Richard here is the Windows Update log.

Thank you very much.

Chester

View attachment WindowsUpdate.zip
 
Hello again!

Better news, the error shows up in your Windows Update log, and I now think it much, much less likely to be hardware.

WARNING to other users: The reset I am applying here is extremely aggressive, and you should not follow these instructions without first checking with an expert. Lots of evidence is wiped out, and it may be impossible to fix the machine afterwards. Here, I have collected that evidence already.

Open an Elevated Command Prompt: https://www.sysnative.com/forums/wi...-prompt-window-windows-windows-vista-7-a.html

then paste in and press enter after:

Code: 
net stop bits
net stop wuauserv
ren %SystemRoot%\SoftwareDistribution *.bak
net start bits
net start wuauserv

Then re-try Windows Update.

Thank you.

Richard
 
niemiro said:
Hello again!

Better news, the error shows up in your Windows Update log, and I now think it much, much less likely to be hardware.

WARNING to other users: The reset I am applying here is extremely aggressive, and you should not follow these instructions without first checking with an expert. Lots of evidence is wiped out, and it may be impossible to fix the machine afterwards. Here, I have collected that evidence already.

Open an Elevated Command Prompt: https://www.sysnative.com/forums/wi...-prompt-window-windows-windows-vista-7-a.html

then paste in and press enter after:

Code: 
net stop bits
net stop wuauserv
ren %SystemRoot%\SoftwareDistribution *.bak
net start bits
net start wuauserv

Then re-try Windows Update.

Thank you.

Richard
Click to expand...

Dear Richard,

It still doesn't work.... So is it hardware problem???

Chester
 
niemiro said:
Hello again!

Better news, the error shows up in your Windows Update log, and I now think it much, much less likely to be hardware.

WARNING to other users: The reset I am applying here is extremely aggressive, and you should not follow these instructions without first checking with an expert. Lots of evidence is wiped out, and it may be impossible to fix the machine afterwards. Here, I have collected that evidence already.

Open an Elevated Command Prompt: https://www.sysnative.com/forums/wi...-prompt-window-windows-windows-vista-7-a.html

then paste in and press enter after:

Code: 
net stop bits
net stop wuauserv
ren %SystemRoot%\SoftwareDistribution *.bak
net start bits
net start wuauserv

Then re-try Windows Update.

Thank you.

Richard
Click to expand...


Hey Richard, did you manage to figure anything out??

Chester
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top