Ok, I did a full repair using almost all options from the Tweaking.com - Windows Repair program 3.5. Maybe you could do something with the logs? I'm assuming this didn't fix my problem, but I'm now trying to do the update to the newest preview again.... let's keep fingers crossed! :)
[Windows 10 build 10525] Upgrade to build 10532 fails and corrupt files
- Thread starter mrtnptrs
- Start date
And it failed again with the same error...
zcomputerwiz
Windows Update Expert
Let's try this.
View attachment localdump.zip
Download LocalDump.zip and extract it somewhere you can easily find it.
Double click on LocalDump.reg and confirm the import.
Reboot, then try running the Windows 10 Upgrade again. When it crashes, a .dmp file should be created in C:\Temp\
Zip and attach that file with your reply.
View attachment localdump.zip
Download LocalDump.zip and extract it somewhere you can easily find it.
Double click on LocalDump.reg and confirm the import.
Reboot, then try running the Windows 10 Upgrade again. When it crashes, a .dmp file should be created in C:\Temp\
Zip and attach that file with your reply.
It gives an error about that it can't import the script, because it isn't a registerscript, Only binary files can be imported from the register-editor.
zcomputerwiz
Windows Update Expert
Ah, I see. Let's try again with this one: View attachment localdump.zip
Now the register file works, I will provide the dump tomorrow! Thanks for still wanting to help me, even when this is case is very difficult! :)
Edit: the installation went faster then I thought! :)
Sorry, it maybe was wrongly used sarcasm: the installation did fail, but now it didn't take such a long time to fail with that same error code....
zcomputerwiz
Windows Update Expert
I think you could try a repair install with the Windows 10 Media Creation Tool: Installing Windows 10 using the media creation tool - Windows Help
Give that a shot and let me know how it goes.
Give that a shot and let me know how it goes.
That one gives an error about that I can install Windows, but that I can't keep any files or programs, because Windows isn't installed in the default map, which isn't true of course!
But I found something out, when I tried to begin the complete reinstallation using the media creation tool on USB: It said: "Windows cannot be installed to this disk. The selected disk has an MBR partition table. The EFI systems, Windows can only be installed to GPT disks." Maybe that is why I can't do a repair installation or an inplace upgrade? Do you know a solution for this? Did you get any useful information from the minidump by the way? When you know no solution and also no solution for the problem that I can't keep my files and programs during re-install/upgrade, I'm now preparing for a complete re-install, copying things to my other internal HDD. So, just tell me when you see no other possibility and I will do a re-install! :)
zcomputerwiz
Windows Update Expert
I didn't get anything useful out of the minidump, I don't see any third party modules in the list other than something for the nvidia display driver. You could try uninstalling that and using the Microsoft Basic Display Device driver to see if it makes any difference.
For the UEFI/MBR error, you will have to choose the legacy boot option for the USB stick if it is offered in the boot menu.
If that option doesn't appear, try turning off UEFI/Secure Boot support in your computer's BIOS/Firmware Setup.
For the UEFI/MBR error, you will have to choose the legacy boot option for the USB stick if it is offered in the boot menu.
If that option doesn't appear, try turning off UEFI/Secure Boot support in your computer's BIOS/Firmware Setup.
I already managed to convert my disks to GPT without losing data. But I will try to de-install the Intel HD graphics driver and the Nvidia graphics driver, using DDU, and see if that helps anything....
Ok, so that all didn't help, so I installed build 10240 (clean install from USB), sfc/scannow said that no corrupt files were detected, but after the update to the latest preview (10532), it sais again that some files are corrupted and can't be repaired. And it is that OpenCL.dll file again!!!! As I am on the latest preview now, could you now be able to produce a solution for me?; something like you copying the versions of OpenCL.dll and send them to me? Could that be possible? By the way: SFCfix still crashes when trying to repair, but I Haven't seen any more issues so far.
So, this is the error output that the CBS log gives (just the same as from before the installation....):
2015-09-13 17:14:40, Info CSI 00004d9f Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10532.0_none_3de013bf566c2b11\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da0 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-13 17:14:40, Info CSI 00004da1@2015/9/13:15:14:40.082 Primitive installers committed for repair
2015-09-13 17:14:40, Info CSI 00004da2 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10532.0_none_3de013bf566c2b11\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da3 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-13 17:14:40, Info CSI 00004da4 [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10532.0.RemoteFX clientVM and UMTS files and regkeys"
2015-09-13 17:14:40, Info CSI 00004da5 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da6 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10532.0_none_3de013bf566c2b11\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da7 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2015-09-13 17:14:40, Info CSI 00004da8@2015/9/13:15:14:40.102 Primitive installers committed for repair
Maybe it's just Nvidia's and Microsoft's mistake?: https://forums.geforce.com/default/...-driver-feedback-thread/post/4639948/#4639948
Do you think that this could be important or that I can just ignore it? Maybe Nvidia has to release new drivers for the preview versions?
2015-09-13 17:14:40, Info CSI 00004d9f Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10532.0_none_3de013bf566c2b11\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da0 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-13 17:14:40, Info CSI 00004da1@2015/9/13:15:14:40.082 Primitive installers committed for repair
2015-09-13 17:14:40, Info CSI 00004da2 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10532.0_none_3de013bf566c2b11\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da3 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-13 17:14:40, Info CSI 00004da4 [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10532.0.RemoteFX clientVM and UMTS files and regkeys"
2015-09-13 17:14:40, Info CSI 00004da5 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da6 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10532.0_none_3de013bf566c2b11\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
Found: {l:32 b:g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 b:gDmFrN8verVmxgOY6cWYzieeMTVYZmsVH/5InAV4Hrw=}
2015-09-13 17:14:40, Info CSI 00004da7 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2015-09-13 17:14:40, Info CSI 00004da8@2015/9/13:15:14:40.102 Primitive installers committed for repair
Maybe it's just Nvidia's and Microsoft's mistake?: https://forums.geforce.com/default/...-driver-feedback-thread/post/4639948/#4639948
Do you think that this could be important or that I can just ignore it? Maybe Nvidia has to release new drivers for the preview versions?
zcomputerwiz
Windows Update Expert
Yes, that should be safe to ignore :)