DISM error

Question

I ran sfc /scannow and got a number of issues that could not be repaired.

I copied the issues at the end of this post. About the first (Unified telemetry client) I read that it was a  false positive.

Here in Microsoft community I then read that I should try running the DISM.

This gave an error.

I also tried starting windows update service first but still got error message.

This is a screenimage;

;

I have the CBS and DISM logs but do not know how to add them here.

For the CBS log I copied all the issues that could not be repaired:

2015-08-17 20:26:57, Info                  CSI    000004d1 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\0e238d4c1ad9d001387e0000ec21a023\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:hyDk3BXuVEmGLmMMYKyiT59XkHrpGhm9a4DXTb14jjU=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-08-17 20:26:57, Info                  CSI    000004d2 [SR] Cannotrepair 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-08-17 20:26:57, Info                  CSI    000004d3 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\0e238d4c1ad9d001387e0000ec21a023\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:uJb1xc+7UfB0sWDxWhgMheOSADljkxkTslfhp7nidZg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-08-17 20:26:57, Info                  CSI    000004d4 [SR] Cannotrepair 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-08-17 20:26:59, Info                  CSI    000004d5 [DIRSD OWNER WARNING] Directory [ml:520{260},l:94{47}]"??\C:\Windows\diagnostics\system\UsbCore\nl-NL" is not owned but specifies SDDL in component Microsoft-Windows-UsbCoreDiagnostic.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-17 20:27:00, Info                  CSI    000004d6 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\381d5e4e1ad9d001637e0000ec21a023\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:hyDk3BXuVEmGLmMMYKyiT59XkHrpGhm9a4DXTb14jjU=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-08-17 20:27:00, Info                  CSI    000004d7 [SR] Cannotrepair 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-08-17 20:27:00, Info                  CSI    000004d8 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"

