Windows 10: DISM unable to locate Install.wim file

Ah, the version of my machine is 10586. The DVD I was using as drive letter T: is 10240.

I don't know what the version of the installable USB I made today is because it does not have a WIM file; it just has an ESD file.

At least that explains why my DVD is not working. That now leaves me wondering how to (a) find the version of an ESD file, and (b) use an ESD file to repair my corrupted files.

- Patrick

 

Go to Tech Bench and download the iso file > save it to a folder and name it with version # for future reference.
http://www.microsoft.com/en-us/softw...load/techbench

That's your 10586 version.

After downloading, Right click at the iso > click Mount > leave it there.
Then open your elevated command prompt and enter your dism command line.
You know the drill from here on.

 

I made a new ISO, mounted it as H and tried DISM again. The version of the image is now reported correctly as 10586, which matches my machine, but I still get the file-not-found error. Note that the ISO contains only an ESD file, not a WIM file.

Oh, dear! Where do I go from here?

 

I asked you to download the iso file from Tech Bench which will provide the Install.wim instead of install.esd.

Did you do it ?

 

Nothing wrong with using install.esd

@EasyGoingPat
FYI, install.esd or install.wim both result the extraction of the component store files to temp folder (%USERPROFILE%\Appdata\local\temp) then use them to repair.

• Copy install.esd to your Desktop
• From Admin command, run: Dism /Online /Cleanup-Image /CheckHealth
• then run: DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:%USERPROFILE%\install.esd:1 /LimitAccess

For Step 2 & 3. Just copy and paste the command to make sure the syntax is correct. See screen shot:
NOTE: Step 2 in the screen shot will be different from yours since I have no corruption.

 

I am sorry to disagree.
Each time someone got the " sources file not found " message was because the user was using an iso which contained Install.esd.
Each time I told the user to download from Tech Bench and use the iso containing the install.wim , it always turned out successful.
This method never fails.

 

What can I tell you ? I posted the result above using install.esd.
The problem is if you don't use the correct syntax on the DISM command then of course it will not be found.

Using 7-zip to see the contents of both install.wim and install.esd. They are both exactly the same, the only difference is the compression method for INSTALL.ESD is smaller than INSTALL.WIM

 

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.

 

well that us just say it appears to be resolved with Dism version 10.0.10586

 

OK, thanks.

 

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.

 

Image-Health Option 1 then Option 0
Post details.txt

 

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