Windows 10: Run SFC Command in Windows 10  

Page 12 of 17 FirstFirst ... 21011121314 ... LastLast

  1. Posts : 26,810
    Windows10Pro 64Bit - Build 14393.1198
       25 Dec 2015 #110

    Brink said: View Post
    Hey Mike,

    I just ran SFC /SCANNOW as a test using the latest 361.43 NIVIDIA driver, and SFC came back with no issues. Looks like it's sorted now.
    Well we are both running the same release, but when I run SFC /verify it reports same error.....hmmmm.....ok I'll try running same command you just did.....but I'm going to take a pic before and after to make sure Windows does not delete one of my opencl.dll files. I'll report back Shawn.
      My ComputersSystem Spec


  2. Posts : 26,810
    Windows10Pro 64Bit - Build 14393.1198
       25 Dec 2015 #111

    @Brink
    Ok Shawn I ran SFC /scannow and just as I thought it would, it found errors, (opencl) and repaired the errors, and REMOVED 1 of my Opencl.dll files. Take a look at the 2 pics I posted below. If you look at 1st pic, its shows Opencl.dll in my C:/Windows/SysWow64 folder, Then in my 2nd pic, Windows removes it after running SFC /scannow. This is a Microsoft problem and not Nvidia's so only Microsoft can fix this issue. But.... it does seemed to be fixed in one of the latest Insider Builds.

    Click image for larger version. 

Name:	NewOpen.PNG 
Views:	52 
Size:	63.7 KB 
ID:	55318

    Click image for larger version. 

Name:	Newopen2.PNG 
Views:	69 
Size:	69.1 KB 
ID:	55319
      My ComputersSystem Spec


  3. Posts : 20,887
    64-bit Windows 10 Pro build 16199
    Thread Starter
       25 Dec 2015 #112

    It seems so then. I'm using the latest 11082.1000 build as well.
      My ComputersSystem Spec


  4. Posts : 26,810
    Windows10Pro 64Bit - Build 14393.1198
       25 Dec 2015 #113

    Brink said: View Post
    It seems so then. I'm using the latest 11082.1000 build as well.
    Yes I thought you might be, as it IS fixed in that build. But not for me on build 10586.36 BUT knowing that Microsoft IS aware of this issue, and fixed it in the newer insider builds makes me now know that in some future update I will get a fix.
      My ComputersSystem Spec

  5.    13 Jan 2016 #114

    Hello!

    I ran the SFC /SCANNOW command and the result was this:

    2016-01-13 02:04:59, Info CSI 00004c3e [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
    2016-01-13 02:04:59, Info CSI 00004c41 [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
    2016-01-13 02:04:59, Info CSI 00004c42 [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"
    2016-01-13 02:04:59, Info CSI 00004c45 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

    I read the note that says we can ignore this, but is there a way to fix that?

    Thanks in advance.
      My ComputerSystem Spec


  6. Posts : 26,810
    Windows10Pro 64Bit - Build 14393.1198
       13 Jan 2016 #115

    Moutro said: View Post
    Hello!

    I ran the SFC /SCANNOW command and the result was this:

    2016-01-13 02:04:59, Info CSI 00004c3e [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
    2016-01-13 02:04:59, Info CSI 00004c41 [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
    2016-01-13 02:04:59, Info CSI 00004c42 [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"
    2016-01-13 02:04:59, Info CSI 00004c45 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

    I read the note that says we can ignore this, but is there a way to fix that?

    Thanks in advance.
    Most of the time SFC /Scannow DOES fix the opencl issue. After you ran the SFC command, in your command prompt did it say that it ran successfully?? Most of the time it will. (even thou it does not actually repair this problem correctly, it does report that it did. )
      My ComputersSystem Spec

  7.    13 Jan 2016 #116

    "Windows Resource Protection found corrupt files but was unable to fix some of them."

    That's the message thats it shows.
      My ComputerSystem Spec


  8. Posts : 26,810
    Windows10Pro 64Bit - Build 14393.1198
       13 Jan 2016 #117

    Moutro said: View Post
    "Windows Resource Protection found corrupt files but was unable to fix some of them."

    That's the message thats it shows.
    Ok Sorry for late reply, been outside snowblowing.
    You can repair your Windows 10 using DISM command. Here are the instructions.

    Have you saved a Windows 10 ISO from tech bench? (has to be from Tech Bench)
    If yes, please mount it.
    Then go to elevated command prompt and copy/paste this...............
    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess
    Note: H is the letter where the iso is mounted. If yours is not H, change it.
    1) Best way is copying the install.WIM from the ISO to a partition, like E:
    2) DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:E:\Install.wim:1 /LimitAccess
      My ComputersSystem Spec


  9. Posts : 26,810
    Windows10Pro 64Bit - Build 14393.1198
       13 Jan 2016 #118

    If you have trouble understanding this, just ask me, I'll try to explain it better....

    The only file DISM is looking for in the ISO is Install.wim which is on the iso from tech bench. This file has all the needed files to repair your Windows 10.
      My ComputersSystem Spec

  10.    13 Jan 2016 #119

    Ok thanks. Gonna try it now.
      My ComputerSystem Spec


 
Page 12 of 17 FirstFirst ... 21011121314 ... LastLast

Related Threads
How to Open an Elevated Command Prompt in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands in an elevated command prompt, you can perform tasks that require...
General Tips Open Command Prompt in Windows 10 in Tutorials
How to Open a Command Prompt in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands at the command prompt, you can perform tasks on your computer without using the Windows...
How to Open a Command Prompt at Boot in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands at the command prompt, you can perform tasks on your computer without using the...
Show Us Your Command Centre in Chillout Room
This is my study. Also my office when I am working. I call it Sanctuary. 327 328
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:27.
Find Us