locked
DISM cleanup image results in error 6824 RRS feed

  • Question

  • I noticed c:\Windows\SoftwareDistribution folder is taking a lot of space.

    I run dism.exe /online /Cleanup-Image /StartComponentCleanup but the task results with error 6824:

    Error: 6824
    The operation cannot be performed because another transaction is depending on the fact that this property will not change.

    I found this errors in dism.log:

    2019-01-30 14:23:39, Error     DISM   DISM Package Manager: PID=14284 TID=8850 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80071aa8)
    2019-01-30 14:23:39, Error     DISM   DISM Package Manager: PID=14284 TID=8850 Failed processing package changes - CDISMPackageManager::StartComponentCleanupEx(hr:0x80071aa8)
    2019-01-30 14:23:39, Error     DISM   DISM Package Manager: PID=14284 TID=8850 Failed to start component cleanup. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071aa8)
    2019-01-30 14:23:39, Error     DISM   DISM Package Manager: PID=14284 TID=8850 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071aa8)
    2019-01-30 14:23:39, Error     DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80071AA8

    and this error in CBS.log:

    2019-01-30 14:23:39, Error CBS Session: 30718140_2841436248 failed to perform Synchronous Cleanup operation [HRESULT = 0x80071aa8 - ERROR_CANT_BREAK_TRANSACTIONAL_DEPENDENCY]


    I also noticed that the server tried to install 2018-06 CU many times today which doesn't make sense since the 2019-01 CU was successfully installed last week.


    Please advise how to troubleshoot this.

    Wednesday, January 30, 2019 1:41 PM

All replies

  • Hi,

     

    First, we need to understand the following instructions for using /Cleanup-Image /StartComponentCleanup:

    • /StartComponentCleanup can be used with Windows 10, Windows 8.x, and Windows PE images above 4.0.
       

    Based on this description, I think the DISM tool does not apply to clean up the “SoftwareDistribution” folder.
     

    If it is just the size, then if you use Disk Cleanup Tool and opt to Clean up System Files on your System Drive, and then Windows Update components & Delivery Optimization files, you will find that the size of this folder will get substantially reduced.
     

    It is usually safe to delete the contents of the Software Distribution folder. Even if you delete files, they will be downloaded automatically. The following methods are used to delete:
     

    1. Press Windows + R and enter CMD in the Run.
       
    2. Type the following commands in CMD:
      > net stop wuauserv
      > net stop bits
      This will stop the Windows Update Service and the Background Intelligent Transfer Service.
       
    3. Now browse to the %WinDir%\SoftwareDistribution folder and delete all the files and folders inside.
       
    4. After you have emptied this folder, you may restart your computer or you may type the following commands in CMD: 
      > net start wuauserv
      > net start bits
       
    5. Now that folder has been flushed, it will now get populated afresh.
       

    For the DISM tool, this article has a detailed explanation:
    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options#cleanup-image
     

    Hope the above can help you.
     

    Regards,
    Yic Lv

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, January 31, 2019 7:24 AM
  • The solution (workaround) was strange. 2019-01 and 2018-10 re-installed by themselves. Then I restarted server and after that I was able to run DISM and do the cleanup...
    Monday, February 4, 2019 6:43 AM