Windows 10: SFC Corrupt Files on CBS.Log ?

Can someone please help...my sfc command says it can't fix some files...but I don't know what files or how to fix them...looked at CBS.log but doesn't mean much to me.

Tried to attach CBS log but am getting this error:

CBS.log: Your file of 9.00 MB bytes exceeds the forum's limit of 2.00 MB for this filetype.

could someone let me know how to upload log and check what files are 'Corrupt' and how to fix them...?

Thanks...TiminAz

:)

 

Accidentally Deleted

Hi!

If the system is running okay, but your are still trying to figure out the corrupted files look in the CBS.log. Or maybe other members will read them for you. I never found sfc or DISM very useful. Start a new post sfc found corrupted files, and post the
CBS.log.

 

DISM command within Windows 10 Pro

Please share CBS.log after running SFC once because sometimes SFC gives a false note that files are corrupt.

You would find CBS.log in C:/Windows/logs/CBS.log

Share it on onedrive/Gdrive where you want publically and drop a link.

 

If you filter your file and send only the filtered items, that will help alot. Try opening CBS.log in Notepad, click Edit, Find and then enter "corrupt" in the search box. Cut'n'paste ONLY lines that meet this search criterion into a second file, and you should have something much smaller. That, you should be able to upload.
HTH,
--Ed--

 

Hi,

Use member Kyhi's excellent IMAGE HEALTH tool:

Windows 10 Recovery Tools - Bootable Rescue Disk

Note that for some tasks DISM (which is what IMAGE HEALTH uses) needs a Windows installation media mounted for it requires the install.wim to extract files from in order to repair damaged image files.
This can be a mounted ISO file or a USB stick, DVD etc.

Cheers, *Wink

 

Sorry Ed...didn't think of that...here's corrupted entries only:

2016-10-29 11:33:57, Info CSI 00004550 [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-10-29 11:35:43, Info CSI 000055ea [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-10-29 12:07:25, Info CSI 0000459c [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-10-29 12:09:09, Info CSI 00005636 [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-10-29 12:22:28, Info CSI 00004591 [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-10-29 12:24:16, Info CSI 0000562b [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted


Thanks...TiminAz

 

Hi,

Looks like the NVIDIA drivers have overwritten the Windows libraries.
See my post right above yours.
After this is fixed I suggest you download and install the latest drivers for your graphics card.

Cheers, *Wink

 

Yes, FWIW this is a well-known issue that works something like this:
1. before the latest Nvidia drivers enter the picture, Windows references its own internal opencl.dll file
2. When the latest Nvidia drivers get installed they insert their own (and correct) version of opencl.dll to go along with their drivers
3. When DISM ... /clean-image /restorehealth (or whatever) is run, that code looks for a hash that matches #1 not #2, even though #2 is correct for an updated Nvidia driver
We've been sqawking about this to Microsoft since the problem first surfaced a while back (perhaps even late in 2015) and they've been on-again, off-again in fixing it. You can repair the problem if you like, but you don't have to, because it's not really a problem.
Capisce?
HTH,
--Ed--

 

Success !!!To all who helped on this...my problem has been completely corrected...but I can't say 'solved'...since I don't know exactly what happened. What I did is go back to a complete Acronis tib system backup of my Windows Pro C: drive system from July 1, 2016After start up...I just left everything alone and low and behold...everything...including Anniversary Update, downloaded and installed without a hitch. Last 24 hours of testing/using also went without a hitch...Updates - Firewall issues gone - and all my accessories and options respond and are working fine...even Cortana is zipping along.
Obviously immediately saved another current Acronis image and backed that up twice to two different drives ?Wish I could report what worked...but glad I'm up and running with (so far) a new Win 10 Pro 64bit system and Anniversary update that is functioning great !!Many thanks to all that helped....TiminAz