DISM Error

Question

I tried to run command:

dism /online /remove-package /packagename:Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~6.3.9600.16384

and received error: 0x800f0831

Also i run command:

Dism /Online /Cleanup-Image /RestoreHealth

and received error: 0x800f0906

OS: Windows 8.1 x64

I was bought my laptop with Windows 8 and upgrade it to Windows 8.1

DISM LOG:

http://1drv.ms/1DwNQDg

CBS LOG:

http://1drv.ms/16Ks3Ln

Answer 1

Have you included all the spaces?

Select the keyboard shortcut Win+S, type Command Prompt, right click Command Promptin the list below **** and select Run as administratorfrom the drop down menu. Type cd* and press the ENTER key. Type Dism /Online /Cleanup-Image /RestoreHealth and press the ENTER key*.** Please be patient when performing this procedure as it can appear that nothing is happening when it is. Please say what is reported when the check completes.

Take care to include the space before each / (forward slash) when typing the command.

Answer 2

I was bought my laptop with Windows 8 and upgrade it to Windows 8.1

I'm trying to see what your current cumulative level is.  It may be faster for you to tell us that.  E.g. in View Windows Update History (in an English version of Windows for me it is Win-w V W U H Enter).  Then the first line in there starts "Most recent cumulative update".  What do you see there?  For example I have  KB3000850 but I can't even tell if you have KB2919355 yet and don't know if that feature existed earlier.   FWIW I call that  W8.1.2  just as KB2919355 is also known as W8.1.1.

Let's try to match up the first error from your CBS.log with your last  RestoreHealth  attempt, corresponding to line 477 in the DISM.log

2015-02-0916:09:28,InfoDISMDISM.EXE:Executingcommandline:Dism/Online/Cleanup-Image/RestoreHealth

OMG.  Did it take this long?

2015-02-09 16:09:29, Info                  DISM   DISM Package Manager: PID=2900 TID=4632 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize

2015-02-09 16:43:37, Info                  DISM   DISM Package Manager: PID=2900 TID=5388  Error in operation: (null) (CBS HRESULT=0x800f0906) - CCbsConUIHandler::Error

Then here is the final summary at line 6518

Operation: Detect and Repair <br><br>Operation result: 0x800f0906 <br><br>Last Successful Step: Entire operation completes. <br><br>Total Detected Corruption: 53]

So apparently there was so much corruption that DISM decided it couldn't fix anything.  But IMO it is such trivial stuff that I don't understand why they make this a blocking condition.

You could try picking away at it the way that this poster did but it looks like it could be a lot of hacking required.  However, the logs look quite similar, especially with the Flash errors, so you might find that it would be feasible in the same way.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/update-kb3000850-fails-to-install/43125206-f39e-477f-b5b6-73a177abb589?page=4

HTH

Robert Aldwinckle

---

Answer 3

I was bought my laptop with Windows 8 and upgrade it to Windows 8.1

I'm trying to see what your current cumulative level is.  It may be faster for you to tell us that.  E.g. in View Windows Update History (in an English version of Windows for me it is Win-w V W U H Enter).  Then the first line in there starts "Most recent cumulative update".  What do you see there?  For example I have  KB3000850 but I can't even tell if you have KB2919355 yet and don't know if that feature existed earlier.   FWIW I call that  W8.1.2  just as KB2919355 is also known as W8.1.1.

Let's try to match up the first error from your CBS.log with your last  RestoreHealth  attempt, corresponding to line 477 in the DISM.log

2015-02-0916:09:28,InfoDISMDISM.EXE:Executingcommandline:Dism/Online/Cleanup-Image/RestoreHealth

OMG.  Did it take this long?

2015-02-09 16:09:29, Info                  DISM   DISM Package Manager: PID=2900 TID=4632 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize

2015-02-09 16:43:37, Info                  DISM   DISM Package Manager: PID=2900 TID=5388  Error in operation: (null) (CBS HRESULT=0x800f0906) - CCbsConUIHandler::Error

Then here is the final summary at line 6518

Operation: Detect and Repair <br><br>Operation result: 0x800f0906 <br><br>Last Successful Step: Entire operation completes. <br><br>Total Detected Corruption: 53]

So apparently there was so much corruption that DISM decided it couldn't fix anything.  But IMO it is such trivial stuff that I don't understand why they make this a blocking condition.

You could try picking away at it the way that this poster did but it looks like it could be a lot of hacking required.  However, the logs look quite similar, especially with the Flash errors, so you might find that it would be feasible in the same way.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/update-kb3000850-fails-to-install/43125206-f39e-477f-b5b6-73a177abb589?page=4

HTH

Robert Aldwinckle

---

List of all installed updates from Windows Update:

http://goo.gl/XaVHYm

Answer 4

Hello,

Please refer the following fix and see if that helps you:

http://www.thewindowsclub.com/repair-corrupt-windows-image-error-0x800f0906

Hope this helps, Good luck :)

Thank you for you fast answer,

I run all this command and reboot my computer, but it didn't help me :(

C:\windows\system32>Dism.exe /Online /Cleanup-Image /RestoreHealth

Cистема DISM

Версия: 6.3.9600.17031

Версия образа: 6.3.9600.17031

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

Ошибка: 0x800f0906

Не удалось скачать исходные файлы.

Укажите расположение файлов, необходимых для восстановления компонента, с помощь

ю параметра "Источник". Дополнительные сведения об указании расположения источни

ка см. на веб-странице http://go.microsoft.com/fwlink/?LinkId=243077.

Файл журнала DISM находится по адресу C:\windows\Logs\DISM\dism.log

New DISM LOG:

http://1drv.ms/1CQmuJ3

New CBS LOG:

http://1drv.ms/1CQmHMq

Answer 5

Hello,

Please refer the following fix and see if that helps you:

http://www.thewindowsclub.com/repair-corrupt-windows-image-error-0x800f0906

Hope this helps, Good luck :)