Share via

Dism Online Cleanup-Image RestoreHealth fails

Anonymous
2019-01-11T18:11:51+00:00

I tried Dism Online Cleanup-Image RestoreHealth after Windows update locked up the boot

DISM failed. No operation was performed: dism.log errors

2019-01-11 18:44:25, Info                  DISM   DISM Package Manager: PID=15128 TID=15148  Error in operation: (null) (CBS HRESULT=0x80072ee6) - CCbsConUIHandler::Error

2019-01-11 18:44:25, Error                 DISM   DISM Package Manager: PID=15128 TID=15144 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80072ee6)

2019-01-11 18:44:25, Error                 DISM   DISM Package Manager: PID=15128 TID=15144 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80072ee6)

2019-01-11 18:44:25, Error                 DISM   DISM Package Manager: PID=15128 TID=15144 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80072ee6)

2019-01-11 18:44:25, Error                 DISM   DISM Package Manager: PID=15128 TID=15144 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80072ee6)

2019-01-11 18:44:25, Info                  DISM   DISM Package Manager: PID=15128 TID=15144 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2019-01-11 18:44:25, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80072EE6

NB this is an Asus X750JB laptop with Microsoft Windows 10 Pro Version 10.0.17134 Build 17134, originally bought as Windows 7, upgraded to 8, 8.1 then 10.  Now with a SanDisk SDSSDA240G. As such, the boot sequence in the BIOS seems to be legacy rather than UEFI.

Any ideas how to fix this?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-01-11T18:27:11+00:00

    The boot just kept spinning for hours on end...

    Recovery Environment said it could not fix the repairs - and went back to spinning dots...

    Eventually, the only successful option was a system restore via a USB  - the system restore of the same restore point via the SSD failed. 

    However , the above information - IE the problem - occurs AFTER all this, AFTER the successful system restore.

    IE DISM worked fine previously, as did sfc /scannow.

    Now I'm scared to even restart the computer.

    [Subsequent sfc /scannow shows:

    2019-01-11 18:44:25, Warning               CBS    Current tick count: 800 lower than last tick count: 1063. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

    2019-01-11 18:44:25, Error                 CSI    0000000a@2019/1/11:17:44:25.535 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]

    2019-01-11 18:44:25, Error                 CBS    FC:   CFCAcquirerWUClient::Download(136): Result = 0x80072EE6

    2019-01-11 18:44:25, Error                 CBS    FC:   CFCAcquirerWrapper::Execute(147): Result = 0x80072EE6

    2019-01-11 18:44:25, Error                 CBS    Session: 30714324_2636989176 failed to perform store corruption detect and repair operation. [HRESULT = 0x80072ee6 - Unknown Error]

    2 people found this answer helpful.
    0 comments
  2. DaveM121 872.1K Reputation points Independent Advisor
    2019-01-11T18:15:41+00:00

    Hi John, dism will fail if that update did not complete successfully, because you will have corrupt system files . . .

    You say a Windows update locked up your boot process, please explain what you are seeing when you try to boot your PC . . .

    In the meantime, have you tried all the options in the Recovery Environment?

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt . . . etc.

    Please try each option one at a time, then see of Windows will boot . . .

    Go to Troubleshoot - Advanced Option - Revert to previous build of Windows

    If available, this is the best option . . .

    Go to Troubleshoot - Advanced Option - Startup Repair

    See if Windows startup can repair itself

    Go to Troubleshoot - Advanced Option - System Restore

    Check to see if you have a restore point you can go back to

    If you do not have a Restore Point, go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Once in Safe Mode, backup your data if you do not already have a backup

    Open Device Manager and check to make sure all your Drivers are up to date

    Reboot to see if Windows will start Normally

    If the above fails, go to Troubleshoot - Advanced Options - Reset this PC

    Choose to keep your files and apps, just your files or to keep nothing

    Then start the Reset

    0 comments