Let Windows run for a day or two before following the reset instructions.
If you get the 0x800f0906 error, try resetting Windows Update components:
Launch an elevated Command Prompt
Execute the following commands
net stop wuauserv
ren Download Download.old
net start wuauserv
net stop bits
net start bits
net stop cryptsvc
ren catroot2 catroot2old
net start cryptsvc
You can copy the lines above and paste them into the Command window
Then restart your machine and try Dism.
edit: Then restart your machine, run Windows Update (it might take a while after the reset) and then try Dism.
Last edited by Slartybart; 07 Aug 2015 at 10:51. Reason: add WU after reset, before Dism
I think the clean install solved the issue.
Give the new install a few days and then yes, please run Dism to test if it returns and run errors (0x800f0906). If it runs and reports integrity errors, that's something different - this test is just to see if Dism runs
Dism /Online /Cleanup-Image /RestoreHealth
If you do get the error, wait a few days for Win10 to 'clean itself up' before running the Windows reset commands in post# 43. When I ran the WU reset - it took a while (5-10) minutes) for Windows to 'settle down'.
- Windows update too a long time to load - not surprising.
- Two Start tiles (both PowerShell links) changed position and size - this issue also occurred in the preview releases, so it's probably still a bug that shows up less frequently. I just re-sized the tiles and put them back where they were.
- I couldn't launch anything elevated - that concerned me, but Windows cleared that up by itself - very nice! If your experience differs, try restarting the machine after giving Windows a fair chance to do any system configuration checks that it normally does (security on special files, required services started, etc)
Thanks - you're doing a great job providing feedback and acting on suggestions.
Is that possible? Sure, a Fresh install doesn't require too much checking.
The 20% does seem to be where the Dism progress sits for a while. I don't know why, but once Dism finishes those initial checks, the progress goes fairly quick.
I usually don't watch the progress so I rarely see the interim percentage complete. I launch it and it gets to 20% then I do something else - when I return to the screen, it's 100%. If it's not, then I might start digging. Most of the time it just takes time - how much? It depends on the work it has to do - 3 or 4 hours is when I get concerned enough to think there might be an issue.
Even then I resist the temptation to cancel the command - if it runs for more than 12 hours - there's probably a problem that requires a bigger hammer
Take your time adding programs back in to your system, add one and see how the program and system behaves. then add another and make sure things are running well. It takes time, but if one program does cause an issue, you know which one. Uninstall the problematic program, then keep going with other programs.
You can later investigate any programs that cause issues - usually an updated installer, updated co-requisite software, or an updated program resolves most software 'conflicts'
Brilliant work Steve and Bill.
Kudos for working with them oldage, glad to hear your problem's sorted.