[SOLVED] SFC scannow cannot repair some files

[niemiro]

Excellent!

That log has helped a lot, thank you :)

In addition, thank you very much for your detailed description of your SSD related setup. I will take that into account where appropriate. I have a very similar setup for my SSD also :)

I am now going to try a similar fix to Tom. However, I will be using a different program to perform the fix. This program has been designed from the ground up with language packs in mind, and hopefully will do the trick here (it, for example, internally entirely uses SIDs to avoid ever having to call the Administrators group by name, and many other such things)


WARNING: This fix has been designed specifically for jean. If you are not jean, do not follow these instructions, as you may cause harm to your computer.

Firstly, please download a copy of SFCFix, and save it to your Desktop: www.sysnative.com/niemiro/apps/SFCFix.exe

Then please download the attached .zip file to your Desktop also.

Now, single click on the .zip file and drag and drop in onto the SFCFix.exe.

The program should execute, and a report should be generated. Please copy and paste it here for analysis.

With luck, it will fix everything in one go. Fingers crossed

Richard

P.S. At the moment, the tool requires a prerequisite of Microsoft Visual C++ 2010 SP1, available here: http://www.microsoft.com/en-gb/download/details.aspx?id=8328

This will be resolved in the next few days, but in the mean time, if it fails to run, or crashes, please install that package, and all should be well. You will need the x86 package even though you are using a x64 computer.

 

[tom982]

Where's the attachment?

 

[niemiro]

Where's the attachment?

*facepalm*

Thanks Tom :)

Uploaded now.

 

[jean]

Where's the attachment?

*facepalm*

Thanks Tom :)

Uploaded now.

Hello Tom, Hello Richard,

Something wrong happen with the process as you can see in SFCfix_First_run (in fact each line report an error)
I also included the content of "C:\Users\Jean\AppData\Local\niemiro"
I did erase that folder and create a shorcut for sfcfix.exe with option to "run as administrator" for that shortcut and drag your sfcfix.zip to this new shortcut
You can see the result in the "SFCFix_as_administrator_second_run" as you can see somes are successful this time but still some errors....

N.B. In french OS, "everyone" group is "tout le monde" if ever useful....

I will wait for your advice

Jean

 

[niemiro]

Hello again :)

We have taken up enough of your precious time already.

The easy method for repairal of system files on non-English computers is an offline method.

What you do is find your Windows CD, or create one like this: http://www.howtogeek.com/howto/5409/create-a-system-repair-disc-in-windows-7/

We are not re-installing Windows, just running a Command Prompt off that CD. The advantage of this method is that permissions are completely avoided. The file names are all English, and not the problem. This method avoids that. If you have a CD to hand, we can easily use this tried and tested method now. I have used this several times on non-English computers (I specifically remember a Spanish computer, and a Chinese (Simplified) computer, but there were others). The method works.

The thing is that some people find it hard to find a CD, and perhaps even a CD drive in modern netbooks. The process takes a long time, and is fairly tricky. Although I can see that you are more than competent to perform it easily, there are many people who are not quite as used to computers as you. We almost always manage to talk them through it with clear instructions and screenshots, but the process is still daunting, especially if we have to invoke the one-time boot menu to even boot the CD.

We are currently trying to perfect an easy technique from within Windows to ease the process for everyone. It quickly became clear that the batch file approach was not working. That was the reason I wrote SFCFix.

It was designed to work on non-English computers, and indeed it has passed all tests on non-English computers. But there appears to be a bug which breaks it on non-English computers.

If you are willing, one more debug run would be massively appreciated. I will not take up any more of your time beyond this after that, and we can nail it from the offline disk (yet more disasters permitting). But I do not ask it of you. If you are willing only.

But if you are willing, could you please run the attached script, and upload both logs. I hope that nobody ever again has to go through what you went through here.

Thank you,

Richard

 

[jean]

Hello again :)

We have taken up enough of your precious time already.

The easy method for repairal of system files on non-English computers is an offline method.

What you do is find your Windows CD, or create one like this: http://www.howtogeek.com/howto/5409/create-a-system-repair-disc-in-windows-7/

We are not re-installing Windows, just running a Command Prompt off that CD. The advantage of this method is that permissions are completely avoided. The file names are all English, and not the problem. This method avoids that. If you have a CD to hand, we can easily use this tried and tested method now. I have used this several times on non-English computers (I specifically remember a Spanish computer, and a Chinese (Simplified) computer, but there were others). The method works.

