Use DISM to Repair Windows 10 Image  

You can use either wim or esd image for what's the format concerned.
For more info look HERE
For ESD:
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:Full Path to install.esd file:1
or
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:Full Path to install.esd file:1 /limitaccess
For Wim:
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1
or
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess
will do the job of recognizing the format.

The trouble with esd is not the format it self, but, esd made with MediaCreationTool sometimes (it's Microsoft so read that as most of the times) is, by its content, faulty. I've tested these esd images converting them to wims, and the error persists for both formats. MSDN or retail wims are tested by microsoft for this functionality, but i believe that MediaCreationTool ones simply are not. They wait for us to do that, report and fix the problems. It's cheaper that way, and holiday last longer if they do not have to do that (Just as they sometimes leave peaces of testing software on Retail and MSDN images just to do some hidden testing on our working machines with out letting anyone know about it.)

Have a nice day.

PS convert wim from MSDN or retail to ESD and try the commands. They work all right. Take a few seconds more to complete but it actually (pays off in space/time ratio to refer to Mr. E. from the post above).

And... Albert was right... at that point of time, he did. A bit latter it had consumed it. We are using "bugs" and "glitches" as an excuse to obtain artificial profit. Nothing for something kind of a way. That's not over-unity, that's absolute absence of humanity (in the manner of: we do not know how to define humanity no more). Do not fail to see that Albert's "technology" equivalents greed, that is what "appalling" is about. The old bast*rd was a poet above all. Just ass Albert was a poet, Microsoft is actually lead by no fools.

Bree... I was merely explaining wim-esd general differences. Nothing of what I have said in my last post has a thing to do with this particular error. So I do not understand "Not quite, apparently." part.
The MediaCreationTool image (esd or converted to wim, all the same) has returned error in numerous cases, when MSDN or Retail image of the same build did not.
Not that you are wrong about Windows 10 version 1703 where all of the images fail online and none (for MediaCreationTool read none as current) does fail offline (If no other errors of course, so 100% is actually around 50% average and sfc comes in handy in most of the other 50%).
About of the content of the image... It is faulty. We did use INSTALL.wim/esd to install in the first place. And we got to the error using it (as well as with windows update). The error is there even if we do clean install with current MediaCreationTool or any other 1703 image. I've tested that. The DATABASE that DISM uses to find what should be installed is part of the image. DISM is instructed to read REGISTRY that has been written by install image it self. If working offline, DISM is instructed not to read registry and that is a workaround but not the solution to the error of 1703 build problem. It merely allows other errors to be fixed and OS to be repaired when DISM fails online on 1703 build. Uninstalling the offending package is the solution as Microsoft will finally confess.

PS /ScratchDir:C:\Scratch I like a lot (if not enough ram particularly... though... D: if available could speed things up in some cases)

That article points back to @Eagle51 's post here at Tenforums as the fix:
Creators update component store shows corruption but unable to repair - Page 3 - - Windows 10 Forums

Cheers!

At least they're only trying to be helpful. :)

Brink said:

At least they're only trying to be helpful. :)

Agreed. :)