2015-08-17 20:27:00, Info                  CSI    000004d9 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\381d5e4e1ad9d001637e0000ec21a023\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:uJb1xc+7UfB0sWDxWhgMheOSADljkxkTslfhp7nidZg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-08-17 20:27:00, Info                  CSI    000004da [SR] Cannotrepair 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-08-17 20:27:00, Info                  CSI    000004db [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"

_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-17 20:34:25, Info                  CSI    00000943 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\eb3bfc571bd9d001a7ca0000ec21a023\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:hyDk3BXuVEmGLmMMYKyiT59XkHrpGhm9a4DXTb14jjU=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-08-17 20:34:25, Info                  CSI    00000944 [SR] Cannotrepair 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-08-17 20:34:25, Info                  CSI    00000945 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\eb3bfc571bd9d001a7ca0000ec21a023\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:uJb1xc+7UfB0sWDxWhgMheOSADljkxkTslfhp7nidZg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-08-17 20:34:25, Info                  CSI    00000946 [SR] Cannotrepair 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-08-17 20:34:26, Info                  CSI    00000947 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :

Found: {l:32 b:v1Esz8BVi8FeeaBNfwKwB//e7r3kwk6AGPLRTf5jsbc=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

1. Re: Microsoft-Windows-Unified-Telemetry-Client corrupt files: "utc.app.json" & "telem

Hi Stijn :)

These files are falsely reported as corrupt by SFC. Microsoft is aware of this situation and they said that this issue will be fixed in a later update. These files aren't corrupt and they won't affect anything on your system. You can leave it be without any consequences. For more information, see the Microsoft Article below.

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

This update contains the following files 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 actual corruption on a device running this update, and a later service update will resolve this issue.

2015-08-17 20:34:26, Info                  CSI    00000948 [SR] Cannotrepair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-08-17 20:34:26, Info                  CSI    00000949 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :

Found: {l:32 b:v1Esz8BVi8FeeaBNfwKwB//e7r3kwk6AGPLRTf5jsbc=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

2015-08-17 20:34:26, Info                  CSI    0000094a [SR] Cannotrepair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-08-17 20:34:26, Info                  CSI    0000094b [SR] This component was referenced by [l:166{83}]"Package_2709_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-6825_neutral_GDR"

2015-08-17 20:34:26, Info                  CSI    0000094c Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\89037d581bd9d001b0ca0000ec21a023\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:hyDk3BXuVEmGLmMMYKyiT59XkHrpGhm9a4DXTb14jjU=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

2015-08-17 20:34:26, Info                  CSI    0000094d [SR] Cannotrepair 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-08-17 20:34:26, Info                  CSI    0000094e [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"

2015-08-17 20:34:26, Info                  CSI    0000094f Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\89037d581bd9d001b0ca0000ec21a023\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:uJb1xc+7UfB0sWDxWhgMheOSADljkxkTslfhp7nidZg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

2015-08-17 20:34:26, Info                  CSI    00000950 [SR] Cannotrepair 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-08-17 20:34:26, Info                  CSI    00000951 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"

Answer 1

ZigZag's download link was for 10.

@@@@@@@@@@@@@@@@@@@@@@@

You are correct; Telemetry is a false positive in the results.

Where you have problems with corrupt files there is a certain path that you follow.

The next progressive step after DISM fails is R efresh > then Reset if necessary.

Here is how it works from SFC > DISM > Refresh > Reset

And these eightforums.com Tutorials are very detailed for problems resulting from SFC Scan:

"How to Run "SFC /SCANNOW" Command at Boot or in Windows 8 and 8.1"

http://www.eightforums.com/tutorials/3047-sfc-scannow-command-run-windows-8-a.html

Read this Section there in conjunction with the rest of the information they give in above link.

   Note

If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 times restarting the PC after each time to completely fix everything that it's able to.

If not, then run the **Dism /Online /Cleanup-Image /RestoreHealth**command to repair any component store corruption,

Repair-WindowsImage -Online -CheckHealthRepair-WindowsImage -Online -ScanHealthRepair-WindowsImage -Online -RestoreHealth

Restart the PC afterwards, and try the sfc /scannow command again.

If still not, then try using OPTION ONE above to run the sfc /scannow command at boot

If still not, then you could do a refresh of Windows 8, or run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.

If still not, then you can use the steps in the TIP box in the OPTION THREE section to manually replace the files that SFC could not fix.

__________________________________________________

"How to Refresh Windows 8 and Windows 8.1"

http://www.eightforums.com/tutorials/2293-refresh-windows-8-a.html

Refreshing your PC goes like this:

• The PC boots into Windows RE (RecoveryEnvironment).
• Windows RE scans the hard drive for your data, settings, and apps, and puts them aside (on the same drive).
• Windows RE installs a fresh copy of Windows.
• Windows RE restores the data, settings, and apps it has set aside into the newly installed copy of Windows.
• The PC restarts into the newly installed copy of Windows.

_________________________________________________

"How to Reset Windows 8 and Windows 8.1"

http://www.eightforums.com/tutorials/2302-reset-windows-8-a.html

"When you reset your PC, the drive will be completely reset, and all your apps and files will be removed from it. Windows 8 will be reinstalled, and you'll need to change any settings and reinstall any apps that you want to get back after resetting. If you know if any files that you don't want to lose, then you should back those files up before starting the reset"

Cheers.

Answer 2

Hi,

Please see the post marked as Answer in this thread:

http://answers.microsoft.com/en-us/windows/forum/windows_8-update/error-when-running-dism-online-cleanup-image/f9fffd60-85ff-448d-b95e-b03ed95cc4b3

Answer 3

Thanks to both of you for your very fast response.

Indeed the PC is Windows 8.1 Pro - I never said it was Windows 10 or did I?

So I am now downloading the installation media Bill Smithers pointed me to.

Once this will be done I will use the instruction ZigZag gave

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:T:\Sources\Install.wim:1 /LimitAccess 

Would that be the correct instruction having downloaded the Iso to T?

Answer 4

Hi,

Here is the information about Telemetry.

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

@@@@@@@@@@@@@@@@@@@@@@@@

And you have Windows 8.1, not 10.

Here is the correct information t download Windows 8.1.

"Create installation media for Windows 8.1"

http://windows.microsoft.com/en-us/windows-8/create-reset-refresh-media

A similar Tutorial which may also assist you

"Create Installation Media for Windows 8.1"

http://winsupersite.com/windows-8/create-installation-media-windows-81

In the first screen of this very simple wizard, you need to choose the following:

Language. English – en-us if you're in the United States.

Edition. Windows 8.1 (Core), Windows 8.1 N, Windows 8.1 Pro, Windows 8.1 Pro N, or Windows 8.1 Single Language.

Architecture. 64-bit (x64 ) or 32-bit (x86).

Cheers.

Answer 5

If you get the error message "cannot find source files" you need to have an ISO file mounted and need to specify where it is located with the below command

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess  Where "X" is the drive letter where the ISO is located.  Simply change the "X" to the correct drive letter

**If you do not have an ISO you can make one.  The instructions are http://microsoft-news.com/download-windows-10-build-10041-iso-image/**[here](http://www.microsoft.com/en-us/software-download/windows10)