[SOLVED] sfc scan can't repair all detected corruption

[Ronnz]

Hi all,

After installing Win 8.1 x 64 and all necessary software applications earlier this year, I encountered periodic and varying BSOD's over several months which had a common denominator in that amongst other things, they all pointed to possible driver errors. Driver Verifier found a problem with the driver for the NetWorx bandwidth monitor I use which turned out to be a known problem and was resolved by using a generic driver instead. No further BSOD's have occurred over the month since then.

I've also begun to experience a problem with File Explorer over the last month or so for no known reason. When creating a new folder, I am unable to rename the folder when using File Explorer and instead receive an error pop up stating: "An unexpected error is keeping you from renaming this folder. If you continue to receive this error, you can use the error code to search for help with this problem. Error 0x80004005:Unspecified error." Googling this hasn't been helpful but fortunately I also run Directory Opus which doesn't suffer from the problem and is allowing me to retrospectively rename new folders after they have been created using File Explorer.

I have run the sfc scan several times and then SFCFIX which reports as follows:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-07-04 10:38:16.908
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.

AutoAnalysis::
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-u..ed-telemetry-

client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-u..ed-telemetry-

client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-07-04 11:19:27.238
----------------------EOF-----------------------

Any help to get this sorted will be much appreciated.

Best regards,

Ronnz

 

[BrianDrab]

Hi and welcome to Sysnative. The two telemetry corruptions are a known issue that Microsoft is working on. They can safely be ignored. They don't affect the function of your machine. More info follows.

https://support.microsoft.com/en-us/kb/3022345

Originally Posted by Microsoft
This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

telemetry.ASM-WindowsDefault.json
utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.

So your issue is likely not related to Windows Update/Servicing however we can do one more check to me sure. Please do the following.

Step#1 - DISM /RestoreHealth Scan
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. Right-click on the Start
   
   button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
   Dism /Online /Cleanup-Image /RestoreHealth
3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
   copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
   
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
   Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

 

[Ronnz]

Hi and welcome to Sysnative. The two telemetry corruptions are a known issue that Microsoft is working on. They can safely be ignored. They don't affect the function of your machine. More info follows.

https://support.microsoft.com/en-us/kb/3022345

Originally Posted by Microsoft
This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

telemetry.ASM-WindowsDefault.json
utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.

So your issue is likely not related to Windows Update/Servicing however we can do one more check to me sure. Please do the following.

Step#1 - DISM /RestoreHealth Scan
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. Right-click on the Start
   
   button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
   Dism /Online /Cleanup-Image /RestoreHealth
3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
   copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
   
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
   Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Hello BrianDrab,

Thanks for the welcome and the especially quick reply. Good to know that things might not be as bad as first appeared. I actually ran SFCFix a couple of times before posting this thread and after the second occasion, found that about 60 of the corrupt files that sfc.exe had detected were repaired to leave just the ones I first uploaded here. SFCFix seems a pretty amazing repair tool.

I have done as you asked and the CBS.txt file is attached. Let me know whatever else you may need me to do.

Cheers,

Ronnz

 

[BrianDrab]

Those logs look clean. Just to be absolutely sure can you please do the following?

SFC Scan Again
1. Right-click on the Start

button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

 

[igorko]

Hello,
I have a similar problem.

 

[Ronnz]

Those logs look clean. Just to be absolutely sure can you please do the following?

SFC Scan Again
1. Right-click on the Start

button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

OK. Thank you. Have done as you asked.

 

[BrianDrab]

igorko - If you need assistance, please start your own thread and someone will assist you. Thank you.

Ronnz - Are you sure you followed the instructions and ran SFC /scannow ? The log you sent doesn't show that you ran this command.

 

[Ronnz]

Hi BrianDrab. Yes, I definitely ran SFC /scannow. However, I ran it as a user that has Admin privileges, same as I had done previously. Not sure if this accounts for the lack of evidence you report but I have run it again just now as Admin and the new CBS.txt file is attached. Hopefully that will give you the content you need.

 

[BrianDrab]

Yes, I see what I need now. All looks good so you are corruption free. If you still feel you have performance issues you may want to put an inquiry within our Windows 8 forum.

 

[Ronnz]

Thanks for that BrianDrab. I really appreciate your help.

This morning I explored the "Error 0x80004005: Unspecified error" issue a little which still remains and found that
using file explorer, I can't rename folders or move folders. I can however open files contained therein, extract files from .zip folders and delete folders. The issues do not affect any files: only the folders.

Directory Opus does not suffer from any of the defects reported above so I conclude that the problem is related to file explorer and on researching further, I came across this: Windows patch KB 3022345 triggers apparent sys file corruption | InfoWorld.

It seems that the Windows update has the potential to mess with File explorer so as my next step, I have in mind to simply uninstall the kb-3022345 and assume that given what you have done for me, there will be no need to follow the instructions set out here: The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files.

How does this sound to you?

Thanks again,

Ronnz

 

[BrianDrab]

Correct. You can uninstall the update. There is no way to permanently resolve the corruption until Microsoft fixes. It only resolves temporarily by following the instructions you pointed out above. I've never heard of this update messing with File Explorer so if you find that it does I would love to hear.

Thanks.

 

[Ronnz]

Correct. You can uninstall the update. There is no way to permanently resolve the corruption until Microsoft fixes. It only resolves temporarily by following the instructions you pointed out above. I've never heard of this update messing with File Explorer so if you find that it does I would love to hear.

