Folks, with regard to installing 17093 and/or 17101, whether it's an update or clean install, and your computer won't boot afterwards, here are some "solutions"; mine and some I found on the Feedback Hub that
might solve your issue. It seems the solutions are all over the map.
First, my solution: I just went into Settings>System>Power & Sleep> Additional Power Settings (on the right side of your screen)>Choose What the Power Buttons Do>Change Settings That are Currently Unavailable>and finally clear the checkbox on Fast Startup.
This worked for me, but doesn't seem to work for everyone.
Another solution from a member guru trying to help me privately; from the menu, right click Windows PowerShell then click Run as Administrator. When it comes up, type in the following command
Powercfg -h off. This will disable both hibernation and Fast Startup.
And now, here are the possible solutions I picked up from Feedback. I copied them exactly as they were, with no alterations on my part. I'll leave it up to those more savvy than I to figure out what the OPs meant:
1. UPDATE: I finally fixed it and now my computer boots properly.
Put Windows 10 setup USB and click repair my PC.
then go to troubleshoots and open CMD and insert
bootrec.exe /fixmbr
and shutdown completely. Then your computer should boot up properly. :)
enjoy
2. Mine Bootloop fixed: Settings > Update & Security > Troubleshoot > Hardware & Devices > Run troubleshooter. That's it.
In case you can't boot > keep pressing to start Windows in troubleshoot/safe mode by pressing F11 or F12 (don't remember which one was that) or alternatively keep pressing both from power on onwards. All menu options will fail. Take exit to windows or similar option and you are good to go. Once inside, try troubleshoot option as above.
3. I just cmd in with iso, and bootrec.exe /fixmbr
4.
This is what seams to have fixed it for me permanently:
Boot from USB Drive, startup repair (fails), reboot works fine. Than on elevated command prompt: powercfg -h off
That did fix it so far, the disable "fastboot" option did only fix it for a couple of boots, but this seams to have done the trick
--------------------
Sorry about the different fonts and sizes, but when you copy and paste, that's what you get.
I also think some were confused and got the boot loop issue confused with the no-boot issue. Your mileage may vary ...