1.    03 Dec 2015 #1
    Join Date : Aug 2015
    Posts : 69
    Windows 10 Professional

    "Errors" found by SFC/SCANNOW after clean install


    After attempting the 1511 upgrade (with disastrous results), I blew away the world and did a clean install of Windows 10, 1511 yesterday. It appears to be better - at least it'll boot consistently and be usable. Last evening, Windows popped up and yowled that it had a bunch of updates, so I let it install them. It MAY HAVE HAD NOTHING TO DO WITH ANYTHING, but...

    Today, I right clicked on "This PC" to display the Computer management window and nothing happened.

    SO, I ran SFC/SCANNOW and got back a LOT of errors. For example, it found
    [DIRSD OWNER WARNING] Directory [l:28 ml:29]"\??\C:\Windows\System32\Boot" is not owned but specifies SDDL in component Microsoft-Windows-BootEnvironment-Windows, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

    There are hundreds of these things are scattered throughout the thousands of lines in the log file. I have no idea if it's important, critical, annoying, or just information. Nor do I know what to do to fix any of this 'cause it appears SFC can't fix whatever's wrong.

    Here's a chunk from the very end of the log. It APPEARS to my uninformed eye, to be saying it can't fix whatever...

    Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2015-12-03 11:49:41, Info CSI 00004e98 [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
    2015-12-03 11:49:41, Info CSI 00004e99@2015/12/3:17:49:41.784 Primitive installers committed for repair
    2015-12-03 11:49:41, Info CSI 00004e9a Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2015-12-03 11:49:41, Info CSI 00004e9b [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
    2015-12-03 11:49:41, Info CSI 00004e9c [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"
    2015-12-03 11:49:41, Info CSI 00004e9d Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 0+iOy0R93IRfsv6fLhxX7z8cbJ86MO0FEF3nCS3e1X0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2015-12-03 11:49:41, Info CSI 00004e9e Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2015-12-03 11:49:41, Info CSI 00004e9f [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
    2015-12-03 11:49:41, Info CSI 00004ea0@2015/12/3:17:49:41.800 Primitive installers committed for repair
    2015-12-03 11:49:41, Info CSI 00004ea1 [SR] Repair complete


    I found another discussion elsewhere with a similar problem. They were recommended to run
    Dism /Online /Cleanup-Image /StartComponentCleanup
    Dism /Online /Cleanup-Image /RestoreHealth
    SFC /scannow

    to fix(?) the problem? I currently have these running, but WHAT is goingon? And HOW do I fix whatever's screwed up? The person in the other discussion did multiple clean installs and still had problems. If this is going to compost I'd much rather it did it now than in a day or 2 when I've got all the applications reinstalled.
      My ComputersSystem Spec
  2.    03 Dec 2015 #2
    Join Date : Jun 2015
    N.Y.
    Posts : 3,067
    Windows 10 Pro 64 bit

    Ongoing issue with NVIDIA Display drivers OpenCl.dll being detected as corrupt. It is a false positive many posts on this.I would reinstall my NVIDIA display adapter again and do not run SFC it will not cause you any issues. Most likely is a MS issue. Show you another post on this.

    Read some of the last few pages here
    SFC some corrupt files can not be fixed
      My ComputerSystem Spec
  3.    03 Dec 2015 #3
    Join Date : Aug 2015
    Posts : 69
    Windows 10 Professional
    Thread Starter

    I just installed the new drivers with the re-install. I think I'll ignore it as long as the box works!
      My ComputersSystem Spec
  4.    04 Dec 2015 #4
    Join Date : Jun 2015
    N.Y.
    Posts : 3,067
    Windows 10 Pro 64 bit

    Quote Originally Posted by GracieAllen View Post
    I just installed the new drivers with the re-install. I think I'll ignore it as long as the box works!
    Yes, but i would reinstall the drivers and do not run SFC, because if you run SFC it will replace the NVIDIA Open.cl.dll with the wrong .dll it should have, as to what caused the files to be flagged and fixed by SFC in first place. As said false positive, then everything will be fine for now.
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Will Free Windows 10 "Upgrade" work with Clean Install (CMPXCHG16b)?
I have a 2006-era Compaq PC with an AMD 64 X2 4400+ CPU (Socket 939), and it runs Windows 7 Home Premium x64 perfectly. It can even run Windows 8 x64. However, it cannot do the in-place Windows 8.1 or Windows 10 Technical Preview 64-bit...
Installation and Upgrade
Solved sfc /scannow found errors
I ran "sfc /scannow" just for the heck of it and it found the following errors. 32091 32090 Can anyone decipher the issue(s) it's pointing to? And perhaps know how to resolve it?
Performance & Maintenance
Solved "Error (0x800F081F) - DISM Unable to find source" & "sfc /scannow"
I have upgraded 5 machines and clean installed 3 machines. Experienced an issue with one machine with continuous corruption problems After the 3rd attempt I discovered that even with a Clean Install of Win 10 I get unrepairable errors - Sorry...
General Support
SFC/SCANNOW and DISM found errors, but couldnt fix them
Hello. My laptop become slower and slower every year, but seeing my father's PC running Windows 10 flawlessly with about a half of my laptop specs, I've started to wonder if i'm doing something wrong. Therefore, searching the forums, I've found ...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:50.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums