Windows 10: Inaccessible Boot Drive after Update?

https://i.imgur.com/LWVkyeQ.png
Also, when i tried to do "Bootrec /Fixboot" it comes up with "access is denied"
I also did "sfc /scannow" and it came out with "Windows Resource Protection did not find any integrity violations"
Today is the 23rd Jan my computer went into Inaccessible boot device AGAIN. and i had to restore. AGAIN. my computer works fine after each restore but its really annoying how it keeps happening.
Windows Malicious Software Removal Tool January 2018 (KB890830) keeps updating each time. I have other apps that needed updating like Razer Synapse 3 and Java. As of right now, I have no idea what is causing the problem.
Also after each "inaccessible boot device" it restarts and throws me into the BIOS with this message https://media.discordapp.net/attachm...205&height=904
My Windows 10 Pro is installed on my C: Drive (Samsung 850 EVO SSD)

 

That's the most annoying part of the inaccessible boot device error, not knowing what causing it. This is a pretty good tool for restoring the boot record:

Dual-boot Repair Windows 10

A portable app, that runs in Windows. Starting up the dual boot repair tool presents a number of options:





The green text is for novice users, like me:





Worked for me, but your mileage may vary....

I did not try running this app in a recovery environment, such as WinPE, but it would probably run there as well...

 

Have you upgrade the BIOS/UEFI firmware check your motherboard manufacturer website for latest newer version of BIOS/UEFI firmware upgrade and install it if there is one.

 

Today, the inaccessible boot device came back. I have already used Dual-boot repair windows 10 that Cr00zng suggested so that seemed to be ineffective for me. I restored my PC again in order to access it and download the BIOS update I was going to install. I have updated my Gigabyte Z270X K7 BIOS from F3 to F9a (Jan 2018 version) literally 5 minutes ago. If the inaccessible boot device thing comes back, I will be sure to post.

One other thing is that the SSD i have windows installed on does not show up as a selectable option in the BIOS boot priority list. My PC can only boot to it because Windows Boot Manager has automatically selected my SSD to boot from and Windows Boot Manager itself is a selectable option. So I have selected Windows Boot Manager as the top priority.

I am not sure if this could be the problem. I have left my BIOS to boot "Legacy" mode because i have always left it that way.

 

Also, I have noticed something when I ran "systeminfo" in cmd. Does this mean anything? (picture) https://i.imgur.com/BYA7ptp.png

 

Please post screenshot of Disk Management console.

You can open the Disk Management console by typing Diskmgmt.msc into Start Menu.

 

I'm away from my PC at the moment but I remember doing this earlier today when searching up stuff. It came out with my 2 drives. SSD and HDD. 250GB and 2TB. And it also had 2 things labeled (Disk 0 partition #) I remember one was 45MB. I dont remember the other one but it was bigger and both did not have a file system.

Every drive is Healthy
I only remember this much. For the full screenshot I guess we will have to wait until tomorrow.

 

Yes please when you have time post a screenshot of the Disk Management console.

 

https://i.imgur.com/wNQ4uPS.png

 

Please re-post the image:
Disk Management - How to Post a Screenshot of General Tips Tutorials

 

https://i.imgur.com/5lMcBbn.png

 

UPDATE
My PC was just thrown into "Inaccessible Boot Device" again and this time I tried using Windows Startup Repair (expecting it to fail). It actually brought my PC back and cleared the inaccessible boot device problem.

I am still unsure whether or not this is a permanent solution but let's just continue trying to solve it anyways to be sure its fixed.

 

1) Have you backed up all files?
2) Have you made a backup image and updated the image?
3) Have you made a new restore point

4) Please run this log collector and post a zip into this thread:
log collector v2-beta08.zip

5) Please perform these tests on the drive: Either HD Tune or HD Sentinel
HD Tune: HD Tune website
a) Health (SMART)
b) Benchmark
c) Full error scan
Post images into the thread of each scan result:
Take Screenshot in Windows 10 General Tips Tutorials

or

5) Run HD Sentinel: (free or trial edition)Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
5a) click disk > surface test > post image into the thread
(this may take several hours to complete)
5b) Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 General Tips Tutorials

 

All of these were done for my SSD because that is where Windows is installed and that's the drive i want to boot to.

Health https://i.imgur.com/ddq0W0f.png
Benchmark https://i.imgur.com/LdsQCtE.png
Full error scan https://i.imgur.com/1IBRpks.png
Log Collector (tenforums) (2018-01-25 18 46).zip
1. Backup? no
2. backup image? no
3. I just made new restore point.

 

KB4056892 is the offending update, struggled with this since DEC!!!!!!
It somehow manages to wipe the reg key HKEY_LOCAL_MACHINE_SOFTWARE_MICROSOFT_WINDOWS CURRENT VERSION
which is where windows is told about the boot drive and program files.
Solution:
Boot from recovery drive
restore system image (system restore did not try it)
Kill windows update (disable) in services
Open regedit and navigate to above key. confirm all string values ProgramFilesDir etc are shown.
Open update and security and remove all WIN 10 (not office etc) updates after KB4056892.
Close and re-open regedit and re-check key for string values.
If present re-boot and all should be good. Restoring the registry will not solve the problem
Another way to check if this is the issue is to use the Media Creation tool after it downloads your only option will be full install as
"Windows is installed in an unsupported directory" in other words Windows Registry checker can't find the correct path
because the key has been deleted
Hope this helps someone, took me weeks to figure out what was happening