Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


"Inaccessible boot device" and Bootrec /Fixboot and Bootrec /Rebuildbcd don't he

  • Please log in to reply
1 reply to this topic

#1 cseabrook


  • Members
  • 1 posts

Posted 09 December 2016 - 06:54 PM



The Story

I am using a Toshiba Satellite C55t-A5552 (RAM doubled, and HDD replaced once), running Windows 10 Pro (paid) Insider Preview Client 14393. It also has Office 2016 and 365 (though this not relevant).


I recently updated my drivers from the Toshiba web site, because I was having issues with a USB backup drive. Instead of just updating the USB drivers, I updated all the drivers available for my make and model. Upon restart, I got a “inaccessible boot device” blue screen. I could not boot into safe mode. From the recovery environment, I found out that all my restore points are gone, and that I could not “go back to a previous build", and the that there was no “refresh" option. The srttrail.txt log indicated a corrupt driver file for “Toshiba HDD Protection”. I removed the file and driver via command prompt (as per: https://1drv.ms/w/s!AmM_izfCs7fqgtsHTsXVhzpKzr_RMA, and https://1drv.ms/w/s!AmM_izfCs7fqgtsCDKngHoKwWgRmuw ), and gave the system a reboot. No joy.


I have renamed the bcd, and rebuilt the boot record several times. I have run offline sfc, dism, and chkdsk, many times, and the all report that they cannot find any problems.  All that has changed, is that I can no longer get into my recovery partition. I cannot do a “in place upgrade” install from a disk (I have disks for Windows 10 Pro, Insider Preview 14951, and 14956, both en-gb and us).

I can explore the drive via command prompt, and I have accessed the drive via a docking bay (“slaved” the drive). Everything seems to be in place, except for c:\boot, which I am not sure I am supposed to have. I have been working on the problem for several weeks, and I think I am going to have to look for outside advice.


Computer Details:

To start with, here are the details of the machine again:
Machine: Toshiba Satellite C55t-A5552 (RAM doubled, and HDD replaced once).
OS: Windows 10 Pro (paid) Insider Preview Client 14393.
Boot type: UEFI with a EFI (100mb, FAT32) partition.
Number of Disks: 1, Disk number 0 in Diskpart, list disk.
Number of Partitions/ Volumes: 8 (!?)

Attached File  Partitions and Volumes.gif   23.62KB   1 downloads


The Boot info, as shown by both “BCDedit”, and “BCDedit /enum /v”:


Attached File  BCDEDIT.jpg   373.38KB   0 downloads


Attached File  BCDeditenumv.jpg   559.61KB   0 downloads


Here are the copied log files from srt:


Here is an archive of everything I have been reading (and doing).


Here are the last set of commands I entered into the command prompt:


A review of the problems:
1) Cannot boot into safe mode; the BSOD message is: Inaccessible Boot Device
2) System restore points are gone, I have no “refresh” option, and I cannot go “back to a previous build”.
3) From a normal boot, I get an error code for 0x0000001; if I try to get into safe mode, I get “inaccessible boot device”.
4) When my system BSODs, it no longer takes me to the recovery partition.
5) “Bootrec.exe /ScanOs”, and “Bootrec /Rebuildbcd” find “Total identified Windows Installations: 0”, while “ver” finds the OS information.

Attached File  Scanosandver.jpg   203.03KB   0 downloads
6) I have a bunch of empty, or nearly empty, partitions that I don’t know what to make of.
7) There is no c:\boot folder. Lots of stuff I have read indicate that I should have it. I do have a c:\windows\boot\efi that does not have a bcd.


Please let me know if there is any more information that you need.


Thank you for your interest and time.

Edited by cseabrook, 09 December 2016 - 07:01 PM.

BC AdBot (Login to Remove)


#2 flactem


  • Members
  • 2 posts
  • Local time:10:14 PM

Posted 19 December 2016 - 09:50 AM

Hi Cseabrook,


I understand how you must feel...  I had lots of issues with my windows 10 pro...thankfully prior to 10 pro...  you really couldn't find any believable info to problems.....  


I didn't read all your log files and backup...  because your issue I believe is a setup problem..  


1st) the site you used and where I saw your post regarding a missing device bootup..  didn't have the complete instructions for the missing device...   I used this solutions for my windows 8.1pro last year and after 6yrs of complete failure I really didnt expect anything to work but it did.. :


the ppl at superuser take you through all the proper steps to insure you setup is correct...  plus you need to use the windows restore point config.. and system backup too....   on a regular basis so you don't have to worry bout not have a established link...  however on a side note...  if you can get to the logon splash page.. and hold you "shift key" then restart you'll be taken to the F8 repair page whereby you'll be able to use you restore info...    being unable to restore is a symptom of a missing boot device, due to not have the link to your boot-loader...  





from what I read is maybe that you info has been lost...  however, since you only have 1HDD..  I don't see how...  



I love bleepingcomputer...  so please don't get me wrong about our fine hosts....   it just that unlike 3yrs ago...  there are a myriad of great sites and info out there...    and make sure you check out the windows 10 fourms too...


we care....



Edited by flactem, 19 December 2016 - 09:58 AM.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users