Solved How I fixed DISM :)

David Bailey

Banned
Messages
10,485
Location
Harrisonburg, Va.
With Windows 10 coming out the end of July some of you may not be interested in fixing---

Dism /Online /Cleanup-Image /RestoreHealth

Others who stick with Windows 8.1 Pro or regular may find this fix useful.

So to proceed.

I thought the latest Windows Updates had fixed dism.
Wrong.

My mind wanders & I forgot I did the following in an attempt to fix dism.

I used---

Tweaking.com - Windows Repair

To make changes in my 8.1 Pro system.

See picture---

screenshot_274.jpg

To get an easy way to boot to safe mode with networking install---

Boot UI Tuner

screenshot_275.jpg

Also set WMI to Automatic & Running before running dism---

screenshot_276.jpg

Then after running dism you should see----

screenshot_277.jpg

Ignore the sfc results as the errors are caused by the telemetry files from a Windows bad update. :(

Notice the time & date of the scan---

screenshot_279.jpg
 
Good job, David .This was used by some for SFC issues with that update, for me i removed that update for now, hopefully Win10 have better cure The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files

Like I said, ignore the 2 sfc corruptions---

The two corrupt files are:Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]”telemetry.ASM-WindowsDefault.json” :
Found: {l:32 b:X5paRQlbw2v00Wlbryh/shTCSngPuV5NMY9IyDEs/HI=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json do not match actual file [l:24{12}]”utc.app.json” :

Found: {l:32 b:JUC5i/5VApK5qT3QXfHsgN0T00T8uKFsDtICSI+MdPc=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

If dism is fixed by my method the component store is fixed & the other sfc corruptions are fixed. :)
 
Good job, David .This was used by some for SFC issues with that update, for me i removed that update for now, hopefully Win10 have better cure The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files

Like I said, ignore the 2 sfc corruptions---

The two corrupt files are:Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]”telemetry.ASM-WindowsDefault.json” :
Found: {l:32 b:X5paRQlbw2v00Wlbryh/shTCSngPuV5NMY9IyDEs/HI=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json do not match actual file [l:24{12}]”utc.app.json” :

Found: {l:32 b:JUC5i/5VApK5qT3QXfHsgN0T00T8uKFsDtICSI+MdPc=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

If dism is fixed by my method the component store is fixed & the other sfc corruptions are fixed. :)

Ahh, o.k. i see !! Since update is not so important, not causing me an issue i'll wait since i reserved Windows 10, thanks !
 
Here lately I get a message at the last sfc run saying the fixes will take effect after the next reboot.

Never got that message in the past.

So I restart like it says to.
 
Here lately I get a message at the last sfc run saying the fixes will take effect after the next reboot.

Never got that message in the past.

So I restart like it says to.

Never saw that message when running into problem with SFC fixing corrupt files, but most say it may take a few reboots to fix even after a Dism. Even though we knew it was due to this update KB3022345, i recently had to reinstall windows 8.1 did all my updates and that update never came back yet and no SFC or DISM issues at all, ran numerous times. Now this one did come back for the same reasons as other update KB3068708. Go figure !
https://support.microsoft.com/en-us/kb/3068708
 
Good to hear.

I have too many things to replace to reinstall my OS.
I got it fixed so I'll wait & see what Microsoft does.

Microsoft is supposed to put out a fix soon.
So they say.

edit- In the future I won't be using Windows Update Cleanup any more so I'll be able to uninstall unwanted Updates. :)
 
Good to hear.

I have too many things to replace to reinstall my OS.
I got it fixed so I'll wait & see what Microsoft does.


Microsoft is supposed to put out a fix soon.
So they say.

edit- In the future I won't be using Windows Update Cleanup any more so I'll be able to uninstall unwanted Updates. :)


Thanks, yes, have to replace all those themes ;)
Micorsoft fixes...hmmm like this one i have same issues been following, so they say,o.k. yeah right !! Possibly in next OS Win 10
http://www.eightforums.com/bsod-cra...s-errors-startup-metadata-staging-failed.html

And how going to uninstall updates ? Can just go to C:\WINDOWS\SYSTEM32\Software Distribution\Download folder delete them there too. As disk cleanup takes forever to do this on some systems.
 

Wow, latched in there like a virus :shock: possible some other update is preventing it from you uninstalling it, did you try it here, sure you have ? Weird how reinstall for me did not cause it. Maybe some optional other updates you took lately.

Untitled.jpg

Guess as you felt be fixed with new OS, so you will have to see on July 29th how SFC works.
 
A quote from Microsoft-
{update KB3022345}

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.
 
A quote from Microsoft-
{update KB3022345}

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.

When will that be, any dates for resolve ? Never felt caused me an issues before i did uninstall it, although strange as has not come back, unless it did under different KB number as important update.
 
Hi, David,
I used your program and ran it as instructed.
The wole repair process took about 30 minutes.

However. when running the Dism commands I get the following still:
Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>Dism /Online /Cleanup-Image /StartComponentCleanup


Deployment Image Servicing and Management tool
Version: 6.3.9600.17031


Image Version: 6.3.9600.17031


[==========================100.0%==========================]


Error: 14098


The component store has been corrupted.


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth


Deployment Image Servicing and Management tool
Version: 6.3.9600.17031


Image Version: 6.3.9600.17031


[==========================100.0%==========================]


Error: 14098


The component store has been corrupted.


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


C:\WINDOWS\system32>

The update search is still not working neither.
Where do I go from here, please?
 
Back
Top