sfc /scannow cannot repair corrupted files after CCleaner registry clean

quentin101 · Sep 2, 2015

Hello everyone !

I'm on Windows 7 x64.

I post here after seeing this thread : https://www.sysnative.com/forums/windows-update/11769-sfc-scannow-cannot-repair-corrupted-files.html

As I said in the title, after cleaning/repairing the registry with CCleaner (which was a bad idea and seems to do nothing after I did some research -_-'), the computer did a nice BSOD, talking about DRIVER_irql_not_less_or_equal and CLASSPNP.SYS.

I got to the solution of doing a sfc /scannow and I found some corrupted files, but the tool wasn't able to repair it. I also used the Dism /Online /Cleanup-Image /CheckHealth and it also found 4 corrupted files according to the log. Here is the Dism log (the sfc log seems too big to be upload here...)View attachment CheckSUR-Dism_log.txt

So I'm here to ask if someone could give me the same specific script that someone developed for the previous thread.
While this, I'll try to get a Win7 disk to launch a Windows repair.

Thanks for reading and paying attention to my post, sorry for some english mistakes :thumbsup2:

tom982 · Sep 2, 2015

Hello quentin101, welcome to Sysnative!

Firstly, your English is excellent so don't worry about that.

The errors in your CheckSUR log are nothing to worry about. Due to a mistake by Microsoft, those packages aren't named in the normal format and because of this, tools flag them as a problem.

This will upload your CBS log to me, which I can check for errors:

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.

[sfcfixdownload]Download SFCFix[/sfcfixdownload] (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u...ts/~Generic/Collect/CBS/SFCFixScript.txt?dl=1

Regarding your BSOD problem, I recommend you post in our BSOD forum: https://www.sysnative.com/forums/bs...ng-instructions-windows-10-8-1-8-7-vista.html

Some of the best analysts are here at Sysnative and I'm sure they'll be able to get you up and running.

Tom

LogBot · Sep 3, 2015

Logfile submission from quentin101

Logfile submission from quentin101.

The logfiles are available at: https://www.sysnative.com/niemiro/fileDistribution/2015-09/6525.zip

quentin101 · Sep 3, 2015

Re: Logfile submission from quentin101

Hi Tom, thanks for your quick answer.

Here is the SFCFix.txt :

Code:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-09-03 10:23:53.558
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Edith\Desktop\SFCFixScript.txt [0]




Collect:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-09-03 10:38:15.146
----------------------EOF-----------------------

Also, I didn't see the program finish at 100%, when I come back to the PC Avast was analizing SFCFix.exe. Hope it didn't messed up the thing.

Now, I'm going to collect all the computer's informations to post on the BSOD forum, I don't know this PC, it isn't mine -_-'

Quentin.

tom982 · Sep 3, 2015

Hi quentin,

I've reviewed your log and these are the files it's detected:

Code:

2015-09-02 13:08:03, Info                  CSI    00000359 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-09-02 13:08:03, Info                  CSI    0000035a [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-09-02 13:08:03, Info                  CSI    0000035b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:gjV6+IPBrpEZS/JCJakDHCFmoTeES1ACzz83yCz1Myk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-09-02 13:08:03, Info                  CSI    0000035c [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-09-02 13:08:03, Info                  CSI    0000035d Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-09-02 13:08:03, Info                  CSI    0000035e [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-09-02 13:08:03, Info                  CSI    0000035f [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-09-02 13:08:03, Info                  CSI    00000360 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:gjV6+IPBrpEZS/JCJakDHCFmoTeES1ACzz83yCz1Myk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-09-02 13:08:03, Info                  CSI    00000361 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

This was a bug in a Windows Update which has recently been fixed in KB3068708. This update should be offered through Windows Update, but if not you can download and install it from here:

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

Tom

quentin101 · Sep 3, 2015

Hi Tom,

I already got this update, installed the 15/06/2015.

Quentin

tom982 · Sep 3, 2015

Hi Quentin,

Really sorry about that, I linked the wrong update. Try this:

https://support.microsoft.com/fr-fr/kb/3080149

Fixes a previous issue in the Diagnostics Tracking Service where when an advanced user applied the System File Checker Tool (sfc.exe), the .json files were unintentionally flagged as corrupt. This unintentional marking didn’t affect or indicate actual corruption on a device, and after you apply this update the files should no longer be marked as corrupt.

Tom

quentin101 · Sep 5, 2015

Hey, little update !

I installed it, now I wait for the Verifier results, even though I don't know when this thing will be over, and how I will know if there will be a problem or not...

Thanks btw :wave:

Quentin

Search

Search

sfc /scannow cannot repair corrupted files after CCleaner registry clean

quentin101

Member

tom982

Emeritus

LogBot

Well-known member

quentin101

Member

tom982

Emeritus

quentin101

Member

tom982

Emeritus

quentin101

Member