Windows 10: Updating to 10041 from 9926 fails twice.

Today, I tried to update 9926 to 10014 through windows update and both times it failed. After several reboots during the installation I got a window with a message saying something like, "Couldnt' update to Windows Technical Preview -- Have restored you previous version of Windows". Of course it went back to 9926. A little note at the bottom of the window showed OxC1900101-Ox30017. Does that give anyone a hint as to what went wrong?

I will really appreciate any help in getting my system updated so I can continue getting new releases.

Thank you.

:)

 

Checking "Windows Update" process hangs without proceeding

Try this
http://pureinfotech.com/2015/03/20/fix-windows-10-build-10041-install-failure-reverted-to-build-9926/ is the only thing to work for me.

 

How to: 10 Tips before installing the latest Windows 10

I'm getting the last error mentioned, both when trying to update to 10041 and 10049 (both from 9926): "we couldn't update the system reserved partition". However, I'm not able to resize the recovery partition. No options are available in the disk management
tool. I've made sure I have some unallocated space but I can't extend the recovery partition (also, for some reason, I have two recovery partitions, one of 300MB, the other 450MB). External tools have the same problem - the option to extend those partitions
is either not available, or greyed out, depending on the tool.

Suggestions?

Thanks!

 

Try to turn your settings back to slow ring then try updating again. If you get some updates let install then restart and go back to fastring and try again

 

Ok, I did that and now have three failed attempts.

Thanks for trying.

 

10041.0.150313-1821.fbl_impressive_CLIENTPRO_RET_x64fre_en-us would not install on my machine
Failed three times with 3 different error msgs (feedback sent)

The 1st msg was "Cannot install .... on a VHD" - the others I haven't looked up yet, but the key seems to be the 1st msg.

I restarted thinking that might help, but I wasn't offereed the install option, only the download option.

I decided to download it again, this time the $Windows.~BT folder was created, so now it's ready to try again!

I'll hit the install button and see what happens.

Bill
.

 

Are you native booting the vhd? You couldn't upgrade 8 to 8.1 - you had to do clean install or update it as a VM... windows 8.1 - How to upgrade Win 8 to Win 8.1 on a VHD? - Super User - perhaps it is the same.

If that's the case you could make a ISO from the ESD. Kari has written a tutorial to do it here somewhere...

 

Hi there

I'm using VMWARE for my VM --there was absolutely no problem running the update within the VM -- installed and booted just fine.

Had other issues with 10041 but that's a different story.

Try converting your virtual machine to VMWARE format and use the latest version of VMPLAYER (free).

Cheers
jimbo

 

It was a native booting a VHD that wouldn't let you upgrade from 8 to 8.1 - not when running in a VM.

 

Yes, native boot from a VHD.

Research turned up the same solution - load the VHD in a VM and update there, then native boot from the updated VHD.
-> Might try that later or wait for the ISO.

ESDtoISO fails claiming the source is invalid or corrupt. Both downloads?
I tried the v3 version Kari wrote up and the v4 version I've successfully used before. Both fail with DISM - haven't looked more closely at the cmd file, but if I run either on Win10, the DISM version is 10041 (interesting !) and on Win8 it's 9600. There's a test in v4 to see if the version is >= 9600.

I tried creating a wim, an ISO, and a new ESD - nada!

The only things I can think of at the moment is that the encryption key changed, the DISM parms are wrong, there is some other criteria outside of decrypt (MSR part size???), or both downloads are in fact garbage.

The update to a VHD is hit or miss - some versions did not update, but at least one did (sorry, I can't recall which update(s) worked).

Thanks, I'll post what I find out - I'm fairly certain that 9926 will update in a VM, so that will be my next attempt.

Bill
.