Forum Discussion
Solved
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.
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.
So wanted to add to this thread as not sure if related but definitely some buggy issues after 17093. I did note that while I had restore points saved, as I specifically manually created one before the build, they were all gone after the build. Additionally, seems to be something odd with my AMD Radeon HD7750 graphics after the build, each time I reboot the sequence/order of my monitor's changes, e.g. I have main monitor 2, in middle, then 1 and 3 on either side, after a reboot the order is 1,4,3,2. (note I do not have a 4th monitor connected currently) This happens in different orders after each reboot. To compound the issue, when I attempted to access display settings, the GUI wanted to open on the non-existent monitor, and I physically have to move one of my other monitors to the open connector to be able to see settings to then correct the display order/config. Lastly, and perhaps most odd, is I no longer see the lock screen/ login screen after a reboot. I just get blank screens, I almost thought the system was failing to load to windows when this first happened, but on a lark, I did a cntrl/alt/delete key and then entered my login credentials and up popped windows. Now this last might be related to the display bugginess and perhaps the login prompt is appearing on the non-existent monitor as well, but I can't be sure. I do have and will connect my 4th monitor to see. Sorry if this doesn't belong in this thread, but could not find where to post/report any issues after the 17093 build or area for general feedback after an insider build. Thnx
All on this thread, had to post this update thread, and will copy and paste this all to the insider feedback hub. Not sure if an update pushed/loaded last night, I will review logs. Device certainly rebooted at some point last night and while release is still 17093.rs i am now showing prelease 1802021400 - again not sure that is different as did not note further release extension prior to this morning. In any case, device rebooted over night and surprise, this morning I had login screen and my monitor array order did not change with reboot. Note, I rebooted yesterday to update for NORTON and screen configuration did change, causing me to do the whole physical change cables again routine, which is why I was so surprised to both see a login prompt and have my screens in the same configuration as I left them at end of day yesterday. In any case I seem to be all good at this point and will research if there was another update last night.
I Updated to 17101 yesterday and it's not better. I'm still having the same problem booting, I have to use the recovery USB and even the recovery process gives me an error message 0x8000ffff. The PC also shuts down by itself after some period of inactivity.
