Error when running DISM /Online /Cleanup-Image /RestoreHealth - error 0x800f0906

Yea. The problem is when Microsoft hits you with something like 20 Optional Updates all at once, and you really don't have the where-withal to actually look into every single one. That's what happened to me last week, I actually got about 20 Optional Updates! After just recently installing another 20 Recommended or Important Updates! And now, I just got another 9 Optional Updates sent to me! Unbelievable. I am not even going to obsess about how bat sh*t crazy that is. I don't get it. But anyway, you want to hear a VERY possible solution to this problem? Because, I was getting the same exact DISM error message, and couldn't even get System Restore to work. And of course, then I started to now do some research online as to why System Restore may not be working, and I once again looked into something that I had come across before: The "VOLUME SHADOW COPY" in Windows "SERVICES". And believe it or not, it very well may have fixed the DISM problem. At least for now, anyway. It was showing a "Stopped" Status, and I simply turned it on, and then tried the DISM TOOL again, and it completed successfully! Believe it or not. Just press the Windows + R Keys and type: services.msc in the dialog box and look for VOLUME SHADOW COPY in the SERVICES window that comes up, and double-click it. Then click on the "Start" button, then "Apply" and "OK", and make sure it is set to "Automatic". (Note: Make sure the "MICROSOFT SHADOW COPY PROVIDER" is also turned "On" in the same manner. And I learned, that one should check on these services about once a week, and set to Automatic, because certain programs that you install or uninstall may actually turn them off). Then try the DISM TOOL again. Go ahead. If you're having the very same issue mentioned here, as I was. Try it. It very well may have been the trick that worked for me. And not one Microsoft engineer here even mentioned it, I bet. Right? There ya' go...

Just to add my own comments to this thread since I experienced the 0x800f0906 error myself a couple of days ago when DISM failed to resolve the issue.

In my particular case, the machine was running perfectly until I installed a number of Optional updates which had appeared the day before. These were as follows:

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

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

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

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

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

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

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

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

I didn't install KB3029603 since I have an Intel processor and neither did I install KB3045634, KB3055999 and KB3029432. But I did install the others even though I wasn't experiencing the issues raised in the appropriate articles.

A reboot was required which went according to plan, but later the same day, the machine wouldn't shutdown anymore and had to be manually powered off. It was after that that I decided to run SFC which couldn't fix the errors followed by DISM which has always worked in the past, but failed this time around.

I tried running the suggestion on the WindowsClub site which is this one: http://www.thewindowsclub.com/repair-corrupt-windows-image-error-0x800f0906  but that failed to resolve the issue as well.

Since the only installations that had been performed that day were the optional updates, I decided to run System Restore to a time prior to installing them. That fixed the problem I'm glad to say.

The lesson here I think is not to install everything presented as an optional update even though one of them may well prevent a problem occurring at some time in the future.

Also, running System Restore has gotten me out of trouble on more than one occasion and it's well worth a try regardless of the issue.

Hi David,

I totally agree with Phil that DISM is a repair tool. SFC scan and DISM all check for the system files are they working fine or not. IF SFC scan is not finding any violations then for now you may leave it but in future if you face any such issue or different please try to run the scan again and check the status.

Basically the error message which you are getting deals with .Net Framework but as you are not facing any issue with it so I would suggest you to ignore it for now. 

Do keep us updated and feel free to get in touch with us if you face in issue with Windows, we will be happy to assist you.

Regards.

Isn't this "sticking your head in the sand"?  Not very reassuring at all.

Larry,

Experienced everything you said.

Am now looking for a MAC.

Good Luck to all with Windows.

Enjoy those reinstalls...

If you spent as much time learning new software as we did attempting to fix Windows 8, imagine how our resumes would look;

(AutoCAD, Inventor, Oracle, Matlab --> just to begin).