Inaccessible Boot Device error in Windows 10

I noticed a few affected computers were setup with an image, MBR and legacy boot. Anyone else have the same setup? Just wondering if I should convert to UEFI and GPT.

Also, I had the same problem where I could only remove the package once, then it came back, removed it a second time, but still BSOD. Now I can't boot and it isn't listed either.

If your on MBR now STAY THERE. It is Much, Much more flexible.... If you don't have HDD/SDD larger the 2.2 TB don't go to GPT!

I run hybrid MBR on 2x 256 GB SSD, partitioned for OS only and 2 Data Disk of 10 TB each, I have to do GPT.

Best Regards,

Crysta

Fix the issue Crysta from the source, no need for 3rd party.

This is/seems like a baffling issue????? 

FIRST off, I not asking you to do anything active more than what you have already done!!!!

Have you tried any reputable 3rd party services that can help you look at your MBR/UFEI and Boot facility from WinRE or preferably WinPE?

• We just want to inspect this, not change anything yet.
• We also want to determine if the message "Inaccessible Boot Device error" is accurate or is it false.
• If it is accurate, then will repairing of the MBR/UFEI  and or Boot facility(BCD and Menu) work in this case.
• Do you have WinPE on a DVD/USB and/or does your 3rd party service have a CMD WinPE Prompt access

The reason that am asking like this is I have seen a variety of people say they have solved this problem in away that suggest to me that that the error message is false and that it is/maybe something else????

For example how does taking out a Patch Package correct MBR and BCD issues, but this what I have heard people say??? Especially with DISM????

Another thing is that one can make the problem significantly worse using some tools(MS) to early or at inappropriate times.

I am always very careful with CHKDSK because it will outright delete system files if it ?'thinks'? they are corrupt. I try to keep it from going below the Directory level. "CHKDSK /b /x(not necessary in WinPE)" It will tell you that there still maybe some corruption left which is because there maybe corrupt files. We will worry about them later if it becomes necessary.

I use SpinRite(available a grc.com, it is not Free but works better than anything else) on the disk, it won't delete files. In its effort to repair the disk the files may/often do become readable. At least you will have the best of both worlds, a corrected "System Volume Information" with all of its Clusters and the disk in the best state it can be in. Neither utility does both. If an SSD, don't go beyond level 2, the Writes(NOT Reads) could wear your SSD needlessly. On Level 2, it will only write if it absolutely has to, sparingly. If looks DOS era, it is BUT it works and is scheduled for a significant upgrade. All 6.x updates are free to those of use whom purchased v6.

If you can come up with some information maybe we can reason our way through this.

Best Regards,

Crysta

PS I am hesitant to recommend a 3rd party source because I am currently looking for a new one myself. Management changes can do strange things to a Company. You might look for Macrium Free offerings but I am not recommending them. The EasyBCD people are also worth looking at. I do recommend "EasyBCD", used it for years and love it, but it to early for that specifically, one needs to be logged in.

I noticed a few affected computers were setup with an image, MBR and legacy boot. Anyone else have the same setup? Just wondering if I should convert to UEFI and GPT.

Also, I had the same problem where I could only remove the package once, then it came back, removed it a second time, but still BSOD. Now I can't boot and it isn't listed either.