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

For me SFCFIX it does not fix corrupion. More worse it is causing dism corruption as well. The payload files are somehow not present/detected by dism on update servers and dism.. /restorehealth crashes with "error 0x800f0906 The source files can't be downloaded". Everything is working correctly because dism repaired sucessfully indused by me corruption in gpedit files. and I have latest KB3068708 installed which should correct the files for telemetry client but it does not. you can go and read KB3022345, KB3068708 articles on those two hotfixes. M$ knows about those problems, and I quote after KB "There is no impact or actual corruption on a device running this update, and a later service update will resolve this issue." Here excerpt from my dism log for cuirous:

[code]

2015-06-04 15:26:39, Info                  DISM   DISM Package Manager: PID=6688 TID=8100 <----- Starting corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize

2015-06-04 15:26:39, Info                  DISM   DISM Package Manager: PID=6688 TID=8100  - CDISMPackageManager::Internal_Finalize

2015-06-04 15:26:39, Info                  DISM   DISM Package Manager: PID=6688 TID=8100

=================================

Checking System Update Readiness.

(p)    CSI Payload Corrupt    (Fixed)    x86_microsoft-windows-fde_31bf3856ad364e35_6.3.9600.17415_none_3cf85ad9770b339f\fde.dll

(p)    CSI Payload Corrupt    (Fixed)    x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.3.9600.17415_none_74a1f1a06c1e56a5\fdeploy.dll

(p)    CSI Payload Corrupt    (Fixed)    x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.3.9600.17415_none_cc3c2bedaa66d1dc\gptext.dll

(p)    CSI Payload Corrupt            amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\utc.app.json

Repair failed: Missing replacement payload.

(p)    CSI Payload Corrupt            amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\telemetry.ASM-WindowsDefault.json

Repair failed: Missing replacement payload.

(p)    CSI Payload Corrupt            amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json

Repair failed: Missing replacement payload.

(p)    CSI Payload Corrupt            amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.ASM-WindowsDefault.json

Repair failed: Missing replacement payload.

(p)    CSI Payload Corrupt    (Fixed)    x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.3.9600.17415_none_631e8bf880476a4b\gpedit.dll

Summary:

Operation: Detect and Repair

Operation result: 0x0

Last Successful Step: Entire operation completes.

Total Detected Corruption:    8

    CBS Manifest Corruption:    0

    CBS Metadata Corruption:    0

    CSI Manifest Corruption:    0

    CSI Metadata Corruption:    0

    CSI Payload Corruption:    8

Total Repaired Corruption:    4

    CBS Manifest Repaired:    0

    CSI Manifest Repaired:    0

    CSI Payload Repaired:    4

    CSI Store Metadata refreshed:    True

Total Operation Time: 911 seconds.

 - CDISMPackageManager::Internal_Finalize

2015-06-04 15:26:39, Info                  DISM   DISM Package Manager: PID=6688 TID=8100  - CDISMPackageManager::Internal_Finalize

2015-06-04 15:26:39, Info                  DISM   DISM Package Manager: PID=6688 TID=8100 <----- Ending corruption detect/repair info ----->

[/code]

A Clean Boot is just a Diagnostic Tool, it is not a "fix".  By using it you are only trying to locate a possible cause as to the problem.  Perhaps it is something already running on your machine, a Clean Boot may eliminate that possibility.

I'm a little confused, how does a so called "Clean Boot" resolve the problem being discussed?

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...

I don't think setting VSS to 'Automatic / On' is such a good idea somehow. The default setting is 'Manual / Off'. If the user creates a manual system restore point, or makes a backup, then it will (or should) start automatically.

The OS will periodically create its own system restore points which will change the setting to 'On' temporarily, but it'll be turned off again afterwards.

Also, since the maximum number of shadow copies which can be created is 64, at some point in time with an 'Automatic / On' setting that figure is going to be reached after which no more will be created. That implies that the user is going to be left with old data to restore to which isn't ideal.

It might be worth your while trying a clean boot if you find yourself in that situation again: https://support.microsoft.com/en-us/kb/929135