New
#11
I wonder why that happens. Others have had that too. I have no issues unplugging drives etc.
I wonder why that happens. Others have had that too. I have no issues unplugging drives etc.
I re-installed 10049 from image backup. It worked fine. I guess I am a glutton for punishment. Disconnected and reconnected again - same thing. would not boot, could not be repaired. Weird. Does not seem possible. Surely, I am not the only one having problems with 10049. Anyway, AM NOT DISCONNECTING AGAIN. At least anytime soon. Perhaps not the proper forum for this comment. I was rather anxious to see Spartan. Total bummer. VERY BAD! If Spartan is the only thing 10049 has to offer, others SHOULD NOT be any rush to load it. Put your Update Option on SLOW. In my most humble opinion, no need to rush. Unless you like to waste many hours.
Forgot to mention, I have practically constantly disconnected and reconnected both hard drives and SSDs for all the previous builds and have had no problems until 10049. Just does not make any sense. At least to me.
If you have an install iso image, boot to that using usb.
At the install screen hit shift+F10 for the command prompt.
Then type diskpart hit enter
Type list disk hit enter
Choose the disk that has you windows 10 installation on.
Type List Partitions hit enter
Choose the system partition, if you don't have a system partition choose you windows partition. For now will assume either is on partition one
Type select Partition 1 hit enter
Type Active hit enter
Exit
Now type bootrec /fixboot hit enter
Now type bootec /fixmbr hit enter
IF bootrec /fixboot or bootrec /fixmbr doesn't work. Then you selected the wrong partition in diskpart.
type exit
Close the installation by hitting the x and answer yes to cancel installation. Hopefully it will boot into your operating system.
If I missed a step, someone here will correct me.
Had the same issue but I really only wanted the .esd file for a clean install so it really didn't matter.
Thanks for the advice. Do not have an .iso for 10049 yet. My one and only successful 10049 update attempt did leave an install.esd for 10049. I will try and make a .iso from it. I did a pristine 10049 backup image to an SSD last night late. This I was going to use as my "working" copy. Did not one thing to it, except boot several times. No problems. Turned computer off. Turned computer on this AM. Would not boot. No repair attempt worked. I am stubborn and plan to continue working on this for awhile. Thanks to Macrium Images, I now have working copies of 10049 on two SSDs. One of my other SSDs - my "primary" SSD - still has 10041 on it and despite many tries absolutely refuses to update to 10049.