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

  • Please log in to reply
6 replies to this topic

#1 shar907


  • Members
  • 38 posts
  • Gender:Female
  • Location:Michigan
  • Local time:03:01 PM

Posted 14 February 2018 - 11:36 PM

I get this error message. Then it goes to Auto repair, Diagnosing your PC, restart  or advanced options. It restarts and I keep getting the same messages. I have done a System restore a few times and I still keep getting the same error message.




BC AdBot (Login to Remove)


#2 garioch7


    RCMP Veteran

  • Malware Response Instructor
  • 3,917 posts
  • Gender:Male
  • Location:Port Hood, Nova Scotia, Canada
  • Local time:03:01 PM

Posted 15 February 2018 - 05:31 AM

You currently also have a post over at Geeks-to-Go, here.
To avoid conflicting advice and helpers from multiple sites becoming involved, you should only be posting on one site about a specific issue.  Moreover, this topic properly belongs in the Windows 10 Support Forum, as it is not a discussion topic of the merits, complaints, or issues with Windows 10 in general.
Thank you for your understanding.  Have a great day.

Graduate of the Bleeping Computer Malware Removal Study Hall

#3 hamluis



  • Moderator
  • 56,552 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:01 PM

Posted 15 February 2018 - 05:57 AM

Please pursue the topic posted at Geeks-to-Go to completion.


If that does not result in a satisfactory resolution...that would be the time to initiate a new topic here at BC.


Thank you :).



#4 lwlopez1


  • Members
  • 5 posts
  • Local time:02:01 PM

Posted 19 February 2018 - 11:13 PM



Method 1:
Crash the computer a few times on purpose (This will trigger a Windows 10 Automatic Repair)
Get to the Windows Automatic Repair screen
Advanced options
Run a System Restore
Restore to a time before the crash
You may only get one shot at this
cmd (Right Click Command Prompt and Run As Administrator)
Command Prompt
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9
Press Enter (Return)

This is the same fix for INACCESSIBLE BOOT DEVICE from another newer package name Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.214.1.17 and substitute this package name for the one listed in the Method 1 above.


If you already ran a DISM to remove the package during an Windows Automatic System Repair, there have been instances that the package is no longer valid to remove and you are hosed plenty. Attempt to repeat the multiple crashes, run another system restore and then attempt an in-place upgrade or boot to a fresh Windows Media Toolkit for Windows 10 and be sure to choose the option to KEEP MY FILES AND APPS and not the KEEP MY FILES. The difference is KEEP MY FILES AND APPS is the option that keeps all of your programs installed without having to reinstall everything!


Method 2: (If Method 1 is not working)

The alternate method is to boot to the recovery and attempt to cleanup package with these settings.

Make sure you know where windows is installed (IT IS NOT C:\WINDOWS EVEN IF YOU THINK IT IS)


dir win*.* if you see c:\windows then this is the correct drive /image:c:\



dir win*.* if you see d:\windows then this is the correct drive /image:d:\



dir win*.* if you see e:\windows then this is the correct drive /image:e:\


Here is the command:

DISM /image:c:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

VERY IMPORTANT - type exit and then choose CONTINUE. Get your files backed up when you have this chance because the next reboot make take you back into this loop and you may not have this option after this.  


None of this is recommended by Microsoft for Security purposes
All of it is recommended by MILE Technologies (us) for functionality and business continuity.



#5 jenae


  • Members
  • 926 posts
  • Local time:06:01 AM

Posted 20 February 2018 - 01:39 AM

Hi lwlopez1, you have jumped into another thread with a very confusing post. Removing the right package takes quite a bit more then you describe, you need to load a registry hive and run a dism cmd to find the errant package name. Typically this will be the last one and will show status as "pending", you need to delete a registry value data for this to work.


Your method of finding the OS drive in the RE is very amateur, the cmd is:-  bcdedit |find "osdevice" this gives us the assigned drive letter.


Although if you were smart you would know that doing a registry restore using regback fixes almost all of these problems, the hard way is to find the package and remove it, alter the registry, unload the hive (having loaded it). One good thing about all the work is it usually works.


This of course is predicated on the assumption that the drive has not failed (or has bad sectors in the case of a HDD), other factors such as intel chipset driver management corruption, as well as memory or low disk space, come into play. 

#6 shar907

  • Topic Starter

  • Members
  • 38 posts
  • Gender:Female
  • Location:Michigan
  • Local time:03:01 PM

Posted 20 February 2018 - 11:02 AM

Thanks for all the help. The problem has been fixed. 



#7 JohnC_21


  • Members
  • 24,826 posts
  • Gender:Male
  • Local time:02:01 PM

Posted 20 February 2018 - 11:08 AM

Would you please post the steps you used to fix the problem. Thanks.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users