SFC some corrupt files can not be fixed

lx07 said:

Agreed I got it and I only have Intel Graphics and the OpenCL.dll that was corrupt was signed by Microsoft. DISM with /source fixed it though.

I updated to Threshold 2 on windows 10 pro machine, 64bit v1511 (OS Build 10586.11) and only have intel graphics/network drivers. I started a thread here, but it is cold, maybe in the wrong location https://www.tenforums.com/performance...tml#post474458

While still looking for answers and something I am comfortable with trying to do, I noticed this small window(see attachment) in "Action Center"...and link is generic with no help. Could this be the source of my corrupted sfc?

I think my mentioned post of 11/21/15 explains everything
Thanks for any help

If i do clean install, will i still have SFC corrupt? I got this same thing in two Nvidia computers.

Ohwell said:

I updated to Threshold 2 on windows 10 pro machine, 64bit v1511 (OS Build 10586.11) and only have intel graphics/network drivers. I started a thread here, but it is cold, maybe in the wrong location https://www.tenforums.com/performance...tml#post474458

While still looking for answers and something I am comfortable with trying to do, I noticed this small window(see attachment) in "Action Center"...and link is generic with no help. Could this be the source of my corrupted sfc?

I think my mentioned post of 11/21/15 explains everything
Thanks for any help

That does not have anything to do with corrupted files, After installing TH2 upgrade Windows has removed some programs that it seems not to like or want installed on its OS, another program it removed was speccy too. also another one, which I can't remember at the moment. All that screen is telling you is that MS removed that program. Nothing more. Have you tried running SFC /Scannow recently?? The problems we were talking about is with Nvidia drivers and MS, which does affect SFC and the results it finds after running.

RoopeSeta said:

If i do clean install, will i still have SFC corrupt? I got this same thing in two Nvidia computers.

If you run sfc /scannow from admin command prompt it should repair your corrupt files, but it will also change ONE of your Nvidia drivers. Opencl.dll <---- from Nvidia to a MS version. Doing a clean install, will fix your corrupt files, UNTIL you upgrade your Nvidia cards with latest drivers, then same problem will appear back. I would wait for a while to see if we can find another way to fix this Nvidia driver issue with MS This is actually just a small problem right now, not worth doing a clean install unless you really want too. Like I said, I would wait a while longer before doing anything like that.

I have the Identical issue after running DISM I get this error and I did not have the issue pre-installing the Nvidia 359.00 display driver.

On my system this issue appeared only after I upgraded from 358.91. I know because i restored an image with NO corruption created on the 18th (with 358.91). ran DISM health check and got no errors. upgraded to 359.00 re-ran DISM and got the following error.

(p) CSI Payload Corrupt wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

Not sure how to classify this issue,
1) Nvidia issue
2) Microsoft issue
3 Both of the above

Ratbone said:

I have the Identical issue after running DISM I get this error and I did not have the issue pre-installing the Nvidia 359.00 display driver.

On my system this issue appeared only after I upgraded from 358.91. I know because i restored an image with NO corruption created on the 18th (with 358.91). ran DISM health check and got no errors. upgraded to 359.00 re-ran DISM and got the following error.

(p) CSI Payload Corrupt wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

Not sure how to classify this issue,
1) Nvidia issue
2) Microsoft issue
3 Both of the above

Well I am leaning on its an MS issue myself. If you want to try and fix your issue now, you could try and run sfc /scannow and it should repair your errors. Of course it will replace and in some cases remove a couple of your opencl.dll drivers from Nvidia in the process. Lately I am reading where latest updates from MS are affecting more programs besides just Nvidia, also has affected people running Norton's too, and some folks even running CCleaner. That's 3 different companies that after installing the latest updates from MS those programs can be affected. Not everyone is affected, but a lot are.

I posted this problem on the NVidia forum.

https://forums.geforce.com/default/t...-11-19-15-/16/

Let's see what feedback I'll get

Ratbone said:

I posted this problem on the NVidia forum.

https://forums.geforce.com/default/t...-11-19-15-/16/

Let's see what feedback I'll get

I have read some folks asking about that same problem on their forum yesterday, didn't see much of a response from Nvidia thou.

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