Solved Dism and sfc erros

[Cliff S]

It's not the DISM log that needs to be looked at, it's the CBS log at C:\Windows\Logs\CBS\CBS.log that shows repairs and pending repairs and repair failures of sfc /scannow.

At the bottom you will see:

2015-06-27 10:34:15, Info CSI 000008e6 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\70f75f0db4b0d0017cc40000ac17cc0d\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:wAJrdSTUawhs/RawsiNg9RRQFQ6oQM8We6AJ/auSGyM=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-06-27 10:34:15, Info CSI 000008e7 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, 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-06-27 10:34:15, Info CSI 000008e8 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\70f75f0db4b0d0017cc40000ac17cc0d\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:iOgJ9zpM/uQDvt0owjVftLgMNGL/hKwbMjRM5vyAQDk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-06-27 10:34:15, Info CSI 000008e9 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, 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-06-27 10:34:15, Info CSI 000008ea Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\bc04630db4b0d0017fc40000ac17cc0d\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:wAJrdSTUawhs/RawsiNg9RRQFQ6oQM8We6AJ/auSGyM=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-06-27 10:34:15, Info CSI 000008eb [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, 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-06-27 10:34:15, Info CSI 000008ec [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
2015-06-27 10:34:15, Info CSI 000008ed Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\bc04630db4b0d0017fc40000ac17cc0d\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:iOgJ9zpM/uQDvt0owjVftLgMNGL/hKwbMjRM5vyAQDk=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-06-27 10:34:15, Info CSI 000008ee [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, 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-06-27 10:34:15, Info CSI 000008ef [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
2015-06-27 10:34:15, Info CSI 000008f0 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-06-27 10:34:15, Info CSI 000008f1 [SR] Repair complete
2015-06-27 10:34:15, Info CSI 000008f2 [SR] Committing transaction
2015-06-27 10:34:15, Info CSI 000008f3 Creating NT transaction (seq 2), objectname [6]"(null)"
2015-06-27 10:34:15, Info CSI 000008f4 Created NT transaction (seq 2) result 0x00000000, handle @0x7d8
2015-06-27 10:34:15, Info CSI 000008f5@2015/6/27:08:34:15.973 Beginning NT transaction commit...
2015-06-27 10:34:15, Info CSI 000008f6@2015/6/27:08:34:15.993 CSI perf trace:
CSIPERF:TXCOMMIT;31649
2015-06-27 10:34:15, Info CSI 000008f7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired


They will show up in the command prompt as not repairable but are just false positives. They cannot be repaired, because, there is nothing to repair, nothing to get pedant about. If you have other corruptions post the CBS log.

 

[solitario]

View attachment CBS.log

 

[axe0]

@Cliff S, all I'm seeing is corruption with amd64.

 

[solitario]

The Dism tells me that the file or directory is damaged or is illegible. Error: 1392

​

 

[Cliff S]

2015-06-27 05:25:35, Info CBS Reboot mark set
2015-06-27 05:25:35, Info CBS Winlogon: Registering for CreateSession notifications
2015-06-27 05:28:54, Info CBS Repr: CBS Store check completes
2015-06-27 05:28:56, Info CSI 00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xd61c8af8b0
2015-06-27 05:28:56, Info CSI 00000003 Creating NT transaction (seq 1), objectname [6]"(null)"
2015-06-27 05:28:56, Info CSI 00000004 Created NT transaction (seq 1) result 0x00000000, handle @0x3d4
2015-06-27 05:28:56, Info CSI 00000005 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2015-06-27 05:28:56, Info CSI 00000006@2015/6/27:08:28:56.252 Beginning NT transaction commit...
2015-06-27 05:28:56, Info CSI 00000007@2015/6/27:08:28:56.346 CSI perf trace:
CSIPERF:TXCOMMIT;146048
2015-06-27 05:28:56, Info CSI 00000008 CSI Store 919587567904 (0x000000d61bb0b920) initialized
2015-06-27 05:28:56, Info CSI 00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:78{39}]"6.3.9600.17709 (winblue_r9.150219-1500)".
2015-06-27 05:28:56, Info CSI 0000000a@2015/6/27:08:28:56.440 Starting corruption detection (InnerFlags=5)
This is at the end of the log the highlighted shows it needs a reboot to repair. Reboot your PC and run sfc /scannow again then reboot one more time then post new log.

Note: when running sfc /scannow and it finds errors you should always reboot and run again... it can take a few tries to repair, with the exception to date the two things in that link I gave you.

 

[axe0]

Pretty much the same as what I said

Also try this command:
Dism /Online /Cleanup-Image /AnalyzeComponentStore

This command could give more information

 

[Cliff S]

For the difference between sfc and dism see these two links:

System File Checker (sfc) --SFC: Scans and verifies the integrity of all protected system files and replaces incorrect versions with correct versions.

Deployment Image Servicing and Management Technical Reference--DISM: You can use it to install, uninstall, configure, and update Windows features, packages, drivers, and international settings

 

[solitario]

The Dism axe0 gave me the following output:

Components warehouse information:
Size of Windows explorer 8.43 gb
Actual size of components warehouse: 8.32 gb
Shared with windows: 5.01 gb
Backups and features disabled: 1.68 gb
Cahce and temporary data: 1.62 gb

Date of final cleaning: 26/6/2015

Number of enforceable packets: 0
Cleaning the warehouse of components is recommended: No

The operation completed successfully.
​

 

[Cliff S]

Then your WinSxS(Windows side by side files) do not need to be cleaned up.

Clean Up the WinSxS Folder

 

[solitario]

Does which fix this problem?
Many thanks to both.

axe0 do I did as requested and now what? Thanks a lot.

​

Best regards.

​

 

[Cliff S]

You need to do as I said in post# 25:

This is at the end of the log the highlighted shows it needs a reboot to repair. Reboot your PC and run sfc /scannow again then reboot one more time then post new log.

Note: when running sfc /scannow and it finds errors you should always reboot and run again... it can take a few tries to repair, with the exception to date the two things in that link I gave you.

 

[solitario]

Why before the dism not gave me the error 1392?
The sfc/scannow always stays in 96% even if you restart.
I changed the files you mention are corrupt manually with a live cd of ubuntu by other versions of the files.
Thanks a lot.
Best regards.
​

View attachment CBS.log
​

 

[Cliff S]

SFC might look like it's frozen or stopped but it hasn't just leave it running in the background. Sometimes it jumps ahead if a repair takes awhile

 

[solitario]

And what is recommended to do?
Thanks a lot.
Best regards.
​

 

[solitario]

Right now I'm doing a Dism/online /Cleanup-Image /RestoreHealth
​

 

[axe0]

Try sfc/scannow a couple of times, reboot after every sfc/scannow.

 

[solitario]

Not can you provide me a copy of the files that I have corrupt to replace them manually? Specifying the path. It is the only solution that I can think of.
Thanks a lot.
Best regards.
​

 

[solitario]

axe0 ok.
I'll do what you say.
Greetings and thanks.
​

 

[solitario]

Try sfc/scannow a couple of times, reboot after every sfc/scannow.

I think that I am not going to have good results. For three days I am rebooting and doing the sfc
​

 

[Cliff S]

The best advice give is from axe0 in post #9. Just run it through reboot and do it again. Be patient let it run through, and do not stop it before it is finished. If only those two false positives show up(telemetry.ASM-WindowsDefault.json & utc.app.json) at the end of the scan, you are done and don't need to do anything further,