How to get damn DISM to work?

[RejZoR]

I'm using this command:
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1

And the god damn thing keeps bitching source files can't be found even though I'm pointing the path to the darn thing. ISO image is mounted and yet this retarded tool just can't see it. I don't understand why has Microsoft made this tool so monumentally retarded compared to Win8.x where you just used this:

Dism /Online /Cleanup-Image /ScanHealth

And it just worked. Any ideas?

 

[jboydgolfer]

"sources" no capitol , and plural


i mounted the ISO, and ran this command here

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\Install.wim:1 /LimitAccess
"x" = drive letter

oh, your just trying to scan health.....
try this page here
http://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

 

[RejZoR]

I've copied this off an online guide... And several of them had this. Apparently they all copied eachother without actually testing the damn thing. I'll try that.

 

[jboydgolfer]

you dont need the "esd" command unless your running an esd file type.

i recommend if ytour just scanning to
DISM /Online /Cleanup-Image /ScanHealth

or DL an ISO , and run the command i linked above.
DISM /Online /Cleanup-Image /RestoreHealth /sources:WIM:X:\sources\Install.wim:1 /LimitAccess
"x" = drive letter.

iso can be DL'd from here
https://www.microsoft.com/en-us/software-download/techbench

be certain to run elevated CMD prompt.

 

[RejZoR]

Well, I've tried that command and it doesn't work as it always ends with error 0x800f081f. As for ESD, my original unaltered Windows 10 image only contains install.esd and NO install.wim.

 

[RejZoR]

God damn it, I tried like 20 different versions from 10 different guides and none work. Keeps on bitching about "cannot find source". I just don't even know anymore...

 

[blobster21]

At this point, you might try ntlite aswell : https://www.ntlite.com/
(just to make sure it's not related to syntaxe errors)

 

[RejZoR]

I don't understand, if it was a syntax issue it would say that. Instead it just complains the source can't be found even though I'm pointing at it. Then I have to figure out how it's not found. The file not found or it can't find stuff inside the ESD or something third. I have no clue.

 

[jboydgolfer]

God damn it, I tried like 20 different versions from 10 different guides and none work. Keeps on bitching about "cannot find source". I just don't even know anymore...

I got that damn "cant find source" 20 times the other day when i went through what u r now.

The way i got thru it, was to go to the DL link i posted, get an ISO of win10 N ,
Mount it by right clicking on it as thats built into 10
Then once its mounted , youll have the install.wim file,and the rest in a mounted drive

After those steps, you just need to use the command from anove and replace the x with your drive letter,and it should be fine.$$be sure all words are spelled exactly as they are in the directories when entering your commands##
For what its worth, i went thru this the other day too, and it turned out to be a letter here, or capitol there that fucked me up, it sux i know. but if it worked for me, hopefully it will 4 u 2

 

[RejZoR]

Yes, I have the image mounted, the same bloody image I've used to install the OS I'm just using. This is absurd. I've tried this:

Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd /limitaccess
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1 /limitaccess

None of this crap works even though entire freaking internet is saying that this is the way to do it. Some even mention using quotas for the path which makes no difference (It doesn't need it anyway since there aren't any spaces anyway.

I just can't understand how can OS integrity check tool feature be dumber as years pass by instead of being smarter and more useful.

EDIT:
Redownloading 4 gigs of stupid image because the one I have apparently isn't good enough. *sigh*

 

[jboydgolfer]

I see its giving you trouble.
I too couldnt get the esd source command to work, thats why i suggest you go the "install.wim" route.

You posted that your downloading a iso, hopefully you try the wim method.

Best of luck

P.S.
if you decide to go with the "install.wim" method i recommended, this command worked just a moment ago for me, and hopefully it will for you too...

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\Install.wim:1 /LimitAccess
im sure you know, but be certain to replace "X" with Your mounted drive letter.

 

[blobster21]

Well, i browsed to the sub directory containing the install.esd file and initiated the following command (one of your previous command)

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:install.esd:1

it worked as expected

 

[RejZoR]

Not in my case. Apparently I'm using some sort of freaking alien version of Windows 10...

 

[Kursah]

Excellent command and utility to know about and use. I use it regularly. Not so much for image creation any longer but for image repair quite often.

 

[blobster21]

i forgot to mention that i decompressed this microsoft iso on my harddrive, could it be that you are trying to access the install.esd from a virtual drive ? (in which case it's read only ?)

 

[FordGT90Concept]

Is "E:" correct? You're calling it from "F:"

 

[RejZoR]

Apparently images downloaded through Media Creation tool aren't good (the ones I had). They come with INSTALL.ESD and are entirely rejected by DISM. I wonder what else is borked up with those...

The newly downloaded one has INSTALL.WIM and it worked this time. Absolutely bizarre.

 

[RejZoR]

Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.

 

[RejZoR]

Thanks everyone, I've compiled it into my guide here:
https://rejzor.wordpress.com/2016/06/18/windows-10-system-integrity-check-sfc-dism/

Credits for TPU and @jboydgolfer included

 

[crazyeyesreaper]

FUCKING LIFE SAVING, ran into the Nvidia Opencl.dll issue with Windows 10 aka windows says its borked cant fix it need to do DISM to fix it had the same issues you were having. Thank fucking god the BSODs have stopped.

 

[DeathtoGnomes]

Is "E:" correct? You're calling it from "F:"

No its F: and U: being used here.

 

[silkstone]

I came across this exact same problem.

Start menu was borked and sfc could not fix it. I tried using the .iso from the download tool, but DISM would reject it.

I ended up having to re-install the OS.

 

[RejZoR]

Oh my god, this is the most hilarious shit ever. Just reinstalled OS from ISO's given above, installed few drivers and guess what I got when I tried SFC and DISM for lol? Windows found corrupted files and was unable to fix them. Like 1 hour after OS installation. No wonder computers are all messed up if OS can't hold its integrity true after 1 hour after absolutely clean installation. Microsoft, what the hell are you doing?

 

[FordGT90Concept]

It's probably the drivers. Microsoft distributes what vendors give them.

Case in point: this issue with Speaker Fill not working is now fixed in the latest drivers from Windows Update.

If you know it is the NVIDIA driver causing problems, report it to NVIDIA so they can get it fixed and Microsoft can push out a fixed driver.

 

[crazyeyesreaper]

It's probably the drivers. Microsoft distributes what vendors give them.

Case in point: this issue with Speaker Fill not working is now fixed in the latest drivers from Windows Update.

If you know it is the NVIDIA driver causing problems, report it to NVIDIA so they can get it fixed and Microsoft can push out a fixed driver.

My Opencl.dll issue is due to Microsoft and Nvidia not fixing an issue thats been around since mid 2015. Apparently Microsoft doesn't like th eOpencl.dll Nvidia driver bundles so it defaults to microsoft one causing conflicts. Apparently Nvidia fixed this already but it keep popping up. for most users it just creates a minor error they will never notice for me tho it caused BSODs. The above fixed it. Also seems to be more common problem with upgraded systems vs fresh installs.