DISM Error: 6701...

The system is Windows 10 Pro, 64-bits v.1709 (OS Build 16299.309). I've attempted to cleanup the image with DISM, since the WinSxS folder is close to 8GBs. Issued the command below as admin:

Code:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

This resulted in the following error:



Doing the same in Power Shell results in the same error. The "sfc /scannow" comes up clean.

I am not certain, if the latest update responsible for this or not, but seem to recall that last month the same command had ran with no issues.

Anyone has an idea how to fix this error?

TIA...

Thanks Barman...

That link probably refers to the same error as stated in my CBS log:

2018-03-17 11:42:56, Error DISM DISM Package Manager: PID=4328 TID=5944 Failed processing package changes - CDISMPackageManager::StartComponentCleanupEx(hr:0x80071a2d)
2018-03-17 11:42:56, Error DISM DISM Package Manager: PID=4328 TID=5944 Failed to start component cleanup. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071a2d)
2018-03-17 11:42:56, Error DISM DISM Package Manager: PID=4328 TID=5944 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071a2d)
2018-03-17 11:42:56, Info DISM DISM Package Manager: PID=4328 TID=5944 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2018-03-17 11:42:56, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80071A2D

The recommended solutions are really generic and does not give me much to start with. By no means that the system could not have some malware, certainly it could even if it is doubtful. Sunday is my offline scan of the system that should answer that question...

In the meantime, checked the image health:



Well, there seems to be no correction, so ran the cleanup:



Wow, I've know for awhile that my system is fast, but blazing fast? :)

It pretty much cuts out after 20% and gives me the green light. I really don't know what to think of this...

The system left unattended for for couple of hours, before the above commands ran. During this time the scheduler did run a maintenance of the system a couple of times. It's evident in the dism.log and the errors no longer show up. Maybe the the maintenance script fixed it?

The other change to this system that might cause issues with the DISM is Macrium Reflect. More accurately, having the "Recovery Boot Menu Option" enabled, that changed the boot option. This option has its own wim startup image, that can be selected at the time Windows starting. The Reflect wim is pretty much the same as booting to a Reflect created bootable USB drive. The intent of the option to provide recovery environment to restore Windows boot record, restore and/or backup images.

Based on the log entry in the dism.log file, The last time DISM ran successfully was on "2018-03-07 19:05:26". And yes, before the March update applied, but after Reflect option had been added....

I really don't know what to do with this...

Cr00zng said:

Wow, I've know for awhile that my system is fast, but blazing fast? :)

Same as mine. . .

Hi,

Try a USB device (Including updates) repair install/ upgrade, as it fixed the issues I had with DSM.

KCR said:

Same as mine. . .

I am not certain, if that's a good thing, or not... Do you have DCOM errors in your event viewer like this on?

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user GAPBOY"Standard UID removed" SID (S-1-5-21-3996346522-4209487089-3337043271-xxxx) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Lottiemansion said:

Hi,

Try a USB device (Including updates) repair install/ upgrade, as it fixed the issues I had with DSM.

I'll probably end up doing that, but I'm hesitant to go on that route at this moment; the repair install/upgrade is a hit or miss in my experience.

So far the following steps were taken.

Removed Macrium Reflect "Recovery Boot Menu Option", that did not resolve the issue with DISM.
Uninstalled KB4090914, installed on 3/14 and that hosed the system. After reboot, the system could not get to the login window, just kept spinning its wheel. After about 30 minutes, just hit the reset and system did the same upon booting. Booted to Reflect USB recovery drive and restored the drive from backup image. Having a daily image backup comes handy at times...

Callender said:

In that case consider using DISM++ to clean up WINSXS.

Well, the DISM++ scanned the system and stated:



If that the case, why does the MS DISM fail?