Windows 10: Inaccessible boot device after reboot from Update

Got exactly the same issue after updating on the fast ring last night - only solution was a complete rebuild. Even a ful reset of the PC deleting everything including files did not fix the issue and i ended up having to reinstall completely and reformat drives. I guess the fast ring is a dangerous place to play! i have gone back to the RTM version and will be staying away from insider builds from now on. At least on my main PC.

 

Sorry to hear that,,, please enlighten me though as some of the terms you used are unfamiliar to me.
Fast Ring?
RTM Version? Sorry, what version are you referring too?
Inside Builders?

I was using Windows 7 Ultimate before I did the upgrade to Win 10 Pro, had a snag and went with the fresh install option, which led me to my current status.

 

In the Windows 10 Insider Preview there are 2 rings, the fast and slow.
Those in the fast are getting frequently updates for the insider preview, the slow ring users slower as it speaks.
The Insiders help improve Windows 10 by sending bugs and suggestions to Microsoft for stabilizing Windows 10 for the next RTM.

The RTM version is the stable version of Windows 10, currently version 10240.

The reason why I cannot find a possible solution is because I never had helped someone who had this problem with MBR instead of GPT. So I don't really know what way I need to go and how to do it.
I will ask the team if someone might know a way out of this.

EDIT: totally forgot about my plan.
Please boot in the troubleshooting options, these options are available when you reboot a few times but are unable to boot normally.
In the troubleshooting options, go to the advanced options, there is the command prompt available.
In the command prompt, enter following commands
Code: bootrec /RebuildBcd bootrec /fixMbr bootrec /fixboot Exit[/quote] You should be able to reboot, but sometimes you need to run an additional extra command
Code: bootsect /nt60 SYS or bootsect /nt60 ALL[/quote] (the "or" part of course not)
Try to reboot and see what happens.

 

Thanks for the feedback, the terms are clearer now. I will try your suggestion when I get stuck in that loop again,, odd thing is, this is the 2nd morning in a row where I have NOT experienced that mystery update that required a restart that ultimately caused that looping BSOD. I was restoring to the exact same image file daily, so no changes have been made unless they occurred without my knowledge? I will do a manual windows update today and see what happens,,, thanks

 

Update: Did a manual update, it updates 2 of the exact same security updates and a GPU update. Unable to hide either one of them for the future, and the GPU update is not on the list to be able to uninstall? Regardless, I rebooted a couple of time and shut down once and at this moment, I am not experiencing any issues? Leave a sleeping dog lay I say at this moment I suppose,,,
Attachment 44356
Attachment 44357
Attachment 44358

 

I again sincerely hope it stays this way *Smile

 

Amen!*092
I will report back in a few days if nothing pops sooner,, if it does, I will do those command prompts and report back, otherwise, it will be a new install again with the exception I will use the GPT file structure,,,

 

*Thumbs

Keep us posted *Smile

 

So far, so good! No idea of course why everything is seemingly fine now, but it is,,,,I hope I don't have to come back to this thread, but I sure do appreciate the help!