New
#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.
Quote