So I use my tablet (wifi) for most all my internet stuff but if it's a big job (photo edit, etc) I boot up my "big machine".
Built it about 5 yr ago but about 3 yr ago I had to upgrade the SDD I used for my OS (HDD is solely for programs, storage, etc). to a bigger SSD (those windows updates just suck up so much room it's a PITA).
Well, I go to boot up the big boy this a.m. and whoa: it won't boot. Tells me to insert os disk or change the boot order.
HUH? Never ever had this problem before. OK, easy fix . For some reason the MBR must have been corrupted. Fix it/get the good word.
Boot up-->same error message (load OS etc).
Hmmm. Maybe a bug but seeing as it worked last time and I haven't done anything since, well who knows.
Try to access my backup (offline HDD) where I store my image backup. Well, dang it no USB connections so I can't access my images.
Try windows repair disk options (there are 2-3 that may be applicable) but again, it asks for it's own files.
Go into BIOS and geez, the SSD is not even listed now. Unless someone broke into the house last night, opened the computer and stole my SSD: not likely.
Each time I try, it's only a warm boot that I do.
Well, I'm really puzzled. Go online to look at other sites while describing my issue. Do a cold boot says one.
Well, I've been doing warm boots only but hey, it's a no brainer to try.
After all, the primary fix on this SLK site is to either do a batttery reset or get a new battery.
So's I do the cold boot and damn, IT WORKED!
Moral: before trying to fix a (boot) problem the hard way (software repair, reinstall, etc). turn the damn machine OFF, wait a few minutes and try again.
MBR-master boot record
SSD--solid state drive
HHD-hard disk drive
BIOS-Basic Input/output system (resides on mobo, not part of the OS)
OS-operating system (windows, iOS, linux, etc)
warm boot-pressing the "reset" button while the computer is still running
cold boot-what you do when you start your computer by pressing the power button.
I hope you find this useful and that it saves you a few bucks down the road.
I should also mention why this happened: computers are strange beasts and something software-wise tried to run/execute a command before another command had a chance to run or complete.
Nothing you did would (normally) cause this. It's the machine's fault