Though I didn't mention it in this post, I did indeed try some variations, all of which failed identically.
Originally Posted by KYHI
What I was planning to do next was to completely ignore the hints to DISM about the type of file (the "esd:" and ":1" substrings) and make sure I actually was in the directory with the "sources" subdirectory - that way any tacking on of my "current" directory would be correct AND there wouldn't be any strangeness with "esd:" getting injected into the pathname. Something like this (where the ISO file is mounted as "g:"):
I do not remember where I read it - probably at least a couple different locations maybe even including something on eightforums - but the gist of what I read was that "install.esd" is equal to OR maybe even the replacement for "install.wim" and could be used with the DISM "/Source:" argument.
dism /Online /Cleanup-Image /RestoreHealth /Source:sources\install.esd /limitaccess
Certainly using the "esd" strings caused no complaint at all from DISM so I assume it accepted it just fine, though maybe it simply passed along the string to some other library/application that totally choked on it. That is the gist of the questions behind this thread - how is this error happening to ME when many others have apparently used this exact same argument format and it's worked fine?
Anyway, I'll probably be trying that out "soon" and will post a followup whether success or failure.
I just tried this with the displayed results - DISM accepted an ".esd" file as if it were a ".wim" file:
G:\sources>dism /Get-WimInfo /WimFile:install.esd /index:1
Deployment Image Servicing and Management tool
Details for image : install.esd
Index : 1
Name : Windows 8.1 Pro
Description : Windows 8.1 Pro
Size : 13,185,962,705 bytes
WIM Bootable : No
Architecture : x64
Hal : acpiapic
Version : 6.3.9600
ServicePack Build : 17415
ServicePack Level : 0
Edition : Professional
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 18805
Files : 104794
Created : 11/21/2014 - 1:07:26 PM
Modified : 8/28/2015 - 8:34:32 PM
The operation completed successfully.