The thing is that some people find it hard to find a CD, and perhaps even a CD drive in modern netbooks. The process takes a long time, and is fairly tricky. Although I can see that you are more than competent to perform it easily, there are many people who are not quite as used to computers as you. We almost always manage to talk them through it with clear instructions and screenshots, but the process is still daunting, especially if we have to invoke the one-time boot menu to even boot the CD.

We are currently trying to perfect an easy technique from within Windows to ease the process for everyone. It quickly became clear that the batch file approach was not working. That was the reason I wrote SFCFix.

It was designed to work on non-English computers, and indeed it has passed all tests on non-English computers. But there appears to be a bug which breaks it on non-English computers.

If you are willing, one more debug run would be massively appreciated. I will not take up any more of your time beyond this after that, and we can nail it from the offline disk (yet more disasters permitting). But I do not ask it of you. If you are willing only.

But if you are willing, could you please run the attached script, and upload both logs. I hope that nobody ever again has to go through what you went through here.

Thank you,

Richard

Hello Tom, Hello Richard,

Here is your files together with the last CBs.log from my system, i also include yours files to verify if that are in their original state (the one today was o.k., but i had somes problems downloding the two first one... maybe they were corrupted in the process?

N.B. I did run the new run as administrator again...

Than you and i will wait for your advice

Jean

 

[niemiro]

Thanks again Jean :)

I have managed to track down the bugs in the code from your logs. I should have it all fixed up in a few days time. Thank you very much for doing that for me.

Back to your topic, I am really pleased with process :) PresentationFramework.resources.dll has now been fixed, just icardagt.exe to go now.

I have also identified why the tool did not manage to replace that file, and that too will be fixed in the next update.

But for now, let's do the manual method.

Unfortunately, I do not have the French translations for the button texts. Hopefully you will be able to manage?

Navigate to the C:\Windows\winsxs\amd64_wcf-icardagt_exe_31bf3856ad364e35_6.1.7600.16385_none_8dcc9c6f8b58a5eb\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Under the Owner tab, click Edit.
Click "Other Users and Groups".
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK THREE times.
Click on the Permissions tab.
Under type Deny, single click on it and click Remove.
Click OK.
Click Edit (now on the standard file Property window under the Security tab).
Click Add.
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK.
Single click on Everyone and then tick the "Full Control" box under Allow.
Click OK TWO times.

Once you have done this, please copy and paste in the missing file icardagt.exe from one of my previous attachments.

Then, please go back to the file properties security dialogues and remove the Full Control (Allow): Everyone entry from the file permissions.

Then please restore TrustedInstaller as the owner (see here for details of how to do this, as it won't appear under a "Find All" search: http://www.askvg.com/guide-how-to-r...default-owner-of-a-file-or-folder-in-windows/)

Finally, please re-run SFC. Fingers crossed everything is now fixed.

Richard

 

[jean]

Thanks again Jean :)

I have managed to track down the bugs in the code from your logs. I should have it all fixed up in a few days time. Thank you very much for doing that for me.

Back to your topic, I am really pleased with process :) PresentationFramework.resources.dll has now been fixed, just icardagt.exe to go now.

I have also identified why the tool did not manage to replace that file, and that too will be fixed in the next update.

But for now, let's do the manual method.

Unfortunately, I do not have the French translations for the button texts. Hopefully you will be able to manage?

Navigate to the C:\Windows\winsxs\amd64_wcf-icardagt_exe_31bf3856ad364e35_6.1.7600.16385_none_8dcc9c6f8b58a5eb\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Under the Owner tab, click Edit.
Click "Other Users and Groups".
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK THREE times.
Click on the Permissions tab.
Under type Deny, single click on it and click Remove.
Click OK.
Click Edit (now on the standard file Property window under the Security tab).
Click Add.
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK.
Single click on Everyone and then tick the "Full Control" box under Allow.
Click OK TWO times.

Once you have done this, please copy and paste in the missing file icardagt.exe from one of my previous attachments.

Then, please go back to the file properties security dialogues and remove the Full Control (Allow): Everyone entry from the file permissions.

