Windows 10: "Errors" found by SFC/SCANNOW after clean install

Discus and support "Errors" found by SFC/SCANNOW after clean install in Windows 10 Installation and Upgrade to solve the problem; 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... Discussion in 'Windows 10 Installation and Upgrade' started by GracieAllen, Dec 2, 2015.

  1. "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.

    :)
     
    GracieAllen, Dec 2, 2015
    #1
  2. Radium3D Win User

    0xc0000454 on Reboot After Installing Windows 10 Creators Update on Laptop

    Thank you for the suggestion. I configured "clean boot" mode but I still have the restart problem. I also ran sfc /scannow and no corrupt files were found. Still have the error on reboot.
     
    Radium3D, Dec 2, 2015
    #2
  3. Error 1935 during 3rd party installation on Windows 10 64bit

    Have you found a solution yet? I installed Windows 10 as an upgrade too and then did a refresh. I've tried the above fsutil fix, without success and running "sfc /scannow" also reports no errors.
     
    DarkSensei, Dec 2, 2015
    #3
  4. jds63 Win User

    "Errors" found by SFC/SCANNOW after clean install

    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
     
    jds63, Dec 2, 2015
    #4
  5. I just installed the new drivers with the re-install. I think I'll ignore it as long as the box works!
     
    GracieAllen, Dec 3, 2015
    #5
  6. jds63 Win User
    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.
     
    jds63, Apr 4, 2018
    #6
Thema:

"Errors" found by SFC/SCANNOW after clean install

Loading...
  1. "Errors" found by SFC/SCANNOW after clean install - Similar Threads - Errors found SFC

  2. sfc /scannow found corrupt files after fresh win10 install

    in Windows 10 Performance & Maintenance
    sfc /scannow found corrupt files after fresh win10 install: I started scan with admin priv. Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs,...
  3. sfc /scannow found corrupt files after fresh win10 install

    in Windows 10 BSOD Crashes and Debugging
    sfc /scannow found corrupt files after fresh win10 install: I started scan with admin priv. Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline...
  4. sfc /scannow found uncorrectable errors....

    in Windows 10 Performance & Maintenance
    sfc /scannow found uncorrectable errors....: csfc /scannow found uncorretable errors.... Post here or a different thread? Can someone help fix or should I continue over to MS? [img] Also.... What does the 'Fresh Start' accomplish? Will this correct the errors that sfc couldn't repair?...
  5. Error in log after sfc /scannow

    in Windows 10 Performance & Maintenance
    Error in log after sfc /scannow: Maybe this is the cause of my dde server errors. I don't know how to try and fix. CSI 0000065c Error - Overlap: Duplicate ownership for directory \?? I have a few for different folders. Can some one point me in the correct direction ? 62743
  6. Problems found after running sfc /scannow

    in Windows 10 Performance & Maintenance
    Problems found after running sfc /scannow: WINDOWS\diagnostics\system\Apps" is not owned but specifies SDDL in component Microsoft-Windows-AppsDiagnostic, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} 26799
  7. sfc /scannow found errors

    in Windows 10 Performance & Maintenance
    sfc /scannow found errors: I ran "sfc /scannow" just for the heck of it and it found the following errors. CbsPersist_20150814233244.zip [img] Can anyone decipher the issue(s) it's pointing to? And perhaps know how to resolve it? 17116
  8. SFC /SCANNOW Errors After Update

    in Windows 10 Performance & Maintenance
    SFC /SCANNOW Errors After Update: I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:...
  9. 'SFC /scannow' errors on clean install

    in Windows 10 Performance & Maintenance
    'SFC /scannow' errors on clean install: I decided to run 'SFC /scannow' on my recent clean install of Windows 10 and was surprised that it reported so many errors that cannot be repaired. I installed on a 256GB Samsung Pro SSD. After trying a few recommended fixes that all failed I decided to do clean install on a...
  10. SFC /SCANNOW Error

    in Windows 10 Performance & Maintenance
    SFC /SCANNOW Error: When trying to run SFC /SCANNOW the following error is generated: C:\Windows\system32>sfc /scannow Windows Resource Protection could not start the repair service. Is this a knpown problem with solution? 20898

Users found this page by searching for:

  1. sfc scannow cant repair after clean install