Inaccessible Boot Device error in Windows 10

WOW no doubt your an IT guy, Sam,

You hit most if not all the points, kudos!

One thing, and certainly in addition to this Community, are you aware of a hotspot for IT people dealing with Patching and WSUS, it is Patchmanagement.org they have been dealing with all sorts if these issues. I would C&P this dissertation right into an Email over there Toooo!

Susan Bradley, whom you may have seen here is a Senior Moderator there, I and others call Her(lovingly of course) The Patch Lady! She maybe able to help you if it comes to this, with Support calls/tickets etc, you will just have to ask her at the appropriate time, here or on the ORG.

Now to your Boot Manager. Have you ever heard of, or tried EasyBCD @ NeoSmart Technologies. It is excellent for building BCD/Boot Menus. I MultiBoot and use it all the time. There are a suite of tools in it. I believe Enterprises can get a trial but they do ultimately need to pay. Private Individuals do not but you need to sign up. They will send you an Email for the purposes of helping beginners and novices. I also Donate to their cause.

If it is boot issues one should be able to solve them with that and it is definitely for MBR.

I also point you to my above post, if you haven't read it......

For the future and since we don't know where some of the problems are coming from, investigate Tweaking.com

I am not sure about Enterprise arrangements but there "Registry Backup" is excellent. I have it set to backup every time I logon. Make sure it stays on VSS though. I have had so many of MS utilities in these areas fail me multiple times over the years I turn to 3rd party products. Now with MultiBoot, Restore Point isn't supported anyway. 

How much extra work do you have after Reimaging a PC? Is it worth doing a per PC Backup? OR are you doing that as well?

Have you tried CHKDSK /b /x no deeper than the Directory clusters level?(it will delete system files if it thinks they are corrupt) Have you tried SFC /scannow? DISM /Online /Cleanup-Image /RestoreHealth? (Check the helps for variations such as /offline)

In conjunction with CHKDSK, I use Gibson Research's SpinRite. No freebies here and there is a corporate/Enterprise plan(yes he has several corporate customers). If you want to see and hear Steve talk about these issues the last 2 "Security Now" episodes on TWiT.tv are available for streaming on download. I think they would be worth while for you and your management as well.

Here is my little script that I run in Powershell.exe:

ReagentC /Info

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

DISM /Online /Cleanup-Image /AnalyzeComponentStore

DISM /Online /Cleanup-Image /StartComponentCleanup

DISM /Online /Cleanup-Image /AnalyzeComponentStore

As you can see I check RE agent Control to make sure the Recovery Environment is set up properly just in case I need it, even if it is Plan D.

By the way, there are WinPE variants for above, I will have to look in my notes for them but you probably are very handy with the various helps. If you have a central Boot location on a 'System' partition, on some commands that is specified separately. As you're also probably very aware List vol in DiskPart is ones friend.

Some have wondered if Symantec is causing them more trouble than it is worth???? You might want to turn one of your problem PC into a Test PC. Problem is with these problems, so varied and persistent no 2 PCs are identical in every way necessarily......

At least your not dealing with repeat updates from WU/MU!!!!

Well Sam, I believe that covers the points you brought up, hope it helps a bit and maybe you can find out what is causing these persistent and reoccurring issues as well as BSoD.

Best Regards,

Crysta

Thanks, it fixed my problems, thank GOD!

Let us know if it stays fixed..... Please....

Other are finding that it does not?????

Best Regards,

Crysta

Thanks, it fixed my problems, thank GOD!

Let us know if it stays fixed..... Please....

Other are finding that it does not?????

Best Regards,

Crysta

Crysta,

The security updates dated 10/Jan/2018 caused the BSOD, after I removed those two updates, I was able to re-enter the system successfully without the need of re-installation of the whole system, thanks to Showster18's post.

As long as I keep those two updates from re-installing again, my Win10 will be fine, I think.

Charles

An update to my experiences with this issue:

I had a total of 4 units with the BSOD.

1. The first one brought in I attempted most of the solutions in this thread with no luck, except for the one time boot I was able to do directly after removing the installed package with dism.  Ultimately I completed a fresh Windows installation and was able to complete all available updates with no further issues encountered.
2. This time the client told me a fresh Windows install had to be a last resort and was willing to leave the unit with me longer if that would help avoid reinstall.  I decided here to restore the unit back to a point near the end of December and disable updates until a later date.  This seemed like a good solution until the client brought the unit back to me a day later with the same issue (not sure if they managed to re-enable updates or what).
3. Units three and four came in around the same time.  I quickly got into Windows on both by removing the package with dism.  I tried all the updated solutions this thread offered and few other things with no luck.  What I hadn't tried was letting Windows updates install all available updates immediately after being able to boot once after removing package.  This actually worked on the fourth unit brought in.  I went back and ran system restore on units 2 and 3 (as i had since rebooted and got BSOD) and removed the package once again.  After booting into windows on these, I completed all available updates and my next restarts went smoothly.

TLDR; Fixed this BSOD on three units by removing the package through dism, and immediately after being able to boot once, completed all available updates before restarting.