Windows 10: Run SFC Command in Windows 10

Hello Cliff, *Smile

The SFC command is used for repairing corrupted or modified Windows system files. It can only be used on the Windows drive.

What is wrong with the USB?

 

Hey win10 forums,

I have run the sfc /scannow command and got the error message regarding the corrupt files found but unable to be repaired. i did as you said in step 5 with the sfcdetails.txt.

I have these 5 things which i'm not sure what to proceed to in order to fix these

2015-12-04 22:43:27, Info CSI 0000524e [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-04 22:43:27, Info CSI 00005250 [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-04 22:43:27, Info CSI 00005252 [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-04 22:43:27, Info CSI 00005254 [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-04 22:43:27, Info CSI 00005256 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-04 22:43:27, Info CSI 00005259 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch

i have previously tried the DISM /Online /Cleanup-Image /RestoreHealth command but that couldnt locate the source.

is it worth fixing these few errors or would it be alright to leave it as it is?

thanks!

Alex

 

Too do that needed repair you need your Win10 1511 iso that you installed your Win10 on. The files that DISM command is looking for are on that iso file. Then mount it, and tell Dism where it is. similar to this command.
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

Where the H <-- needs to be where ever that iso is mounted. Could be on a usb stick, dvd, or mount on your hard drive.

 

Brink:
Nothing wrong with my USB drive or connection at all but I was not thinking about the command "sfc /scannow" only working with the win 10 system files. Thanks for all the work and answers that you post. This is a wonderful website.. and great help here from users.

All be safe.. best to all. Cliff M

 

I'm glad to hear the USB is fine. *Smile

 

thanks, i will download the iso from microsoft later and report back how it goes

 

Fresh install of windows 10 installed from USB drive created with official media creation tool.
Should I be worried? Did log file as in this tutorial there are many lines but most are same (my graphics card is not GeForce its Intel's integrated gpu, driver from WU).

sfcdetails.txt

 

Hello VBs, *Smile

The hash mismatch for the opencl.dll file found by SFC is only a bug for the NIVIDIA driver. It's safe to ignore until NIVIDIA fixes it in the next driver release.

 

But he did say that his GPU is not NVIDIA but Intel, so how come he still has that problem?

 

He may have an Intel graphic chip, but he may also have NVIDIA as well like mine.

Either way, there's no need to do anything to fix it.

 

Oh ok, got it. Thanks for the clarification.

 

Thank you for fast response.

PC that has error definitely doesn't have any GPU other than one integrated with Intel CPU. It's operating as headless server (mostly for running hyper-v and storage spaces), so no other graphics card is necessary (it's not laptop with hybrid graphics). Scan was performed in RDP connection from PC with nVidia card, but strangely enough that PC with nvidia card shows no errors when running sfc /scannow. Does running sfc /scannow when connected in RDP has anything to do with errors?