Windows 10: DISM and SFC

Yes, in my understanding, if sfc passes, DISM is not necessary.

 

Hi,

It can but then you have to run the correct command line by replacing .wim for .esd.
That said, just from experience, .wim files seem to be "easier" for DISM to handle as it stands .

Cheers, *Wink

 

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?
TY
Peter

 

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.
TY again
Peter

 

Hello again
I thought you would find this interesting:
I typed ,"Can you run a computer that failed SFC in my search box and the bottom link says "SFC Command - Run in Windows 10 - W indows 10 forums".

BRINK said to run SFC /scanow Command at boot

I followed the directions for #1 and under 'Leaving DiskPart', his screen shows X:\Sources> HOWEVER,
my screen says, after X:\ windows 32\ not Sources

Because there has been a question about sources in this thread, I thought it coincidental that this occurred.

If it has any significance, please let me know as I may have an adjustment to make.
TY
Peter

 

All this does not matter. Surely you can restore uncorrupted Miscrosoft opencl.dll back using DISM and install.wim followed by sfc by the method posted in this forum already many times, but it will damage correct Nvidia/ATI/Intel opencl.dll.

 

I believe you - my naive level just thought there may have been a correlation between my path and Brink's.
I will leave the pcs as they are and thank you for your help, and time saving.
Would allowing the latest NVidia update affect anything for better or worse, as I see you refer to NVidia?
Peter

 

If you are getting " X:\windows\system32 " in your command prompt
then you are booted into winPE and trying to repair an Off-line windows image..
All the commands and tutorials here are for On-Line windows images..

for the tutorial
X = the drive letter assigned to the setup media ( mounted ISO - DVD - USB)

what ever drive letter was assigned by your PC to the media - you would replace X with that drive letter

 

So I should have changed the letter to the one assigned in the drill.

 

I performed an image restore and am all set with SFC .
Should I keep the 7 GB previous Win installations in system cleanup?