Rebop
Senior Member
OK. Just my pov.
It doesn't bother me a lot to install and setup my software. I don't have a huge amount. Possibly 3 or four hours for the whole kebang.. That I imo, is a little better than the time you have spent trying to sort out the problems.. The error you are encountering points to a corruption of system files. I would have thought a sfc /scannow might have been the first possible chance
SFC found nothing wrong. Run early on.
And these were all happening well before I installed any software as the first thing I do is configure options, create a custom view in events viewer, update the normal.dot with all my Word Macros, Install Outlook Stationary, etc. I do not believe it has anything to do with installed software.
Just going to run SFC again right now...
This time found some things and said to look at the log.My apologies for doubting. It is huge. Most seem related to running the test. This is the final summary after that:
2016-04-25 11:29:51, Info CSI 000052ae [SR] Verify complete
2016-04-25 11:29:51, Info CSI 000052af [SR] Repairing 1 components
2016-04-25 11:29:51, Info CSI 000052b0 [SR] Beginning Verify and Repair transaction
2016-04-25 11:29:51, Info CSI 000052b1 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 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b2 [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
2016-04-25 11:29:51, Info CSI 000052b3@2016/4/25:18:29:51.794 Primitive installers committed for repair
2016-04-25 11:29:51, Info CSI 000052b4 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 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b5 [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
2016-04-25 11:29:51, Info CSI 000052b6 [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"
2016-04-25 11:29:51, Info CSI 000052b7 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b8 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 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-04-25 11:29:51, Info CSI 000052b9 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-04-25 11:29:51, Info CSI 000052ba@2016/4/25:18:29:51.825 Primitive installers committed for repair
2016-04-25 11:29:51, Info CSI 000052bb [SR] Repair complete
2016-04-25 11:29:51, Info CSI 000052bc [SR] Committing transaction
2016-04-25 11:29:51, Info CSI 000052bd Creating NT transaction (seq 2), objectname [6]"(null)"
2016-04-25 11:29:51, Info CSI 000052be Created NT transaction (seq 2) result 0x00000000, handle @0xdb4
2016-04-25 11:29:51, Info CSI 000052bf@2016/4/25:18:29:51.841 Beginning NT transaction commit...
2016-04-25 11:29:51, Info CSI 000052c0@2016/4/25:18:29:51.856 CSI perf trace:
CSIPERF:TXCOMMIT;20005
2016-04-25 11:29:51, Info CSI 000052c1 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
What seems most interesting and seems like it was unable to repair is the opencl.dll.
Thoughts?
~Bob
Must do some real work today. Will try to get to more questions.