W10 – Can’t get DISM.exe to work on online image

Topic

New Reply

I frequently used DISM.exe on running W8 and W8.1 x64bit operating systems. The command was always written as: “>dism /online /cleanup-image /restorehealth”. I never got an error message and never used “/Source” as part of the command.

With W10x64 recently using >dism /online /CheckHealth and >dism /online /ScanHealth, the results indicated “repairable corruption” in the both the image and the componentstore. But, when I ran DISM as written above in paragraph one, I got the following error message:
“Error: 0x800f081f
The source files could not be found. Use the /Source option to specify the location of the files that are required to restore the feature.”

When working with W8.1, it was my understanding that DISM.exe would use Windows Update to retrieve most current files to repair any corruption to the online image. Windows 10 seems to need additional DISM.exe arguements to find current files to repair the corrupted files.

Q. With W10, do i need to specify a /Source location for Windows Update?
Q. Do I need to specify the /Source location for an .ISO file or the 10586 USB thumbdrive I have, to repair my running online image?

My PC is running Windows 10-10586.

thanks

Reply | Quote

Replies

First you need the iso of the exact version of Windows 10 you have installed, or at least the install.wim of it. If you have the iso then mount it. In a command or powershell window open as administrator paste the following code substituting in the drive letter where install.wim is for X. Run the code, then afterwards run sfc /scannow.

Code:

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:SourcesInstall.wim:1 /LimitAccess

Reply | Quote

Is it necessary to convert install.esd in a downloaded iso to install.wim?

Reply | Quote

Is it necessary to convert install.esd in a downloaded iso to install.wim?

No, you would use the same command as above substituting in ESD for WIM, and the full path to the esd file. So, you would have this

Code:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:X:SourcesInstall.esd:1 /LimitAccess

Reply | Quote

No, you would use the same command as above substituting in ESD for WIM, and the full path to the esd file. So, you would have this

Code:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:X:SourcesInstall.esd:1 /LimitAccess

Got it. Thanks.

Reply | Quote

Is it necessary to convert install.esd in a downloaded iso to install.wim?

Apparently not, if esd and install.esd is specified:

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:SourcesInstall.esd:1 /limitaccess

Reply | Quote

But then I have to ask: Who at the moment would have an iso of build 10586, version 1511, November update with an install.wim instead of an install.esd and how did they get it?

Reply | Quote

But then I have to ask: Who at the moment would have an iso of build 10586, version 1511, November update with an install.wim instead of an install.esd and how did they get it?

Convert Windows Update esd to iso. I do it all the time. Then I restart, and do the upgrade with the setup file in the mounted iso. I can also save the iso, in case I want to do a clean install or testing in Hyper-V.

Reply | Quote

djohnson

I read you First post:
1. The iso file is build 10586 and the W10 installed operating system is 10240. I downloaded 10586 from the MS Download site yesterday, Nov. 29.2015
2. I do not know *what the “install.wim” file is or *where to find it!
{When I mount the ISO in File Explorer, the contents of the ISO look like the install files for Windows 10. The mounted ISO includes a setup.exe file)
3.Lastly, your instruction in Post 1 to run the DISM code references the “Install.wim” file again. Please see item two above.

I read your Second post:
1. Do I need to mount and copy the ISO files to the ESD folder at CESD?
2. Will moving the ISO files to the C:ESD folder make DISM.exe pull “good” files from C:ESD as substitues for the corrupted files in the existing OS?

I read your Third post.
I am completely at a loss

Reply | Quote

But then I have to ask: Who at the moment would have an iso of build 10586, version 1511, November update with an install.wim instead of an install.esd and how did they get it?

I got mine (wim file) using NTLite to convert the esd file. I’ve had no success using the esd file with the DISM tool.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

** Thanks to djohnson and BruceR for the discussion…

I *have to digest the content of the discussion above between you-all before I can question or comment further….
There is a lot there for me to get a hold of…….

I hope you both will be around to further the discussion.

Reply | Quote

** Thanks to djohnson and BruceR for the discussion…

…. I hope you both will be around to further the discussion.

……………………………………………………………………………………………………………..

12.07.15

I am a bit confused…..

After playing with my .iso as a Source of files, I decided to try my C:ESD folder instead. Judging by dates of files only, I guessed the files where 10586. I also finally found the “Install.esd” file in the ESDWindowsSources folder and did the following:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:C:ESDWindowsSourcesInstall.esd:1 /LimitAccess.
the command did not work (source files not found) so I changed the text and I ran it like this:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:C:WindowsSourcesInstall.esd:1 /LimitAccess.
the command did not work (source files not found) so I corrected the text to mirror the suggestion provided above. I ran this:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:C:SourcesInstall.esd:1 /LimitAccess
unfortunately, I got the same error message; “Source files not found”.

I think I am following directions but I obviously must be missing something ….
Can either one of you gentlemen help me out?
I would really like to get the command to work to repair corruption found by running DISM /… /Scan Health and /Check Health

thank you

Reply | Quote

……………………………………………………………………………………………………………..

12.07.15

I am a bit confused…..

A

Maybe contagious! I am confused too, just where is your source file?

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

addendum 10:25am :
looks like i was posted this reply before the website downloaded reply posts from several users. (ex – djohnson and Berton, et.al).

……………………………………………………………………………..
FYI – To WAVY
I do not know where ‘my’ source file is…?

I have used the following locations as ‘source files’. I have tried to point DISM to an .ISO file stored on C:; to an .ISO-2- DVD install disk on a DVD burner/player; and to a USB drive with a W10 setup.exe files. All the above are children of the .ISO (or the USB) I downloaded from MS using the Medial Creation Tool. Some help from the Mr.Johnson would be appreciated…

