Windows 10: Build 10049 didn't install

Hi there. I am dualbooting Windows 7 and Windows 10 TP on a laptop. I downloaded 10049 overnight with Windows Update. When I got back to the laptop this morning, it had a brief error message saying, "Cannot install 10049 on a virtual drive". That's where Build 9926 is installed on. I rebooted, but there was no installation process going on, and it still booted into Build 9926. What can I do now? Thanks in advance for your tips or help.

:)

 

Windows 10 TPV Builds 10240-10049 Crashes Microsoft Money

Windows 10 TPV Builds 10240-10049 Crashes Microsoft Money

 

Stuck on build 10049

It will expire and then that's it. You have no choice but to upgrade to the official Windows 10 build 10240. You say you were running with Windows 7 before you installed Windows 10 build 10049? You'll have to go back to that version then go through the
free upgrade path. If you don't have sufficient disk space, you'll need to upgrade your hardware to support it.

 

There's a lot going on, at Microsoft, with the Win-10 TP updates. What seemed to work yesterday, won't necessarily work today, on the same PC.

I've seen this a lot on the several different PC's that I use for OS testing. One Laptop ran 10041 just fine but crashed while trying to run 10049. My 10 year old Desktop PC, runs XP Pro and even 8.1 pro just fine but crashes horribly on any Windows 10 TP version.

Although a lot of people seem to want to use a VM for OS testing, that's NOT the best way. No-one will ever be buying a new Windows 10 PC, with the OS running in a VM. It just ain't natural! And it's not a fair way to test any new OS.

The only way to really evaluate any new OS, is my doing a Clean Install. That can be done, (I do it) on a laptop, by backing up the main OS to a second partition and doing a clean install of the new OS to the C: partition. Then if the new OS fails, I can just do a Restore of the saved OS, back to C: and everything is back to normal again. That's a more natural way to fully evaluate a new OS.

Good Luck!
*Cool

 

Thank you, Technomage. I will go from here and reinstall on a regular partition.

 

If you are going to do a reinstall, just wait a little bit more till 10049 is officially released or get it from another trusted source.

 

Gallicbear I think some have had to upgrade to 10041 first then upgrade to 10049. Also some have had to allow more disk space and memory to the vms. Good luck to you*Biggrin

 

Did you get the ESD. If yes, you can make an iso and go from there.

 

Thanks, all. As far as doing first 10041, I can only go by what Windows Update did. It downloads updates automatically. And the virtual disk holds 50GB; it should be sufficient.

 

Link to download a ISO of 10041
http://windows.microsoft.com/en-us/w...so-update-1503

 

Thank you, Charlie. I'll work on that and report later.

 

Ok. I have copied my VHD Windows 10 installation to a regular partition. Fixed boot with EasyBCD. My new installation loaded with no problem. But it still didn't want to install 10049. Error 0x80070241. It even refused to do a sfc /scannow. Then I installed 10041 off the ISO and all is working fine now. Thanks for the link for that download, Charlie.

 

Yeah, I think it's a throwback to Win7 days. I tried installing Win7 on a VHD and it threw back the same msg "Can't instlall on a VHD"

Every update since 9926 has failed (I think I was running VMs back then, not VHD boots). Anyway, I call it a bug ... MS might claim it's a feature - (you can install and boot with a Virtual drive, but you cannot update it HA-HA-HA-HA-HA)

I've just been installing fresh from an ISO (either created or waited). I have another machine that will test the update process (Win10 installed on a separate partition). This issue actually presents a good test bed - every time a new release is dropped, I have to go through the process - new bugs appear, old bugs are fixed, lots of fun if you're a glutton for punishment *Tongue

I have fed MS the information, will they fix it? Probably not - the issue is more of a testing issue than a production issue. If people want to carry Win10 around, then Windows-to-go is a better solution than a VHD.

Bill
.

 

Thanks for sharing your experience, Slartybart.

 

Bear. According to what you have said in this post you have 10041 running. So from what we have seen your build should try to update you to 10049. It should happen tonight so we will expect good things for you in the marrow yes.