Forum Discussion
Manny Alonzo
Feb 09, 2018Copper Contributor
Problem booting after installing 17093 build
I'm experiencing problems booting after installing 17093 build on my Asus Z97 PC. It appears to have problems with the EUFI settings. It recovered with the USB recovery, but it keeps happening. TIA.
- DeletedFeb 11, 2018
I was able to boot finally after using the Windows Media Creation Tool to create new Windows 10 install usb, going into the bios and selecting to boot from usb, boot from it, and selecting Repair Windows. After fussing around with various options to repair the startup (all of which gave me errors) I reset the machine, went back into the bios, and suddenly had a second Master Boot Record to select. Booting from it worked! Thinking everything was fixed, I rebooted... and ran into the issue again. So I repeated the process and this time when I successfully booted and logged in, I went into settings and rolled back to a previous version of windows. Now everything boots fine with no reboot loops.
This whole incident has made me switch to the slow ring.
Antriksh Yadav
Feb 11, 2018Copper Contributor
I registered to post this. I spent over an hour re-seating all my PC's components because I was convinced it was a hardware failure (Gigabyte H97M-D3H motherboard was the prime suspect). As it turns out, a bootable USB stick works fine. I installed 17093 earlier today.
The motherboard logo shows up, and I can get into BIOS settings just fine. If I don't press F2 to do so, it reboots immediately, before any Windows loading spinners etc. I'll have to look into this USB recovery business now.
The motherboard logo shows up, and I can get into BIOS settings just fine. If I don't press F2 to do so, it reboots immediately, before any Windows loading spinners etc. I'll have to look into this USB recovery business now.
- DeletedFeb 11, 2018
I was able to boot finally after using the Windows Media Creation Tool to create new Windows 10 install usb, going into the bios and selecting to boot from usb, boot from it, and selecting Repair Windows. After fussing around with various options to repair the startup (all of which gave me errors) I reset the machine, went back into the bios, and suddenly had a second Master Boot Record to select. Booting from it worked! Thinking everything was fixed, I rebooted... and ran into the issue again. So I repeated the process and this time when I successfully booted and logged in, I went into settings and rolled back to a previous version of windows. Now everything boots fine with no reboot loops.
This whole incident has made me switch to the slow ring.
- Antriksh YadavFeb 11, 2018Copper Contributor
Did you mess with the boot record etc. using the command prompt at all before you got this?
Quick EDIT:
After messing with things (incl. various suggestions online about using bootrec that didn't seem to go anywhere), I set the Windows Boot Manager as top boot priority and it worked all of a sudden! The Windows USB drive recovery/repair tools also gave me various errors before this. I also tried using bootrec /rebuildbcd and a couple of other command line utilities on recommendation of some forum posts (unfortunately didn't document everything), which also didn't seem to work at the time.
I am now running 17093 with an open case and my GPU pulled out. Will try to go back to a previous version now, turn off tech preview, and hope that any rebooting during this process doesn't start looping again. I will try to keep this post updated, though I'm not sure how much help I can be to others, considering I don't know what fixed it.
EDIT 2:
I'm using a "restore to previous build" feature that I found somewhere in Windows Update. It asked me why I wish to do so, and is currently installing a mystery build (17083?). A bit obfuscated than I'd like, but sure.
Through this ordeal, I noticed that I had no system restore points. It'd be nice if Windows created these automatically before installing major preview builds.
EDIT 3:
Okay, after about 10-15 minutes of waiting, this thing rebooted into 17074. Will try shutting it down, re-installing my GPU, and getting back on the regular release channel.
EDIT 4:
Everything appears to be working normally on 17074 so far, including reboots. It seems the only way to get back to release immediately is to reinstall and restore. Because I rolled back, I hope the program won't install 17093 again. I did get the option to get on the slow channel until the next public release and stop previews thereafter.
I'm thankful for the happy ending.
- DeletedFeb 13, 2018
No, I had not messed with the boot record prior to this update! At one point in the past I had dual booted linux/windows on that box, but then I wiped it and started over with just the windows insider builds. I would love to be able to install the new build since the features sound really cool, but as it stands 17093 fubared my machine too much to trust that I can run the darn thing.
I also felt like I was drowning a bit trying things over and over until I finally got it to boot and could roll it back. I couldn't game at all Saturday when I went through this, which sucks.