Windows 10: Inaccessible boot device after reboot from Update

The OP already found something *Wink

 

Thanks axe0, I spent quite a bit of time last night digesting this MBR vs GPT.Here are 2 things I learned so far. I have not found any FREE utility so farthat will allow me to convert from my current portioning structure to GPTwithout losing data (not willing to do a fresh install of everything just yet,last resort). 2nd, it is my current understanding that there is noreal need to convert unless your dealing with 2 TB drives or larger, and thejury is still out on that.
If Ican find a way to convert without paying, then I will do so, the last resortwill be to do a new build, but its not off the table as an option. Here iswhere Im a bit confused, and it it may be due to my ignorance? It seems to methat to date, the current help I have received was based on an impression thatmy drive was structured as GPT, we have since learned it is not. With thatbeing said, do you still think there is a problem with my partitions under the currentfile structure? It seems to me that it is fine, but I am not experienced inthese matters, so I might me overlooking something that you are well versed in?
It justblows my mind that I can reload a fresh image and reboot it all day with noissues, it seems as though something gets updated behind the scenes when the PCis left idle for many hours and I shut it down at night and when I reboot thenext day, it comes up to the desktop and immediately states that windows needsto restart for changes to take effect, and I look in the update history beforedoing so and there was no update, then I reboot and get stuck in that BSOD loopdue to inaccessible boot device? Thanks for the help and patience,, I really needhelp!

 

The missing EFI partition is one that is causing you the trouble.

The pictures you posted earlier, are they from when you booted from an image?

 

@Fakum - Sometimes with Windows you just have to resign yourself to 'Nuke & Rebuild' *Sad

 

Yes, those screen shots are from a fresh restore from a couple of weeks ago (prior to having these problems). What I am having trouble understanding is that you are stating my problem stems from the fact that I do not have an EFI partition, I agree that I do not, but I don't have partitions structured for GPT, they are structured for MBR which do NOT have EFI partitions,,, am I correct? Thanks

 

Likely you are, but Windows can usually only boot from GPT.

When you boot your system, please visit your BIOS, check the boot mode (UEFI, Legacy etc.) and let me know what the boot mode is.

 

Sorry, axe0 this isn't true, and I currently run Win 10 with an MBR SSD.
You only really need a GPT format if your HDD/SDD is larger than 4TB. However GPT is more robust.
Use Legacy boot for MBR disks and UEFI for GPT.

 

I thought already I was wrong, but I have read enough about GPT that to make me think that.

 

ok, I will check the bootup configuration, but just to clarify, EFI partion missing is not my problem here since I am using MBR SSD,, right?

 

If I understand it all correct, that is right yes.

 

ok,,, so if its not the partition structure of my hard drive that is causing this, what else can I do? Im using the same bios profile, so I don't suspect any issue there but will confirm this evening. I don't know what to check? there must be something updating somehow that I can not pinpoint? After all, it only happens when the PC is idle for awhile, then I shut it off for the night, then the next day it boots up and tells me I need to reboot for changes to take effect,, what changes? I didn't make any,,,,

 

Check for the boot mode in the BIOS.

 

Boot mode is Legacy as expected I suppose with MBR.
Hmm,, image wont attach,, anyway the options are Legacy ROM and EFI Compatible ROM,, and its set for Legacy

 

Besides of clean installing Windows again I cannot think of another possible solution for this.

 

well... that's not good to hear, considering I started this fresh install on 9/13,, I finally finished it about a week ago, and now this,,,, OH BOY!