Windows 10: ISO flavors and DISM

The Windows MCT creates an ISO with an Install.esd file. The TechBench ISO download has an Install.wim file.

I've seen some posts that say the Install.esd file cannot be used with DISM.
I've seen some posts that show a complicated method of using Install.esd with DISM.
I've seen one post that shows DISM with a "SOURCE:ESD: ..." parm (that certainly implies esd files work).

I tried the latter to repair an error that SFC could not fix and got a "The source files could not be found" error. (I don't remember that actual text of the error message, but the logged message was The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
So,

• Should I download the TechBench version just so I get the .wim file?
• If so, should I burn a disk from that rather than use the mct version (assuming I ever really need the ISO)?

Also, I've seen several comments on the web about putting the Install.wim or Install.esd on the desktop and pointing DISM at it. Why? I've got the ISO files on both a DVD and on an external drive. I may soon have a set of ISO files with the .wim file on an external drive. Is this suggestion just a performance consideration, or does DISM have an issue with accessing source on external drives?

:)

 

Licensing for Windows in a customer service scenario

For Windows 10 you can create ISOs for the different flavors of 10 and install it, then have the customer login with their LIVE account (if it was an upgrade) or enter in their License Key.

Download Windows 10

I'm not sure about getting ISOs of prior versions.

 

E60 vs. linux - Export addressbook to linux

Support for Linux is one thing, but the problem is there are lots of flavor of Linux(e.g. Suse, Limpus, RedHat, Slackware, Mandrake,Ubuntu etc) one have to recompiled it for each flavor, with the libs for the particular flavor.

Maybe in the near future, there will come up a ubiquitus flavor that Nokia will give support. No doubt about it, its a very stable system, no blue screen from time to time.

Message Edited by android on 21-Jan-2008 12:55 PM

 

I don't know that much about DISM but I had the same problem with SFC not repairing some files. I followed a guide using DISM and they had me copy the wim to the root of C drive. When I tried the command and the wim was on the desktop it didn't work. I got the same message you did.

I dont know if DISM will work with a esd file but you can convert them to wim files. Use this tool from kyhi

Windows 10 Recovery Tools - Bootable Rescue Disk - Page 2 - Windows 10 Forums

 

Pokeefee.
You need the TechBench WIM version....download and right click to mount...check drive letter mounted on Run the DISM command in Command Prompt (Admin):
DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:E:\Sources\Install.wim:1 /LimitAccess

WIM:E above should be changed if your mount drive is different

 

Any explanation why source:ESD:E was accepted but didn't seem to work?

 

It did not work for me either.
Did you check what drive it was mounted on?

 

Well, at this point I can't confirm I actually had the correct drive, but I had tried it twice - once pointing to the DVD; once pointing to the .esd file in the downloaded files. I would have expected to get it right one of those times. (But I'm a firm believer in Murphy, so who knows.)

Anyway, I downloaded the Tech Bench version, pointed to it, and DISM ran successfully. Then SFC found and corrected the corrupted files.
Does that imply I should burn a new ISO disk using the Tech Bench version of the ISO files? Is the MCT version bad?

Not directly related to my initial question, but ... What does DISM do (in this case)? It obviously didn't correct the corrupted files that SFC had originally found or the 2nd execution of SFC wouldn't have been needed. Does DISM just fix the files that SFC uses to fix files?

 

SFC and Dism in this case was confirmation source files had been restored.... after Wim.install loaded the missing source files.
Don't forget to mark up as solved.

 

Tech Bench versions expire after 24 hours so a repair today may not work tomorrow. Just recreate a new iso and mount to main drive for repair. The iso unmounts when you restart your computer anyway. Either esd or wim versions of correction source files work to correct the problem (sfc /scannow integrity issues) unless the problem is to many damaged files. In that case, even the dism correction methods will not fix the damaged files. Then, wait for the next windows cumulative update to correct the damaged files. However, you may still have files that are unable to pass the integrity issue damaged files but unable to repair. At this point run the dism repair command as instructed. I do not include the "limit access" as part of the command line instructions as I have been more successful without that.

The above situation as described by me has happened 3 or 4 times since the original july 2015 roll out of windows 10. The integrity issues found and unable to repair has lasted anywhere from several weeks to several months. Just recently this issue of bad files found but unable to correct was corrected by me using the dism repair procedure as explained in this forum. I think the dism run was after the latest update of win 10.

Just to be sure everything is where it is supposed to be, I ran the sfc thingy just now and the results are "Windows Resource Protection did not find any integrity violations". Just what you want.

 

>>Tech Bench versions expire after 24 hours so a repair today may not work tomorrow.
What do you mean by that. Does it mean that every time I want to use DISM I have to download a new version of ISO from the Tech Bench?

 

@lopedoggie

I'm not sure if you may have meant something else, but that's incorrect. A Tech Bench ISO is no different than retail. As long as you have a valid product key to activate it, it will stay activated.

https://www.tenforums.com/tutorials/9...-download.html

 

One thing I HAVE noticed in last month or two is that the TechBench downloads now require validation and then you are given a download link, and that link is what expires in 24 hours. MS has their own timing (generating a lot of TF discussion*Nerd) on how often the TechBench ISO build is updated.

 

Thank you for clarifying Word Man. *Smile

 

for what it is worth, i have had techbench work with the install.wim and i have had it not work. this via dism clean up restore cannot find source files etc. microsoft writes code, i do not. i guess every edition of there iso updates are all the same. what do i know. go at your own chosen speed.