sfc /scannow unable to fix corrupt files.

[devinator12]

Hello Sysnative forums!

I'm here today to request help in solving a problem that has gone from bad to worse.
Through my web searching i found this site though this post "https://www.sysnative.com/forums/windows-update/11769-sfc-scannow-cannot-repair-corrupted-files.html"

As the notes in the post recommended i am making a new request.

Please note files attached to this post.

Thank you for your time.
Devin C Smith

 

[BrianDrab]

Hi and welcome to Sysnative. Are you encountering any issue besides the message about being unable to fix corrupt files? The reason I ask is that the corruptions you have are a known issue and Microsoft will be providing a fix. The corruptions don't cause any Windows Update issues.

2015-05-25 14:46:36, Info                  CSI    00000338 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:Dk6fUP1SnCTleFraPRQVF4X7qKh8b/NoJA44WgQ6+JE=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-25 14:46:36, Info                  CSI    00000339 [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-25 14:46:36, Info                  CSI    0000033a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:a6gI0J5yvfGTOqcpiYLkzGXusnwKS2mJUXOwOYSGFFg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-05-25 14:46:36, Info                  CSI    0000033b [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-25 14:46:36, Info                  CSI    0000033c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :

More info on this is below. If you are not encountering any Windows Update errors then the errors you currently have can safely be ignored.

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.

 

[devinator12]

My system has been experiencing a processing bottleneck after playing GTA V. Also when i have exited the game tray icons of applications are gone. I'm worried of the computer breaking down at this point and time.

 

[BrianDrab]

The best I can do is to ensure that you don't have any Windows Update/Servicing issues (which you don't) and also to ensure that your disk is healthy and that you don't a have any memory issues. At that point another forum would be more appropriate.

1. Did you happen to do chkdsk?
2. Have you checked your disk for issues using any testing tool?
3. Have you tested your memory?

 

[devinator12]

I have run a chkdsk and found errors on the OS before i made the post and with the new logs. Windows gadgets was one of the things repaired.

HWInfo64 reports the hard drive S.M.A.R.T is all good.

Memory test has not been done. Should I use MemTest86 or a different tool?

 

[BrianDrab]

I have run a chkdsk and found errors on the OS before i made the post and with the new logs. Windows gadgets was one of the things repaired.

You may want to run this again to see if more is found. Hopefully not though.

HWInfo64 reports the hard drive S.M.A.R.T is all good.

I would probably run a short test and long test using the hard drive manufacturers testing tools. If they don't have one for your drive then you can use SeaTools HDD Diagnostics.

Memory test has not been done. Should I use MemTest86 or a different tool?

Yes. That's what I would do.

Test RAM With Memtest86+

Please ensure you allow 8 passes of the program!

Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

 

[Rich-M]

Usually when I see checkdisk repair errors or close drive segments I like to run Windows Drive Fitness Test
shown here: Windows Drive Fitness Test v0.95 Review (Free HD Test)
because I have my doubts about asking Seagate to test their own hard drive etc...and prefer to have an independent utility
do so that it casts no aspersions on its own products. Either that or I just replace the drive because what you found today
will more than likely make more issues tomorrow and who needs to take that chance?