Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

How To Fix Corrupt Files In Windows 10 (sfc /scannow)


  • Please log in to reply
7 replies to this topic

#1 Rocky Bennett

Rocky Bennett

  • Members
  • 2,819 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Mexico, USA
  • Local time:09:39 AM

Posted 03 June 2016 - 05:42 AM

Hello All,

My system was acting a little funny so I ran an sfc /scannow of the system from my command prompt. It came back with the message

 

Windows resource protection found corrupt files and was unable to fix them. The details are in the CBS log.Note that logging is currently not supported in offline servicing scenarios. Well I worked for a couple of hours to fix this error by restoring my computer then resetting my computer all to no avail, the error was still there.  I finally re-formaated the drive and installed Windows 10 from scratch and there were no errors. Great. I did several things and updates and all kinds of things and still no error. Great. As soon as I installed my Microsoft 365 and ran the sfc /scannow the error reappeared. Of course I am not 100% sure that the two are connected but I think that that are.

 

Again I tried for hours to correct the error and I can not fix it with my limited knowledge and ability. In my CBS log I see that the error might be:

 

2016-06-02 18:58:43, Info                  CSI    00003e0a [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-06-02 18:58:43, Info                  CSI    00003e14 [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-06-02 18:58:43, Info                  CSI    00003e15 [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-06-02 18:58:43, Info                  CSI    00003e18 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-06-02 18:58:45, Info                  CSI    00003e7f [SR] Verify complete

 

I do know if that is the source of corrupt file, but I think it is and I can not figure out how to fix it. I also ran the command

 

DISM /Online /Cleanup-Image /RestoreHealth

 

several times and I was unable to fix the error. I get error: 0x800f081f, the source file could not be found, use the source option to specify the location of the files that are required to restore this feature.

 

I am running Windows 10 Pro but I not sure how to use Group Policy Editor to allow my system to fix this problem.

 

I need help. Any help would be appreciated.

 

Rocky Bennett

 

 


594965_zpsp5exvyzm.png


BC AdBot (Login to Remove)

 


#2 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,683 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:39 AM

Posted 03 June 2016 - 06:36 AM

Known issue under Windows 10. You can follow the guide below I wrote on Sysnative to get a SFCFix fix for it.

https://www.sysnative.com/forums/windows-update/18121-guide-opencl-dll-corruption-sfc-dism-windows-10-update-1511-th2.html

unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.


#3 Rocky Bennett

Rocky Bennett
  • Topic Starter

  • Members
  • 2,819 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Mexico, USA
  • Local time:09:39 AM

Posted 03 June 2016 - 06:59 AM

Thanks for the link, I will look at that and report back.


594965_zpsp5exvyzm.png


#4 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,683 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:39 AM

Posted 03 June 2016 - 07:03 AM

No problem. It should solve your issue pretty quickly.


unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.


#5 Rocky Bennett

Rocky Bennett
  • Topic Starter

  • Members
  • 2,819 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Mexico, USA
  • Local time:09:39 AM

Posted 04 June 2016 - 03:21 AM

Thanks Aura, but I looked over that link and it did not seem to apply to my situation. I did fix the problem though, but it was quite complicated. I had to download a brand new copy of Windows 10 from the techbench and substitute the good files from the new copy of Windows 10 with the corrupt files that were in my installed copy of Windows 10.

 

After this my system seems to perform correctly and the sfc /scannow results show no corrupt files.

 

All is good.


594965_zpsp5exvyzm.png


#6 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,683 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:39 AM

Posted 04 June 2016 - 08:32 AM

Actually, it did apply to your situation, since this is a known issue with Windows 10 TH2. The opencl.dll file gets overwritten by one from NVIDIA, and since Microsoft didn't take it into account, SFC report it as corrupt because the B64SHA256 hash doesn't match the expected one. All you had to do is to run the fix that would replace the opencl.dll file in the store with the good one (the right hash), and run SFC again so it could use that good file to replace the other ones.

unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.


#7 Rocky Bennett

Rocky Bennett
  • Topic Starter

  • Members
  • 2,819 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Mexico, USA
  • Local time:09:39 AM

Posted 04 June 2016 - 09:02 AM

Thanks. I hope that this does not happen to me again, but if it does I will certainly give your fix a try.

 

Thanks again.


594965_zpsp5exvyzm.png


#8 Aura

Aura

    Bleepin' Special Ops


  • Malware Response Team
  • 19,683 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:39 AM

Posted 04 June 2016 - 09:03 AM

No problem, you're welcome!

unite_blue.png
Security Administrator | Sysnative Windows Update Senior Analyst | Malware Hunter | @SecurityAura
My timezone UTC-05:00 (East. Coast). If I didn't reply to you within 48 hours, please send me a PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users