Problems with Windows Update

[troslim]

As the title suggests, I have been getting some problems with Windows Update. Updates don't seem to be installed, I mostly get an error with the code 800F0902 or 800F081F, sometimes it gets 'stuck' on downloading the updates. Hope anyone of you guys can help me out.
System specs: Intel(R) Core(TM) i5-3350P CPU @ 3.10GHz, Video Card AMD Radeon HD 7000 series, Memory 8.2 GB, Microsoft Windows 8 (build 9200), 64-bit

 

[David Bailey]

Running---

Dism /Online /Cleanup-Image /RestoreHealth

and then---

sfc /scannow

in admin CMD prompts might help.

Restart after running them.

 

[troslim]

Running---

Dism /Online /Cleanup-Image /RestoreHealth

and then---

sfc /scannow

in admin CMD prompts might help.

Restart after running them.

I ran Dism /Online /Cleanup-Image /RestoreHealth, but then I get the following error: 0x800f0906

http://i.gyazo.com/e10092bbdb466a991a8ed37cf75a8580.png

 

[David Bailey]

If dism has errors I don't know how to fix the problem.

 

[Superfly]

This may help: Repair Corrupt Windows Image - Error 0x800f0906

 

[troslim]

This may help: Repair Corrupt Windows Image - Error 0x800f0906

Did like the post told me, still have the same error

 

[Superfly]

Try mounting your Windows disc/iso file and run this:

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

X: being the directory of the windows disc/iso files.
NB: the spaces...

 

[troslim]

Try mounting your Windows disc/iso file and run this:

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

X: being the directory of the windows disc/iso files.
NB: the spaces...

Does the iso have to actually be mounted with Daemon Tools or something (and use the path F: or whatever drive it'll be) or can I just use the directory the iso is located at (Desktop for example)?

 

[Superfly]

Just open the iso with windows explorer and note the drive letter.

 

[troslim]

Just open the iso with windows explorer and note the drive letter.

Tried that, but it's not showing up as a virtual drive, it just gives me the loading circle next to my cursor.

 

[JohnBurns]

I had same issue and found it was a specific group of Windows Updates which corrupted my System files. DISM and SFC would not work properly restored my system to a point before those particular Updates. Then I just hid those updates - all were "Optional" See thread

http://www.eightforums.com/windows-...-getting-nearly-30-patches-later-today-5.html
(Post #48)

These "Optional" Updates are not always applicable to a specific pc - as I found out the hard way.

 

[LittleJay]

Try mounting your Windows disc/iso file and run this:

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

X: being the directory of the windows disc/iso files.
NB: the spaces...

Just curious, but would this command work if I mounted a W 8.1 system image and substituted the assigned drive letter in place of "X"?

 

[gator2013]

I think it has been well established that it was Update KB3022345 that caused problems with SFC and crashed the DISM tools.

I originally installed KB3022345 when it was an optional update and it caused SFC/DISM problems on both my PC's. It crashed the DISM repair on both. When removed all was well again. A patched version was put out as a recommended update days later which I installed but still caused a file corruption but nothing the DISM tools couldn't fix. If you are still having trouble with SFC file corruptions I would recommend uninstalling KB3022345, for now at least.

 

[Autobahn]

I think it has been well established that it was Update KB3022345 that caused problems with SFC and crashed the DISM tools.

I originally installed KB3022345 when it was an optional update and it caused SFC/DISM problems on both my PC's. It crashed the DISM repair on both. When removed all was well again. A patched version was put out as a recommended update days later which I installed but still caused a file corruption but nothing the DISM tools couldn't fix. If you are still having trouble with SFC file corruptions I would recommend uninstalling KB3022345, for now at least.

Thanks for this.
I have been getting an error with sfc /scannow and uninstalling KB3022345 did the trick

 

[gator2013]

Thanks for this.
I have been getting an error with sfc /scannow and uninstalling KB3022345 did the trick

Currently KB3022345 is uninstalled on both my PC's. I have tried reinstalling on both systems and every time it results in some SFC file corruptions. DISM tools fixes it every time and sometimes I will get a clean SFC scan and sometimes not. With it uninstalled the SFC scan comes back clean every time so KB3022345 is on the back burner for at least several days just to confirm my findings.

Interesting though, I first installed this update in a batch of optional updates around 4/21. After I uninstalled it, it came back as an important update and after uninstalling it again it has reappeared as an optional update again. Which is it MS?
Optional, Recommended, Important????

This behavior is happening on 2 totally different PC's