Error creating recovery disk

[Grimmric]

I bought the SP4 and the first thing I try to do is do a backup of win 10.
You get no media and no serial as i could find so i tried to create a recovery drive on a usb.
I format it to FAT32 and start the creation.
But after about an hour (60% of status bar) it just terminates with an error.
No error code or nothing.
Just a box telling me that it didnt work.
Has anybody else tried this?

 

[boltman2013]

I bought the SP4 and the first thing I try to do is do a backup of win 10.
You get no media and no serial as i could find so i tried to create a recovery drive on a usb.
I format it to FAT32 and start the creation.
But after about an hour (60% of status bar) it just terminates with an error.
No error code or nothing.
Just a box telling me that it didnt work.
Has anybody else tried this?

I returned my first one mainly because I could not get that to work either. Now it works fine every time on my new one.
I did not want to get stuck without the ability to create recovery media.out

Even did a recovery in the Microsoft store on the old one... when it was ready Camera would not launch and same issue with recover disk creation...peace out at that point. Replace.

 

[Grimmric]

That is not good.
I am not really interested to return it as it works very good and i am happy with it. Except this problem.
Is it any difference to do a recovery disk from the SP4 or to get the recovery disk from microsoft homepage?

 

[boltman2013]

That is not good.
I am not really interested to return it as it works very good and i am happy with it. Except this problem.
Is it any difference to do a recovery disk from the SP4 or to get the recovery disk from microsoft homepage?

Yes.... I prefer the one you create as it is more tailored to your device. I know how you feel about exchange (it mostly work..justifying) but chances are there are more than just the recovery disk error that will creep up. In my case it was a non working camera after refresh. So I'd return it .

Pretty sure the built in recovery image is corrupt or possibly the hardware in both of our cases.

Think about it ..... EVERYTHING should work.

 

[Grimmric]

Yes.... I prefer the one you create as it is more tailored to your device. I know how you feel about exchange (it mostly work..justifying) but chances are there are more than just the recovery disk error that will creep up. In my case it was a non working camera after refresh. So I'd return it .

Pretty sure the built in recovery image is corrupt or possibly the hardware in both of our cases.

Think about it ..... EVERYTHING should work.

I totally agree.
I have now done a scan with "sfc /scannow" and it has found a corruption.
Could the below corruption be a problem?

--------------------------------------------------
2015-12-03 13:19:53, Info CSI 0000a926 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 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a927 [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 13:19:53, Info CSI 0000a928@2015/12/3:12:19:53.306 Primitive installers committed for repair
2015-12-03 13:19:53, Info CSI 0000a929 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 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a92a [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 13:19:53, Info CSI 0000a92b [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 13:19:53, Info CSI 0000a92c Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a92d 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 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a92e [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

 

[boltman2013]

I totally agree.
I have now done a scan with "sfc /scannow" and it has found a corruption.
Could the below corruption be a problem?

--------------------------------------------------
2015-12-03 13:19:53, Info CSI 0000a926 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 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a927 [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 13:19:53, Info CSI 0000a928@2015/12/3:12:19:53.306 Primitive installers committed for repair
2015-12-03 13:19:53, Info CSI 0000a929 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 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a92a [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 13:19:53, Info CSI 0000a92b [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 13:19:53, Info CSI 0000a92c Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a92d 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 2C7ATVnEllNPqjHq7wICPosHNZh7tBeiFb+/Czl5xY0=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-03 13:19:53, Info CSI 0000a92e [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

Could be ...just return it and test all functions in the new unit. Do a recovery disk after initial updates and store in safe place.

 

[GatsbyGlen]

I totally agree.
I have now done a scan with "sfc /scannow" and it has found a corruption.
Could the below corruption be a problem?

I think you can safely ignore opencl.dll ...

 

[Grimmric]

I have been looking on the web for this answer and i have seen alot of people with this problem.
I have tried alot of the solutions but so far no luck.
Until today. With the new patch downloaded and installed it finally created a recovery device without any errors.
I am a happy camper right now as that was the only problem i had.
Was thinking alot of returning it, but everything worked so good.
Now i just wait for MS to fix the battery time. For now its no problem for me, but it would be nice with some more hours of battery life when the summer hits.
Thank you all for answers an suggestions.