New
#191
See Solved Unable to repair Windows10 using SFC/DISM or in-place upgrade - Windows 10 Forums
for an important detail on these efforts.
See Solved Unable to repair Windows10 using SFC/DISM or in-place upgrade - Windows 10 Forums
for an important detail on these efforts.
Realized I had the exact same problem today. Microsoft support chat was useless. I followed your instructions and problem immediately solved. Thank you!!!
Thank you for posting this. It worked for me. I had to find the install.wim file, and on my computer created the mount file and uploaded the install.wim file to c: drive and reflected that in line 1, 3 and 4. Also didn't know this, but the commands on done one at a time. The 5th step also is just sfc /scannow...don't include re-run. All in all the instructions here were great and worked. There were some things I just didn't know so how to learn while doing. Thanks again for your help by posting these instructions!
Hi All,
I'm using Windows 10 Enterprise 1511 v10.10586.164 (March 2016 update) and so far the Windows SFC /SCANNOW still reports it is a problem:
Is there any way to fix this issue or just ignore it since it is false positive ?Code:2016-03-14 13:08:58, Info CSI 0001328d Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" : Found: {l:32 8qj6omMiXdZloIM27OmJd/IiV6A2rHZP9sBst8IgNZw=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2016-03-14 13:08:58, Info CSI 0001328e 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 8qj6omMiXdZloIM27OmJd/IiV6A2rHZP9sBst8IgNZw=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2016-03-14 13:08:58, Info CSI 0001328f [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
I return here because since doing this repair, (could be co-incidental!) approximately 6 weeks ago. I have lost Auto-update ability in Windows Update program. On both Windows 10 Pro 'repaired sfc' devices I have received no updates for MS Office Home & Student 2013 for the past 2 'update Tuesday'. Yet on a 10 Home device with no repair...there have been at least 8+ updates for the past 2 update Tuesday cycles for Office 2013, received automatically.
The only real updates received over the past 6 weeks for the 2 Pro devices are :
Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 etc. etc.
Cumulative Updates for Windows 10 Version 1511 for x64
Update for Windows 10 Version 1511 for x64...and that's about it.
My 'View your update History' page is very short on both Pro devices, I have spent many hours trying to establish why I am not receiving these updates....More important what other updates for 10 Pro, am I not receiving?
This problem may well not be associated with the sfc repair...Has anyone experienced this problem or can point me in the right direction to re-establish the auto update function? I have tried several 'fixes' on one device, so I can at least evaluate if one of the fixes has worked, compared to the other device...Everything was working fine up to November Threshold update...
Thank you
HI guys, new here. i am from italy
sorry i am getting mad with this error. i tried with "limit access". and did not worked. i want to try without but not sure what to write and what's the dirrence between the two commands
i'd really appreciate if you could provide help. thanks in advance
i am using a Surface pro 4 with w10 pre installed. and i just reinstalled w10 but problem still persist