So after leaving a glowing review about my new PCS computer and thinking it was all going to be sunshine and rainbows going forward, I fell asleep watching a Twitch stream today, and when I woke up for some reason my PC was in the BIOS menu.
Weird I thought.. but no problem, let's just exit back into Windows... oh wait, my M.2 boot drive apparently doesn't exist anymore according to the boot options? Exited and restarted the PC a few times and each time the red boot led on the motherboard would stay on and it would try booting from some other media (IP4, IP6) I didn't recognise, but never picked up my SSD.
Then on then 4th try instead of going back into the BIOS when it failed to boot it went onto a black screen that said "Reboot and select proper boot device". So I rebooted, forced it back into BIOS.. and there is my M.2 drive last on the boot priority but definitely being recognised again. So I shifted it back up to priority #1, restarted (still tried to boot through IP4 and 6 first, then booted correctly through the M.2 even though it was first in prio), and then it went into Windows properly.
Upon getting back into Windows, there was an update configuring for a few seconds, and now I'm back in fully. It's kinda weird and it's worried me. Can the Windows update somehow cause all this? And why did it suddenly stop and start being detected on it's own without me changing anything?
Weird I thought.. but no problem, let's just exit back into Windows... oh wait, my M.2 boot drive apparently doesn't exist anymore according to the boot options? Exited and restarted the PC a few times and each time the red boot led on the motherboard would stay on and it would try booting from some other media (IP4, IP6) I didn't recognise, but never picked up my SSD.
Then on then 4th try instead of going back into the BIOS when it failed to boot it went onto a black screen that said "Reboot and select proper boot device". So I rebooted, forced it back into BIOS.. and there is my M.2 drive last on the boot priority but definitely being recognised again. So I shifted it back up to priority #1, restarted (still tried to boot through IP4 and 6 first, then booted correctly through the M.2 even though it was first in prio), and then it went into Windows properly.
Upon getting back into Windows, there was an update configuring for a few seconds, and now I'm back in fully. It's kinda weird and it's worried me. Can the Windows update somehow cause all this? And why did it suddenly stop and start being detected on it's own without me changing anything?