Reply | Quote

……………………………………………………………………………………………………………..

12.07.15

I am a bit confused…..

After playing with my .iso as a Source of files, I decided to try my C:ESD folder instead. Judging by dates of files only, I guessed the files where 10586. I also finally found the “Install.esd” file in the ESDWindowsSources folder and did the following:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:C:ESDWindowsSourcesInstall.esd:1 /LimitAccess.
the command did not work (source files not found) so I changed the text and I ran it like this:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:C:WindowsSourcesInstall.esd:1 /LimitAccess.
the command did not work (source files not found) so I corrected the text to mirror the suggestion provided above. I ran this:

DISM /Online /Cleanup-Image /RestoreHealth /source:ESD:C:SourcesInstall.esd:1 /LimitAccess
unfortunately, I got the same error message; “Source files not found”.

I think I am following directions but I obviously must be missing something ….
Can either one of you gentlemen help me out?
I would really like to get the command to work to repair corruption found by running DISM /… /Scan Health and /Check Health

thank you

On my Win10 Home the default path to the install.esd file is C:$WINDOWS.~BTSourcesinstall.esd. Pay particular attention to the $ symbol and the .~BT extension, makes it a different Folder from C:Windows.

Before you wonder "Am I doing things right," ask "Am I doing the right things?"

Reply | Quote

> reply to jwoods, et.al.

thank you for the tenforums link.
regarding my little project, it occurred to me to take my own advice and simply upgrade my W10 installed build 10240 with build 10586. there is no reason to spend time repairing corruption of 10240 when installing 10586 should effectively solve my problems; I hope!!

ps. you might consider turning on private messaging in your profile.
pm

Reply | Quote

I frequently used DISM.exe on running W8 and W8.1 x64bit operating systems.

I may be particularly dense this morning, but for what reason are you doing this? What image are you trying to fix and why is it subject to frequent corruption?

Reply | Quote

no, you are not dense this morning.

why am i doing this? i assume you mean struggling with DISM.exe.
the image i am trying to fix is Windows Pro 10×64 build. I erred in my OP because the build is not 10586 but something earlier.

i was trying to fix some corrupted files identified by running DISM /online/cleaup-image/ScanHealth and also CheckHealth on a W10 install.
The corruption was identified as “repairable”. But, when I ran DISM /online../RestoreHealth. I got an error message that Windows could not identify a location for W10 source files needed to repair the installation. I used RestoreHealth before on W8 and W8.1 and never received the error message. Since I never had to use the /Source flag with DISM before i asked for some help.

No, the operating systems on my PC have not been subject to frequent corruption.

I did abandon my DISM attempts as I did not understand the DISM /Source flag use.
I decided to install build 10586 via MS Media Creator downloading to a USB drive.
Now I am having trouble with that; the new installation process does not complete with the error: :Modern Setup Host has failed”…
It is time for me to walk away from it for awhile and try again later.

I may be particularly dense this morning, but for what reason are you doing this? What image are you trying to fix and why is it subject to frequent corruption?

Reply | Quote

Here are some suggestions that may help with that error – http://www.thewindowsclub.com/modern-setup-host-has-stopped-working-windows

Reply | Quote

I got lost off a while ago :lol

I don’t use Win 10 but it’s useful to know what to advise when someone reports the /restorehealth cmd returns that it is unable to find the source file.

Reply | Quote

Should there be a dot after $WINDOWS ?

Reply | Quote

Should there be a dot after $WINDOWS ?

Just click on install.esd, hold down shift key, and right click. Choose Save as Path. That will put the whole exact path in your clipboard. You can then copy it into your dism command.

Reply | Quote

Should there be a dot after $WINDOWS ?

Yes. Folders can have extensions just like files.
C:$WINDOWS.~BTSourcesInstall.esd

Before you wonder "Am I doing things right," ask "Am I doing the right things?"

Reply | Quote

OK SkinnyWomen, let’s take it from the top. First press Windows key and R. Type in Winver and press OK. My image below is what I see. I put a RED BOX around what I need from you. Please give that info to us, then we can go from there.

Reply | Quote

SkinnyWomen please read private messages I sent you.

Reply | Quote

FYI. djohnson explained the /source flag with DISM for me and I finally could point my use of DISM to /Source correctly.
Also, thanks for the support of other posters…..

i no longer have the DISM problem of DISM not finding the source files to repair corruption.
Berton: 10.4
Sudo15: see Berton’s reply and look at C: in W10 File Explorer

-pm aka skinnywomen

Reply | Quote

Sudo15: see Berton’s reply and look at C: in W10 File Explorer

-pm aka skinnywomen

The problem arises because I don’t have Win 10 to try it out on.

I don’t know if the PM was personal but it’s normal practice that any advice given has to be done in the open forum so that it can be Moderated, so the rest of us are lacking in any detailed advice djohnson may have given on the subject in the PM – but I’ll leave it at that and glad you were able to get it sorted.

Reply | Quote

The problem arises because I don’t have Win 10 to try it out on.

I don’t know if the PM was personal but it’s normal practice that any advice given has to be done in the open forum so that it can be Moderated, so the rest of us are lacking in any detailed advice djohnson may have given on the subject in the PM – but I’ll leave it at that and glad you were able to get it sorted.

I believe the problem, correct me if I am wrong Skinneywomen, lay with a basic unfamiliarity with mounted volumes. The path to the install.wim must be with the mounted volume, and not the volume where the original ISO was located.

Reply | Quote

That is so cool. I am glad you figured it out!

Reply | Quote

Thanks for the clarification DJ – with not having Win 10 I’m unable to mount a volume to see the options that follow.

Reply | Quote