- Dec 24, 2016
- 50
- 0
- 0
Last edited:
IDK! I really don't know? Maybe you need to log on to the Dell forum with your problem. I gave it my best shot! Good night my friend!
Support Forums - Dell Community
Hi friend! I have given you my best shot and I really don't have any more suggestions at this moment!:wink:Dell Support Is so sucks . , not helping me
Hi friend! I have given you my best shot and I really don't have any more suggestions at this moment!:wink:
2016-12-29 13:58:54, Info CSI 00005372 [SR] Repairing 1 components
2016-12-29 13:58:54, Info CSI 00005373 [SR] Beginning Verify and Repair transaction
2016-12-29 13:58:54, Info CSI 00005374 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 NU0UxIkpDOYfUTWGbbmS3l9h6DTGKR0INeAr+9YTGmY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-12-29 13:58:54, Info CSI 00005375 [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-12-29 13:58:54, Info CSI 00005376@2016/12/29:05:58:54.691 Primitive installers committed for repair
2016-12-29 13:58:54, Info CSI 00005377 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 NU0UxIkpDOYfUTWGbbmS3l9h6DTGKR0INeAr+9YTGmY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-12-29 13:58:54, Info CSI 00005378 [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-12-29 13:58:54, Info CSI 00005379 [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-12-29 13:58:54, Info CSI 0000537a Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 NU0UxIkpDOYfUTWGbbmS3l9h6DTGKR0INeAr+9YTGmY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-12-29 13:58:54, Info CSI 0000537b 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 NU0UxIkpDOYfUTWGbbmS3l9h6DTGKR0INeAr+9YTGmY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-12-29 13:58:54, Info CSI 0000537c [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-12-29 13:58:54, Info CSI 0000537d@2016/12/29:05:58:54.726 Primitive installers committed for repa
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
Hi friend! If you would have read my friends thread (abhishek) about tips on installing updates in my post #7; you would have saved yourself a lot of grief!
That's assuming windows files were violated and causing you problems with your updates! It sure looks like you you had some problems with your windows files. Hoping to hear good things from you!
Some times you have to slow down and smell the roses.:smile: Here's the link I'm referring to! http://forums.windowscentral.com/wi...error-codes-solutions-windows-10-upgrade.html
The following steps can resolve many Windows upgrade problems:
Remove nonessential external hardware, such as docks and USB devices.
Check all hard drives for errors and attempt repairs. To automatically repair hard drives, open an elevated command prompt, switch to the drive you wish to repair, and type the following command ' chkdsk /F '. You will be required to reboot the computer if the hard drive being repaired is also the system drive.
Attept to restore and repair system files by typing the following commands ( DISM.exe /Online /Cleanup-image /Restorehealth , sfc /scannow ) at an elevated command prompt. It may take several minutes for the command operations to be completed. For more information, see Repair a Windows Image [ https://msdn.microsoft.com/windows/h...windows-image].
Update Windows so that all available recommended updates are installed.
Uninstall non-Microsoft antivirus software.
Uninstall all nonessential software.
Update firmware and drivers.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
Verify at least 16 GB of free space is available to upgrade a 32-bit OS, or 20 GB for a 64-bit OS and 2gb atleast for Windows 10 mobile.
Hi Are you saying that you repaired your files?I don't understand! "OK let me try, no sign haha still stuck"Ok let me try . i restored successfully repaird all. haha but no sign haha still stuck .
Hi seriously! Can you not answer more then one question at a time? I also asked if all your Windows files were repaired when you ran a sfc /scannow and DISM.
You installed 8 updates successfully, then what happened? This is like pulling teeth to get answers from you. I need to know every thing you do and where you are in this upgrade. I'm really trying to help you. Sorry if I seem angry, but you don't answer all my questions and I have to ask them again. Where are you with the upgrade and what have you tried lately.
Hi Try another reset! things may have changed now, sense you don't have any system file errors. It is my understanding that a reset is supposed to install the latest updates.
I would also try another in-place repair! Some thing has to work!:grin: Have you done a chkdsk?
Have you replaced any major hardware??