Run command prompt (Admin) Check for corruptions (DISM): Check to see if there are any corruptions with DISM. Code: DISM /Online /Cleanup-Image /checkhealth If corruptions are found and it states repairable, we can repair them. If not, go to Check/fix corruptions (SFC) Repair the corruptions (DISM): Method: 1 Enter this. Code: DISM /Online /Cleanup-Image /RestoreHealth If it's successful (no missing source or another error), go to Check/fix corruptions (SFC), otherwise, try Method 2. Method: 2 Enter this. Code: DISM /Online /Cleanup-Image /StartComponentCleanup If it's successful (no missing source or another error), go to Check/fix corruptions (SFC), otherwise, try Method 3. Method: 3 Download the required Windows 10 ISO from Microsoft https://www.microsoft.com/en-us/software-download/techbench Mount it within Windows (double-click or right-click -> mount) Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /limitaccess Change "X" to the drive letter that was assigned to the mounted ISO. "M" in my case. Check/fix corruptions (SFC): Check and repair any corruptions with SFC. Code: SFC /scannow After all this is done, you can check for corruptions again following Check for corruptions (DISM) and Check/fix corruptions (SFC) again to make sure they were repaired. This is what they should look like if everything went as planned. *Thanks to chinobino for pointing this out.
I can't fix it with the method above.. Checked sfc scannow log and its openCL.dll issue lol Checking System Update Readiness. (p) CSI Payload Corrupt wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll Repair failed: Missing replacement payload. http://www.tenforums.com/performance-maintenance/29947-sfc-some-corrupt-files-can-not-fixed-9.html Guess I'll live with it for now..
As far as I know Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /limitaccess is totally unnecessary in almost all cases and should be used only if the stuff below fails. This should be enough: Code: DISM /Online /Cleanup-Image /RestoreHealth If it gives issues then this might help: Code: DISM /Online /Cleanup-Image /StartComponentCleanup Also I would first run DISM and only then SFC because if the Windows is really corrupt the SFC can't fix it and it will just take time and possibly spam the CBS.log.
for some reason when running only DISM /Online /Cleanup-Image /RestoreHealth will result in missing source files for some people.
I have same type of error in the cbs.log with the opencl.dll driver. I read a post from the link you provided, which stated Windows uses the opencl.dll for Remote Desktop. So doing a repair will put the stripped down version of opencl.dll instead of the full feature opencl.dll provided by the Nvidia Geforce drivers? So we have to wait for MS to fix this issue with opencl.dll. My cbs.log is also full of "Error - Overlap: Duplicate ownership for directory" type errors.
It might be unnecessary but it wasn't for me. The other 2 DISM commands were needing a source that it couldn't find. The method I show is a way of forcing the source which worked when the others didn't. I'll add more methods. Thanks for your input. Yeah. I had that problem.
Microsoft need to fix the bug where Windows will return corruption errors when using SFC or DISM after installing new NVIDIA or Intel drivers as they are annoying to see. I have to run DISM using an external Image.wim file taken from the Windows ISO in order to fix every time I update either of those drivers. After that, both SFC and DISM return a clean bill of health until the next time they are updated. True, the corruption does not cause any noticeable issues such as BSODs or application crashes but I personally do not like seeing errors reported when I know there shouldn't be any. SFC and DISM worked perfectly in Windows 8/8.1, only reporting corruption when there genuinely was corruption.
Just done a fresh install and coming up with some of these errors. I mounted a fresh 1511.iso and it seems to have fixed it. Still having some weird issue with OpenCL not showing in GPU-Z and i'm not sure if it's an Nvidia problem or MS.
When I was using LTSB version of 14393, I was getting RPC errors while running dism/sfc. This would've fixed it?
Unlikely, the DISM command repairs the files needed for SFC command to repair/replace the missing/corrupted system files likely causing the RPC in the first place lol Guess an equivalent would be trying to fix a screwdriver repair machine using a broken screwdriver, need the machine to work first to fix that screwdriver, but need the screwdriver to fix the machine - catch 22 Possible it could have been done manually, but not sure how, or what the RPC error cause is My brother had the exact same problem about 3 weeks ago, had next to no UI control but could open CMD, SFC found corrupted file but couldn't fix them, DISM threw up the RPC error, ended up just reinstalling, but turned out one of his RAID0 SSDs was faulty and eventually died a couple weeks later anyway
