Windows 10: 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[/quote]
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...

:)

 

W10 Install: What Needs Your Attention, White Box

I'm using Windows 8.1, upgrading to 10.

I get a similar error when I click the "upgrade" button:

 

How to enable bitlocker for every drive

See it. I only can for C: drive. But I have total 6 drives. I want this feature for every drive.

 

No idea how to fix the error, but I did a little digging and actually found an entry online that supposedly gives possible causes for the error

error code 6701 Coopoint

Hopefully that may give you a starting point *Smile

 

Thanks Barman...

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

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:

*Smile *Wink

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...

 

Same as mine. . . *Huh

 

Hi,

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

 

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

 

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... *Wink

 

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?

 

I reckon it fails because there is nothing to clean up.

 

While DISM++ did not directly resolve the issue with MS DISM, but one of the feature in DISM++ did.

The feature in question is the "Control Panel\Update" that has found KB4090007 as missing update:





I don't know why Windows update did not install this patch; maybe because generally the update disabled on the system and enabled after the dust settled with the next month update. Either way, DISM++ installed and after rebooting the system, the MS DISM completed without error:





Thanks Callender for your tip for resolving this issue...

 

KB4090007 is not being pushed out via Windows Update. It must be installed manually. That's why it didn't handle it automatically. See this TenForums thread for more info: KB4090007 Intel microcode Cumulative Update for Windows 10 v1709 - Windows 10 Forums.
HTH,
--Ed--

 

I did glance at the link for KB4090007 when it had been released. In a nutshell, this is an Intel microcode update for the Skylake to Coffee Lake CPUs for Spectre. The system in question has Ivy Bridge CPU that was not listed in the KB and patch was not installed. On the other hand, the Ivy Bridge CPU is evidently 6th generation CPU:





The patch installed on 03.18.18, but does not protect against the intended Spectre vulnerability:





But it did fix the DISM error for the Ivy Bridge system. In addition, this patch also fixed the very same DISM error on a Coffee Lake system. Why and how, I don't question, just glad it did...