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

[AdamW]

Hello.
I wonder if you can help me.
I keep getting error 0x800f0906 when running DISM /Online /Cleanup-Image /RestoreHealth.

DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature.

For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


*********************
relevant bits from it seem to be:


Checking System Update Readiness.

(p) CSI Payload Corrupt amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wuaext.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wushareduxresources.dll
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x800f0906
Last Successful Step: Entire operation completes.
Total Detected Corruption: 2
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 2
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True


In adition, my windows 8 will not carry out a scheduled maintenance session.

Is this something I can repair, do you think? Any help would be appreciated. The setup event logs mentions 2 errors, so presumably this is the issue.

 

[Go The Power]

Hello AdamW

SFC /SCANNOW

1. Right click on the
   
   button
2. Click on Command prompt (Admin) => Press Yes on the prompt
3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
4. Please wait for this to Finish before continuing with rest of the steps.

Export CBS folder

1. Right click on the
   
   button
2. Click on File Explorer
3. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
4. Find and double click on the Logs folder.
5. Right-click on the CBS folder, and select Copy.
6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
7. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
9. Attach this to your next post please.

Please Note:: if the file is too big to upload to you next please post please upload via Dropbox or ge.tt

 

[AdamW]

Hello again.

Attached please find the CBS file, as you requested.
I look forward to your further instructions.

Regards,
Adam

 

[Go The Power]

Hi Adam,

Was that everything inside the CBS folder? Where there any .CAB files? If there is can you send them all to me please?

 

[AdamW]

I believe that was everything there was in that folder, but I am not certain.
Anyway, just to be on the safe side, I ran the SFC/SCANNOW once again and now have a new CABS log for you to have a look at. The scan ended with the following message:
"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log windir\Logs\CBS\CBS.log." You fill find the details in the attached logs."

Futhermore, I ran DISM /Online /Cleanup-Image /RestoreHealth, the deatails of which I also eclose herewith. This resulted in the following message:

"DISM /Online /Cleanup-Image /RestoreHealth


Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384

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

Error: 0x800f0906

The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source. "



As far as I can gather from the DISM.log, the most important details are as follows:

Checking System Update Readiness.

(p) CSI Payload Corrupt amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wuaext.dll
(p) CSI Payload Corrupt amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wushareduxresources.dll

Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 2
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 2
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

On the basis of the foregoing, I assume that missing or corrupted are the following two files:

amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wuaext.dll
amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wushareduxresources.dll

If am correct, could please supply me with appropriate instructions on how to repair this error?

Regards,
Adam

 

[Go The Power]

Hi Adam,

That CBS log looks better. The first one only had 32 lines and finished in 11 Seconds.

You are correct about the files that need replacing, but as you can see below SFC gives a lot better idea of the files properties:

2014-07-15 12:54:42, Info                  CSI    000007d4 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wuaext.dll do not match actual file [l:20{10}]"wuaext.dll" :
  Found: {l:32 b:DU09ZAjNgIjhbX3NpaNHSUGoy9ANeAqrXb66C4EPD4E=} Expected: {l:32 b:tSbN42ES0XvP+VsYZjlwdYol8cwIn4sqpJL/bnKbKBU=}
2014-07-15 12:54:42, Info                  CSI    000007d5 [SR] Cannot repair member file [l:20{10}]"wuaext.dll" of Microsoft-Windows-WindowsUpdateClient-UI, Version = 7.8.9200.16927, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-15 12:54:42, Info                  CSI    000007d6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wushareduxresources.dll do not match actual file [l:46{23}]"wushareduxresources.dll" :
  Found: {l:32 b:LeBH5VsngXM1kjr/a1iCBzLjpUCSeuFjNhPSiHk9bGU=} Expected: {l:32 b:n9fuTtNdFCYvRSsecvj+ZsT9vUj3tJ4CsVu+Tr1NR5Q=}
2014-07-15 12:54:42, Info                  CSI    000007d7 [SR] Cannot repair member file [l:46{23}]"wushareduxresources.dll" of Microsoft-Windows-WindowsUpdateClient-UI, Version = 7.8.9200.16927, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-07-15 12:54:42, Info                  CSI    000007d8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wuaext.dll do not match actual file [l:20{10}]"wuaext.dll" :

I have located both the files that need replacing

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Run another Scan with DISM and SFC /SCANNOW and upload the CBS folder.

Thanks

 

[AdamW]

Hello Go The Power,

Thank you ever so much for your promt reply.
However, I decided on a different (and in my view, more efficient) approach to resolve the issue. Namely, I chose to upgrade my Windows 8.0 to Windows 8.1. That way I got a completely new system installed on my laptop and the update problem vanished. I am now able to take advantage of the Windows 8.1. update feature to install new updates and the whole operation runs smoothly. Also, running the SCF/SCANNOW does not show any system integrity violatons. The only drawback being the fact that it tool me several hours to do so.
Once again, let me thank you for your kind assistance and I hope I have not inconvenienced you too much.

Best wishes,
Adam

 

[Go The Power]

Hi Adam,

What ever works, as long as the issue is resolved in the end that's what matters :)