Then please restore TrustedInstaller as the owner (see here for details of how to do this, as it won't appear under a "Find All" search: http://www.askvg.com/guide-how-to-r...default-owner-of-a-file-or-folder-in-windows/)

Finally, please re-run SFC. Fingers crossed everything is now fixed.

Richard

Hello Tom, Hello Richard,

Your recommadations work this time.
I would like to thank you for the time you take helping me in that issue. (so don't think that you take me some of my "precious time".... it is me that feel graceful for the time "you" take helping me!
I appreciated working and learning from you.
I still not completly understand how SFC is working but will continue to read about this in the future

For now my system report no error running SFC, i suppose that is a good new!
The CBS.log still indicate that the process "cannot repair" somes files (the same ones) and that is very strange to me. (Usually a "clean system" do not show any "cannot repair" files in the CBS log....

If you have an explanation about his it surely help me understand furthermore... *smile*


Running SFC again only make the log growing in size without any signifiant change....

I include the log for you

Have a nice day and thank you again!

Continue your good work!

Jean

 

[niemiro]

I am really glad that SFC has now come back clean. This is good news.

If you have an explanation about his it surely help me understand furthermore... *smile*

Fortunately, there is a good explanation here.

CBS.log stores the results of many SFC runs, including all previous SFC runs. This is why it keeps growing in size.

If you look at the dates on the left, you will see that all SFC reported corruptions originate from as early as the 7th of December. Well, we know there were corruptions on the 7th December. This is nothing revolutionary.

What is important is whether the very final run of SFC reports errors. You can safely ignore all of these historic runs of SFC and any errors in them, as long as we have fixed them in the final run.

So slide down to the very bottom of the log, and look for SFC runs from late 10th December. Notice that at the very bottom of your log, the final SFC run reports no errors? This is the important one. No errors. :)

Your computer has a clean bill of health now. You are free to go. You may also delete your System Update Readiness Tool download to save space, if you wish, and any other logs or programs or batch files left over from our work here.

I am sorry this took a bit longer than usual, but thank you again for helping me help others. You truly have been an amazing person to work with.

Take care, and happy holidays,

Richard

 

[jean]

I am really glad that SFC has now come back clean. This is good news.

If you have an explanation about his it surely help me understand furthermore... *smile*

Fortunately, there is a good explanation here.

CBS.log stores the results of many SFC runs, including all previous SFC runs. This is why it keeps growing in size.

If you look at the dates on the left, you will see that all SFC reported corruptions originate from as early as the 7th of December. Well, we know there were corruptions on the 7th December. This is nothing revolutionary.

What is important is whether the very final run of SFC reports errors. You can safely ignore all of these historic runs of SFC and any errors in them, as long as we have fixed them in the final run.

So slide down to the very bottom of the log, and look for SFC runs from late 10th December. Notice that at the very bottom of your log, the final SFC run reports no errors? This is the important one. No errors. :)

Your computer has a clean bill of health now. You are free to go. You may also delete your System Update Readiness Tool download to save space, if you wish, and any other logs or programs or batch files left over from our work here.

I am sorry this took a bit longer than usual, but thank you again for helping me help others. You truly have been an amazing person to work with.

Take care, and happy holidays,

Richard

Hello Tom, Hello Richard,

Wonderful explanation Richard! That one make me really happy, it will surely contribute to make me live the holidays in a peace of mind!
I am a bit "shy" also to not have see that by myself! lol! I was too much focused on the errors and did not follow the whole process i guess....

Again, thank you for your help

I wish you both, a merry christmas and happy new year,

Jean

 

[niemiro]

I am really glad that SFC has now come back clean. This is good news.

If you have an explanation about his it surely help me understand furthermore... *smile*

Fortunately, there is a good explanation here.

CBS.log stores the results of many SFC runs, including all previous SFC runs. This is why it keeps growing in size.

If you look at the dates on the left, you will see that all SFC reported corruptions originate from as early as the 7th of December. Well, we know there were corruptions on the 7th December. This is nothing revolutionary.

What is important is whether the very final run of SFC reports errors. You can safely ignore all of these historic runs of SFC and any errors in them, as long as we have fixed them in the final run.

So slide down to the very bottom of the log, and look for SFC runs from late 10th December. Notice that at the very bottom of your log, the final SFC run reports no errors? This is the important one. No errors. :)

Your computer has a clean bill of health now. You are free to go. You may also delete your System Update Readiness Tool download to save space, if you wish, and any other logs or programs or batch files left over from our work here.

I am sorry this took a bit longer than usual, but thank you again for helping me help others. You truly have been an amazing person to work with.

Take care, and happy holidays,

Richard

Hello Tom, Hello Richard,

Wonderful explanation Richard! That one make me really happy, it will surely contribute to make me live the holidays in a peace of mind!
I am a bit "shy" also to not have see that by myself! lol! I was too much focused on the errors and did not follow the whole process i guess....

Again, thank you for your help

I wish you both, a merry christmas and happy new year,

Jean

It is indeed a nice explanation, isn't it :)

It has been a pleasure to work with you, and I am very glad your problems are now fixed.

And a happy Christmas to you too :)

Richard