Inaccessible Boot Device error in Windows 10

I had the same issue with an i5-4750 ASRock B85M (with TPM module) machine. Since I didn't have a system backup I  had to reinstall Win 10 Pro to fix the error. I reinstalled it onto a factory new SSD since the message "inaccessible boot device" made me suspect a hardware error. Luckily I made backups during the reinstallation process because the error reoccured (on the brand new disk). I reset the machine today, using my trusty backup. I didn't encrypt the drive with Bitlocker this time though.

Did you all have Bitlocker enabled? Maybe that's the culprit with some machines? Do you use Norton Internet Security?

From the BIT I have seen and followed, a picture seems to be forming, that some of these ReBoots are destructive, in  that the more they occur the worse the PC seem to get.

The problem with saying that however, is they may not be(probably not) caused be the same thing BUT it seem that some of the various causes to ReBoot are running into a destruction state.

Now, this maybe to late for some of you(or not) but there is a significant difference between Shutdown to Cold Start and Restart/ReBoot. I have seen some mention SPECIFICALLY TO SHUTDOWN and do a Cold(after a minute or two, let the memory capacitance drain and settle) Start in between actions.

I am not vouching to the necessity of this in any specific cases or situations but it is something to keep in mind.

My old memory fails me when it comes to remembering which of you have or haven't removed Packages with DISM so that maybe playing a role in the differences as well.

Suffice it to be said, folks there is nothing monolithic in this huge conundrum that goes far and away BEYOND this community. Even Bobby has been told by MS, his problems are different "than AMD" whatever that may summarize.

There also is nothing monolithic in hardware y'all are using as well as software/apps.

There also is not a monolithic cause to the BSoD some are experiencing while others are not.....

All we can really say is allot people(no idea of %) are having one or more problems with Intel, AMD, Qualcom, Samsung, Nvidea, and/or other Silicone manufactures as well as the related Software makers/creators that program on said Silicone like Microsoft, Samsung, Intel etc.

It is easy to try to say, it is a specific Patch, well what if it is, what that Patch is interacting with, and that ??? is or is not using unsupported/undocumented connection/hooks somewhere, then what??????

Folks I am not trying to get anybody off the hook here I am just trying to say, this is nowhere near, a simple and easy set of problems. It is frustrating, aggravating and stressful to be sure. I certainly can't say, everyone that can, is doing everything they can but at the end of the day, they are our PC or PCs that we are charged to take care of by 1s, 10s, 100s, 1000s, etc. Its our problems. If we are big enough and have deep pockets we can suite or not. We certainly shouldn't be running out and buying new PCs, because they all have all of silicon problems that we have right now and will have, to some extent for years. If you have to buy?????.... Sparingly?????......

So take things methodical and slow with lots of deep breaths. This is going to stretch you. This is the School of Hard Knocks that you may have heard of..... 

Yes I know that some of you could be facing dauntless challenges in terms of 1000's of PCs, I grieve for you.... 

In general, I am just about out answers from my past foyers in the School of Hard knocks.

In specific maybe not????

If anyone wants some guidance with LOCKING down WU/MU/AU let me know, I can help there on a live system.

From WinRE or WinPE, I have never done it but the principals are the same with PS or CMDline. This maybe where you have to stretch.

You have my Prayers,

Best Regards, 

Crysta

After 3 or 4 unsuccessful boot attempts, the system should reboot into the Recovery Environment and attempt to do an Automatic Repair (which will fail). This is by design on Win10. Perhaps your system doesn't have a working RE. Boot from external media instead and use the PE to make repairs.

Hi, just to add my notes with this issue:

1. There seems to be a intentional lock after several re-boots that stops the "Inaccessible Boot Device" message and instead it re-boots, forever.
2. Using USB boot, in my case the list of updates are logged as updated (as suggested at  www.windowscentral.com/how-fix-update-causing-inaccessible-boot-device-error-windows-10).  
3. I can use the disk as non-boot on a different PC, so that's good... if I could find which files/registry entries are affected.  
4. Windows support appeared do not have a clue. 

Yep, this is insane.

Insane indeed,  I've probably heard the Motherboard "beep"  500 times in trying to get this fixed.   Just ridiculous.    

It would be nice to find the other files in the registry that are impacted.