But this problem with install.esd not working (versus install.wim working) was identified some time ago. Example - ESD to ISO - Create Bootable ISO from Windows 10 ESD File and I experienced the same problem in August '15, having quickly resolved it by switching to install.wim as the source, as reported by other forum members prior to that.
Are you saying that problem has been resolved?
Sorry Wordman,
Have to disagree with you..
the Install.esd is supported in the newest version of windows 10
Once again I refer to "Image-Health Repair Corrupt files" in my sig below..
runs source:esd
converts esd to wim then runs source:wim
converts esd to wim and then mounts the wim
So, three Options for Install.esd files..
Use of the media creation Tool ISO has been supported for a while now..
Don't understand where this disagreement is you speak of..... I'm well aware install.esd is supported in WIn 10.
I spoke of my experience of DISM /source option having failed when properly specified using install.esd but having succeeded once install.wim was used - many others have reported the same and had it resolved the same.
Then I asked a question as to whether this failure of install.esd to work in command line DISM /source spec has been resolved recently, begging a yes or no response.
The intended context was strictly (elevated) command line usage of DISM, not any specific tutorial or developed tool to automate the process.
I ended up combining the answers by @topgundcp and @davidhk. I downloaded the ISO from TechBench, mounted it, copied the install.wim file to the desktop, then copied and pasted the commands shown into an Admin Command Prompt and they worked. (Since I had a WIM file, not an ESD, I had to edit the DISM command accordingly.)
Thank you so much for your help, guys. I still have no idea what was going wrong. The obvious answer is that it was my typing, but I honestly struggle to see it, 'cos after five hours I was checking each character I entered with a magnifying glass.
Now I just have to solve the problem that got me started on all of this: the fact that sfc /scannow is reporting corrupted files it can't fix. I hoped DISM would cure this for me, but it hasn't.
Thanks again.
Forgive my ignorance - are you asking me to post more information here?
PS - Update: running sfc /scannow twice did fix the problem. I did read somewhere that sometimes you have to run this three times in a row. I won't pretend to understand why.
So, my machine is finally back to good health. Thank you all for your help.
- Patrick
My computer has corrupt source files which neither Scannow nor Dism commands are able to rectify.
Have mounted the Install,WIm ISO from TechNet and followed your above instructions without success.....see att
Also have tried Topgundcp method again no luck.
This is on an M$ Surface Pro 4....is it perhaps because "C" Drive is Bitlocker Encrypted,?
If you have the Tech Bench ISO file downloaded, then right click at it > click Mount > leave it there
Then open the elevated command prompt and copy and paste this................
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess
Note : H is the drive where the iso is mounted. Change it if your driver letter is different.
When it is completed, you should get the report that the operation is successful.
Now run the sfc /scannow again. It should be ok this time.
Quote
