Run SFC Command in Windows 10

kevindd992002 · 02 Dec 2015

Yeah, I figured. It's just that I posted several threads here already and it seems that nobody knows the answers to my questions

Brink · 02 Dec 2015

Hopefully, soon.

acmanten · 03 Dec 2015

What is the correct syntax for running command: sfc /scannow
on my Drive F: (which is USB connected) instead of normal drive C:

Thanks

Brink · 03 Dec 2015

acmanten said:

What is the correct syntax for running command: sfc /scannow
on my Drive F: (which is USB connected) instead of normal drive C:

Thanks

Hello Cliff, :)

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?

poolwizard · 04 Dec 2015

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

OldMike65 · 04 Dec 2015

poolwizard said:

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.

acmanten · 05 Dec 2015

Brink said:

Hello Cliff, :)

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?

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

Brink · 05 Dec 2015

acmanten said:

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. :)

poolwizard · 07 Dec 2015

OldMike65 said:

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.

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

VBs · 24 Dec 2015

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).

2015-12-24 21:18:26, Info CSI 00003db2 [SR] Verifying 100 (0x0000000000000064) components
2015-12-24 21:18:26, Info CSI 00003db3 [SR] Beginning Verify and Repair transaction
2015-12-24 21:18:28, Info CSI 00003e25 [SR] Verify complete
2015-12-24 21:18:28, Info CSI 00003e26 [SR] Verifying 100 (0x0000000000000064) components
2015-12-24 21:18:28, Info CSI 00003e27 [SR] Beginning Verify and Repair transaction
2015-12-24 21:18:29, Info CSI 00003e29 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-24 21:18:29, Info CSI 00003e34 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-24 21:18:29, Info CSI 00003e35 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-12-24 21:18:29, Info CSI 00003e38 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2015-12-24 21:18:31, Info CSI 00003e9d [SR] Verify complete
2015-12-24 21:18:31, Info CSI 00003e9e [SR] Verifying 100 (0x0000000000000064) components
2015-12-24 21:18:31, Info CSI 00003e9f [SR] Beginning Verify and Repair transaction
2015-12-24 21:18:33, Info CSI 00003f0d [SR] Verify complete

sfcdetails.txt