Depending on how you got your ISO file, it may have an install.esd and not an install.wim. An .esd file is compressed, as I understand and a .wim file is not. It can't read from an esd file.
Thank you for the clarification. I understand the difference. This is quite complicated because there are so many variables.
I think I just got the ISO file from MS when you Google it and burned it to disc. I may have gotten it from the media recovery tool though - I really don't remember. Is there a way to tell? If I understand you I want the .wim ISO.
I think I will take the least complicated road. Too old & too sick but need functional machines.
Tomorrow I will try each of my 2 images and see if SFC works with either. The first was a clean install from the iso disc and the 2nd image was just after the last big update. I think I will try the last one first. If not I will reluctantly either try a reset or a clean install like I did before. I know the ISO disc was being read b/c when I booted from it, Win 10 was installed.
BTW, if all a/v + anti malware tests are OK is there any harm to running a system that doesn't pass the SFC and DISM test?
TY for your help.
P.S. Anything you can tell me to make sense would be greatly appreciated. I am open to corrections.
Yes, in my understanding, if sfc passes, DISM is not necessary.
It can but then you have to run the correct command line by replacing .wim for .esd.Depending on how you got your ISO file, it may have an install.esd and not an install.wim. An .esd file is compressed, as I understand and a .wim file is not. It can't read from an esd file.
That said, just from experience, .wim files seem to be "easier" for DISM to handle as it stands .
If it is still looking for a source - after running option 3 - with the setup media mounted within the Host OS
Then the missing file is not present on the Setup Media, nor is it in the winsxs folder within the Host windows...
The missing file came as part of a windows update... And by all rights should of been saved into the windows\winsxs folder on the Host OS..
you can use an .esd file as a repair source.. the issue is you can not mount an .esd file..
My program exports the install.esd into an install.wim file - then mounts the install.wim for use as the repair source..
SFC does not use the either the install.wim or install.esd..
Dism can use them as a repair source
Please stop giving standard DISM "restore from install.wim" advise, it breaks Nvidia/ATI/Intel driver.
The correct fix will be to remove wrongly installed and activated by Microsoft wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 directory (Microsoft RemoteFX Display driver, 32bit part, which contains opencl.dll with reduced functionality, which overwrites correct Nvidia/ATI/Intel \SysWoW64\opencl.dll on upgrade or attempt of DISM recover from install.wim) from WinSxS (64bit counterpart is in amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586 .0_none_5fcf2a87752df0d7 directory, but is inactive and does no harm). But I know no tool for correct selective remove or deactivate of specific directory from WinSxS. Since \SysWoW64\opencl.dll is hardlink to WinSxS one, attempt to install Nvidia/ATI/Intel driver corrupts two Microsoft opencl.dlls at once (so sfc /scannow fails to recover), and attempt to recover WinSxS one from install.wim damages Nvidia/ATI/Intel display driver's opencl.dll from other hand.
I am sorry but I am only an average user and this is pretty techy.
I wanted to know;
1-is there a big downside to running a PC that cannot run SFC successfully and
2- should I do a system restore, image or reset to fix the corrupted files>SFC?
1) No. With corruption you got correct Nvidia/ATI/Intel opencl.dll
2) No, it makes things worse, breaking 32bit applications wich use OpenCL API, by replacing opencl.dll with Microsoft one with reduced functionality.
For now it will be better to live with this corruption until Microsoft will fix it (if they ever bother to).
If there is no security or functionality downside I will keep it as is.
I am glad you told me not to image back to after the last big update as I was just abut to.
I also had an image that I created after a clean installation of Win 10.
It sounds like MS last big update messed things up? I keep getting an advisory from NVidia that there is a download available. I am not a gamer and I think it is for gamers so I will disregard that update. I only mention this b/c I saw NVidia in your explanation.