Inaccessible Boot Device error in Windows 10

Hello,

   Has anyone seen threads comparable to this one that deal with users that only

developed this problem within the last week (since Tuesday). My machine handled the January

updates without any problem. I blue screened the first time Tuesday. My get-packages look like

(from the bottom):

Installed       Version                Type                       State

  2/14     16299.248.1.17        RollupFix               Pending

  2/2       16299.214.1.17        RollupFix               Pending

  2/1       16299.192.1.9          RollupFix              Superseeded

  12/14   16299.125.1.6          RollupFix              Superseeded

  2/14     16299.245.1.0          KB4087256            Installed

  2/1       16299.212.1.0          KB4074608            Installed

  2/9       10.0.1.0                    KB4074595            Installed

  2/1       16299.188.1.0          KB4058702            Installed

  1/13     10.0.1.0                    KB4058043            Installed

  plus several others on 1/13, all installed.

I've tried using remove-package(c:), but it fails with 800f082f, but I was not in RE(e:)

While trying to recover from the BSOD I remember last weekend just prior the error I had problems trying to back up my files using Seagate.  I would start the Seagate Dashboard and start the backup and within a minute or so, it would halt with a "unable to connect to the drive".  I updated the Dashboard, but still the same problem.  I could run Chkdsk with no problems and access the files on the USB backup drive. There was also plenty of space available on it to do backups.  

I was able to recover the system by using a system restore 2/2/2018 (another Critical update).  I checked everything out and everything appeared to work fine.  I had the wireless connect off, so I went in and paused updating for a month.

Before rebooting, I ran the Seagate Dashboard again using the same USB drive, and it worked as expected backing up all of my files.  I rebooted, plugged in the USB wireless connection and everything worked fine. I did not apply any updates, so hopefully it will continue to run for awhile.

I will be trying this later on today with my wife's system.  It is a Z270/Windows 10 64bit Pro build so it isn't like it is an old system.

It started doing it in January and each time it did it, I was able to get it going again by going back to the 1/18/2018 restore point that was shown as "Installer Module" or something to that end.  Since then, every week it does the automatic update and we end up with this same "Inaccessible Boot Device" BSOD.  If I go in and have it go back to the 1/18 restore point all is fine and it works for a week but each time it does the automatic update that gets listed as "Critical Update", the same BSOD.

This week though, when it did it, the 1/18 restore point dropped off the list and the only options I have are "Critical Update" ones and it refuses to do anything but BSOD.

Due to a lot of the issues she had on her previous system she has kept this one clean and has nothing more than what it installed with, Firefox, no Java or anything, Norton 360 AV, Malware Bytes, a couple adblockers and World of Warcraft.  That is pretty much the extent of it.   So it isn't like she is picking up a ton of malware or anything and that is causing the problem.

My next solution was to simply try and do a full re-install from the original DVD but I have not had that opportunity yet.

I tried the dism fix on two different computers. It did not work on either one. I never got Windows to boot after successfully removing the packages.

I removed all packages that had "amd64" in their titles, including the "permanent" package KB4054022. No luck. I gave up and reset the computers which was a HUGE project that required hours of reinstalling programs and getting them reconfigured to work in my office.