[SOLVED] telemetry.ASM-WindowsDefault.json

D

Devilpup007

Member
Joined
May 17, 2015
Posts
7
HELP: New AMD build. Windows 7 pro. Won't update. Crashes during Sys Test.

CFC scan:
CSI 00000516 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-05-17 10:25:35, Info CSI 00000518 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-05-17 10:25:35, Info CSI 0000051a [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-05-17 10:25:35, Info CSI 0000051b [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
2015-05-17 10:25:35, Info CSI 0000051d [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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-05-17 10:25:35, Info CSI 0000051e [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
2015-05-17 10:25:35, Info CSI 00000521 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
2015-05-17 10:25:36, Info CSI 00000524 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
 
Hi and welcome to Sysnative. This is a common problem that has been happening as of late. Please do the following to fix the corruption.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  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

Step#2 - SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please zip/attach this to your next post.

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.
Items for your next post
1. SFCFix log
2. CBS log
 

Attachments

BrianDrab said:
Hi and welcome to Sysnative. This is a common problem that has been happening as of late. Please do the following to fix the corruption.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  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

Step#2 - SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please zip/attach this to your next post.

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.
Items for your next post
1. SFCFix log
2. CBS log
Click to expand...

Thank you...timing obligation here. Respond back later today with logs. Thank you for your assistance!!!
 
Yeah ran that. Came back with sfc check clean. Still won't update. Downloaded update diagnostic. Came back with:
Windows Update error 0x80073712(2015-05-17-T-11_07_49A) - Not fixed
Cryptographic service components not registered - Not fixed
 
Thanks for the info. Please do the following so we can identify other issues.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
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.
 
BrianDrab said:
Thanks for the info. Please do the following so we can identify other issues.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
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.
Click to expand...

see attachment
 

Attachments

Thanks. We'll have to do this in two passes. Let's first fix all the missing/corrupt files.

Step#1 - Fix Missing/Corrupt Files
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. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files). If the Manifests folder doesn't exist within Winsxs you will need to create it.
    C:\Windows\Temp\CheckSur\Winsxs\Manifests
  6. Open the Packages folder and copy the files into the following folder (if there are any files). If the Packages folder doesn't exist within Servicing you will need to create it.
    C:\Windows\Temp\CheckSur\Servicing\Packages
  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, zip up and attach the following log file:
    C:\Windows\Logs\CBS\CheckSUR.log
 

Attachments

BrianDrab said:
Thanks. We'll have to do this in two passes. Let's first fix all the missing/corrupt files.

Step#1 - Fix Missing/Corrupt Files
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. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files). If the Manifests folder doesn't exist within Winsxs you will need to create it.
    C:\Windows\Temp\CheckSur\Winsxs\Manifests
  6. Open the Packages folder and copy the files into the following folder (if there are any files). If the Packages folder doesn't exist within Servicing you will need to create it.
    C:\Windows\Temp\CheckSur\Servicing\Packages
  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, zip up and attach the following log file:
    C:\Windows\Logs\CBS\CheckSUR.log
Click to expand...

BrianDrab, will this work with my computer also? I have posted a thread that is similar to this problem on the Windows 7 / Vista Problems forum. Would like to get this resolved. Thanks in advance any help on this.
 
JCF2015 -

There is no reason to fix this corruption at this point. Microsoft has acknowledged it and is going to fix it. If we fix the corruption now it's likely to just come back. It doesn't hurt the function of Windows Update so you should be fine.


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


quote_icon.png
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.
Click to expand...
 
BrianDrab said:
JCF2015 -

There is no reason to fix this corruption at this point. Microsoft has acknowledged it and is going to fix it. If we fix the corruption now it's likely to just come back. It doesn't hurt the function of Windows Update so you should be fine.


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


quote_icon.png
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.
Click to expand...
Click to expand...
 
Hello Brian

I was brought to this site by a Google search for PublicKeyToken {1:8 b:31bf3856ad364e35}. After reading through the thread I think I'm having a similar problem. Here are the sfc details that I can't get resolved.

-16 19:58:15, Info CSI 00000200 [SR] Beginning Verify and Repair transaction
2015-08-16 19:58:15, Info CSI 00000202 [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_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-16 19:58:15, Info CSI 00000204 [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_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-16 19:58:15, Info CSI 00000206 [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_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-16 19:58:15, Info CSI 00000207 [SR] This component was referenced by [l:158{79}]"Package_168_for_KB3068708~31bf3856ad364e35~x86~~6.1.1.0.3068708-604_neutral_GDR"
2015-08-16 19:58:15, Info CSI 00000209 [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_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-16 19:58:15, Info CSI 0000020a [SR] This component was referenced by [l:158{79}]"Package_168_for_KB3068708~31bf3856ad364e35~x86~~6.1.1.0.3068708-604_neutral_GDR"
2015-08-16 19:58:15, Info CSI 0000020d [SR] Repair complete
2015-08-16 19:58:15, Info CSI 0000020e [SR] Committing transaction
2015-08-16 19:58:16, Info CSI 00000212 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

I'm trying to upgrade from 7 to 10. Can you direct me to a solution?
Thanks Jim
 
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