SFC some corrupt files can not be fixed

OldMike65 · 22 Nov 2015

Ratbone said:

what do you suggest we do, re-install 359.00 and do not run DISM and FSC until it is fixed?

Well you have a couple choices, don't do anything right now, unless you are having problems. OR run SFC / Scannow under admin command prompt and that should fix your errors. Running dism command won't do much unless you run sfc 1st.
What I did was re-installed 359 update, and left it that way for a few days, didn't run sfc and waited to find a solution, but didn't find any. So I ran sfc this morning, and it repaired the corrupt files, removed two of the Nvidia opencl drivers, and going to leave it like this for now. My display seems to be working ok right now and I have no corrupt files in Windows. I can not find any fix for this problem right now. I still think its a Microsoft issue, but unless MS gives us a NEW update, not much else can be done. Unless someone else figures out how to solve this issue.

Ratbone · 22 Nov 2015

SFC is not able to fix it I still got the same error.

This is how i fixed it:
I rolled back to the clean image (pre-359.00 update)
ran windows update.
went to the Winsxs folder
took a copy of \wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
kept the copy safe for future use when required.

SFC some corrupt files can not be fixed-opencl.dll-master.png

Installed 359.00 and ran DISM health check and got the same error as before.

took ownership of the containing folder \wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\

took a copy of the new opencl.dll and renamed it to opencl_New_NVidia.dll

SFC some corrupt files can not be fixed-opencl.dll-nvidia.png

deleted it form the folder
and replaces it with the original one.

ran DISM and No corruption detected.

I can't see any ill effects from the change so I think this could be a solution.

I will run a few games just to see if I have created any issues. I suspect not. but I will report back if I do.

Just ran a few games no difference of performance issues looks good.

Ache · 22 Nov 2015

Then run sfc /scannnow and see corruption again (fixable by sfc, i.e. Nvidia opencl.dll will be overwritten after that in your case).

Ratbone · 22 Nov 2015

just checked nothing's changed.... I've still got the Microsoft 27KB version in the folder no corruption. keeping the original does not affect the NVidia driver in any perceivable way.

I do not need to run SFC I run this instead:

DISM.exe /Online /Cleanup-image /Scanhealth

I only check for corruption first and not attempt to fix something which is not broken.

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

always run a component clean-up prior to trying to restore health

Dism.exe /online /Cleanup-Image /StartComponentCleanup

finally if there are corrupt files then you will need to mount a Win 10 Installation disk prior to running;

DISM.exe /Online /Cleanup-image /Restorehealth /Source:wim:%OSSource%:1 /limitaccess

The Variable %OSSource% (I use a batch script) is the path to the install.wim: e.g. D:\sources\install.wim

Ache · 22 Nov 2015

If WinSxS contains MS version while SysWOW64 have Nvidia version, SysWOW64 will be overwritten with MS one after sfc /scannow.
Check sizes, since WinSxS file is hardlink after sfc, not two separate files.

OldMike65 · 22 Nov 2015

Ratbone said:

just checked nothing's changed.... I've still got the Microsoft 27KB version in the folder no corruption. keeping the original does not affect the NVidia driver in any perceivable way.

Take a look at the pic's I posted on post # 106 in here. 2nd pic is what mine looked like BEFORE running sfc /scannow. 1st pic is what it looked like AFTER running sfc

Ratbone · 22 Nov 2015

OldMike65 said:

Take a look at the pic's I posted on post # 106 in here. 2nd pic is what mine looked like BEFORE running sfc /scannow. 1st pic is what it looked like AFTER running sfc

I did not have any corruption in the SYSWOW64 folder I only had an issue with

WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

we might have different problems. sfc /scannow could not fix my problem anyway.

In my case the MS version was overwritten by the NVidia 350.00 driver and sfc could not fix it

Ache · 22 Nov 2015

If you have no corruption after sfc /scannow it means Nvidia opencl.dll from SysWOW64 is damaged and not 103kb size, but 27kb.

Ratbone · 22 Nov 2015

Ache said:

If you have no corruption after sfc /scannow it means Nvidia opencl.dll from SysWOW64 is damaged and not 103kb size, but 27kb.

Nope looks fine to me:

SFC some corrupt files can not be fixed-syswow64.png

OldMike65 · 22 Nov 2015

So when you run sfc /scannow it reports no errors??? If so great job...Ratbone.

SFC some corrupt files can not be fixed

Think I fixed it.