How to repair your system files using Dism and Sfc in build 10041

adamf said:

Check your file E:\Sources\install.wim exists. You could have an ISO that contains an esd not a wim.

You need a space and between /Cleanup-Image and /RestoreHealth also.

That's it, my file extention is esd. What do I need to do now? Thanks.

jjthenovice said:

That's it, my file extention is esd. What do I need to do now? Thanks.

You need to convert your ESD to a standard ISO not an ESD ISO.

I just checked the tutorial and it says nothing about it but when I ran it it a few days ago I'm sure it gave me 4 options one of which was "Create Standard ISO" and one was "Create ESD ISO" It seems the tutorial might have changed. Download the utility again and run it again and then point the path in the above command to the generated .wim (assuming it makes an iso with a wim).

If that doesn't work you'll have to ask @Kari on this thread Windows 10 Forums why you are getting an esd not a wim in your iso.

adamf said:

You need to convert your ESD to a standard ISO not an ESD ISO.

I just checked the tutorial and it says nothing about it but when I ran it it a few days ago I'm sure it gave me 4 options one of which was "Create Standard ISO" and one was "Create ESD ISO" It seems the tutorial might have changed. Download the utility again and run it again and then point the path in the above command to the generated .wim (assuming it makes an iso with a wim).

If that doesn't work you'll have to ask @Kari on this thread Windows 10 Forums why you are getting an esd not a wim in your iso.

Thanks for the reply. I downloaded WinReducer and copied the install.esd to my hard drive and converted it to WIM. Then I just pointed to it on hard drive and it worked. When I ran sfc /scannow it found and fixed the corrupted files. Thank you for the help, it got me pointed in the right direction.

Good news :)

May I ask a quick question? Why did I have to run this command: Will I need to keep the install.wim? It's currently in the root directory of my C drive. As stated earlier I had to convert the install.esd on my iso to install.wim. Thank you.

Generally the dism command will repair the component store by looking on the internet. However if this doesn't work you need to use a different source. This can be either another windows installation or a .wim file. Generally an ISO will contain a .wim but (depending where you got it or how you made it) it may contain a .esd file instead. That is why you had to convert it - your ISO didn't contain a wim.

Now I have run it once, and also run sfc /scannow dism works fine without specifying the .wim. I can just enter the command Dism /Online /Cleanup-Image /RestoreHealth without additionally specifying the /source parameter like @Cliff S did in the post above).

So no, if you can run dism and sfc now without error you don't need to keep it. You can always convert the esd again if you do. You will not need it for anything else as you can re-install from the compressed ISO you have.

If you have lots of space though you can just leave it - it will not do any harm (except make your backups a bit slower).

adamf said:

Generally the dism command will repair the component store by looking on the internet. However if this doesn't work you need to use a different source. This can be either another windows installation or a .wim file. Generally an ISO will contain a .wim but (depending where you got it or how you made it) it may contain a .esd file instead. That is why you had to convert it - your ISO didn't contain a wim.

Now I have run it once, and also run sfc /scannow dism works fine without specifying the .wim. I can just enter the command Dism /Online /Cleanup-Image /RestoreHealth without additionally specifying the /source parameter like @Cliff S did in the post above).

So no, if you can run dism and sfc now without error you don't need to keep it. You can always convert the esd again if you do. You will not need it for anything else as you can re-install from the compressed ISO you have.

If you have lots of space though you can just leave it - it will not do any harm (except make your backups a bit slower).

Thanks for the info. Things sure were more simple in the old days (Win 3.0 and 3.1) then "alive in 95 (Win95) the fix in 96. Just a little nostalgia..... Again thanks...

jjthenovice said:

Thanks for the info. Things sure were more simple in the old days (Win 3.0 and 3.1) then "alive in 95 (Win95) the fix in 96. Just a little nostalgia..... Again thanks...

Well I suppose so considering that there wasn't a component store to even repair - you had to guess (thus the 'dll hell' expression).

A bit like a caveman complaining about their fire going out and yearning for the days of raw meat when everything was easier

And you are of course, welcome :)