Thanks.

Hi BrianDrab,

Maybe it was too much to hope for but at Page not found I read:

“After installation of the updated patch [May 6, KB 3022345], I experienced explorer.exe crashes (once after installing the patch and once today) which I had never experienced before.
.......I also know that this patch may not uninstall properly (at least on Windows 8).......”

“Had explorer crash again today so I decided to take a chance and uninstall KB3022345 on one of my other Win 7 Ultimate machines (this machine also manifested unrepairable SFC errors due to the May 5 issued KB3022345).
Uninstall results in the following:
1) Removes "Diagnostics Tracking Service."
2) Cold boots without issue. No errors/warnings in the event viewer.
3) SFC now reports "Windows Resource Protection did not find any integrity violations."
4) KB 3022345 reappears in the update chute.
It appears the uninstall was successful and resolved SFC corruption errors.

I've since received independent confirmation about this behavior from many sources, including reader Canadiantech, who apparently is working with version 4.”

Well, I uninstalled KB3022345 as planned and when I hid KB3022345 from the “update chute”, it went one better and immediately disappeared. Even checking for updates has not located it. Given the way MS has tried to foist the Windows 10 Upgrade upon users, I suspect the disappearance has to do with what I suspect is their strong intent to load literal tracking software onto all Windows machines. As far as productivity is concerned, “updating” from XP to 8.1 this year has been a right royal disaster. Never again will I accept anything on face value that is issued under the MS brand, but I digress....

I then found that my File explorer folder behavior errors were still there. However, re-running sfc.exe detects the same 8 errors relating to KB3022345 so it appears not to have uninstalled properly. In case you should want to check, the latest CBS.txt file is attached.

From what I can see, short of a system refresh or worse, a reset, the remaining options are to:

1. Fully uninstall update KB3022345 (and never install it again) or,
2. Find and fix the cause of the file explorer error or,
3. Roll the registery back to a point prior to both the start file explorer error and the KB3022345 install.

Given the scarcity of material on the internet for fixing the Error 0x80004005, unless you have some thoughts on either options 1 or 2, is option 3 a goer? I presume that if it fixes the explorer issue, it will necessitate running sfc.exe again just to be sure.

Sorry to be a pain.

Ronnz

 

[Ronnz]

Correct. You can uninstall the update. There is no way to permanently resolve the corruption until Microsoft fixes. It only resolves temporarily by following the instructions you pointed out above. I've never heard of this update messing with File Explorer so if you find that it does I would love to hear.

Thanks.

Hi BrianDrab,

Maybe it was too much to hope for but at Page not found I read:

“After installation of the updated patch [May 6, KB 3022345], I experienced explorer.exe crashes (once after installing the patch and once today) which I had never experienced before.
.......I also know that this patch may not uninstall properly (at least on Windows 8).......”

“Had explorer crash again today so I decided to take a chance and uninstall KB3022345 on one of my other Win 7 Ultimate machines (this machine also manifested unrepairable SFC errors due to the May 5 issued KB3022345).
Uninstall results in the following:
1) Removes "Diagnostics Tracking Service."
2) Cold boots without issue. No errors/warnings in the event viewer.
3) SFC now reports "Windows Resource Protection did not find any integrity violations."
4) KB 3022345 reappears in the update chute.
It appears the uninstall was successful and resolved SFC corruption errors.

I've since received independent confirmation about this behavior from many sources, including reader Canadiantech, who apparently is working with version 4.”

Well, I uninstalled KB3022345 as planned and when I hid KB3022345 from the “update chute”, it went one better and immediately disappeared. Even checking for updates has not located it. Given the way MS has tried to foist the Windows 10 Upgrade upon users, I suspect the disappearance has to do with what I suspect is their strong intent to load literal tracking software onto all Windows machines. As far as productivity is concerned, “updating” from XP to 8.1 this year has been a right royal disaster. Never again will I accept anything on face value that is issued under the MS brand, but I digress....

I then found that my File explorer folder behavior errors were still there. However, re-running sfc.exe detects the same 8 errors relating to KB3022345 so it appears not to have uninstalled properly. In case you should want to check, the latest CBS.txt file is attached.

From what I can see, short of a system refresh or worse, a reset, the remaining options are to:

1. Fully uninstall update KB3022345 (and never install it again) or,
2. Find and fix the cause of the file explorer error or,
3. Roll the registery back to a point prior to both the start file explorer error and the KB3022345 install.

Given the scarcity of material on the internet for fixing the Error 0x80004005, unless you have some thoughts on either options 1 or 2, is option 3 a goer? I presume that if it fixes the explorer issue, it will necessitate running sfc.exe again just to be sure.

Sorry to be a pain.

Ronnz

Not sure why the link to the page at InfoWorld - Technology insight for the enterprise failed but the article is entitled: "Windows patch KB 3022345 triggers apparent sys file corruption" and is attached.

 

[BrianDrab]

If it were me I would try option #2 (Find and fix the cause of the file explorer error or,). I would suggest posting an inquiry in our Windows 8 forum. Let them know you were checked out and cleared from the Windows Update forum so they don't go down that road. Also, let me know if they don't get back to you.

 

[Ronnz]

Thank you for all your help. I have posted a new thread in the Windows 8 forum as suggested. It's great to know that there are knowledgeable guys around who have the humanity to share what they have learned for the benefit or others.

Best regards,

Ronnz