Bay Area Tech Pros

  • Home
  • Blog
  • Services
  • Testimonials
  • About
  • Contact
    • Payments
You are here: Home / Usability / Solution: Inaccessible Boot Device with Paragon HFS+

2016/03/06 By Alex 5 Comments

Solution: Inaccessible Boot Device with Paragon HFS+

I came across a challenge that prevented my Windows 10 computer from booting. The issue arose when I uninstalled Paragon HFS+ special edition and installed Paragon HFS+ trial, after reboot my computer would not start and gave the following blue screen error:

Inaccessible_Boot_Device

By referencing a number of sources I was able to reach a solution that allowed my computer to boot. In my solution I used a USB hard drive dock to mount the existing drive as a USB device which allowed me to use another windows PC to decrypt the bitlocker drive.

The solution:

You will need to delete some files and modify some registry keys. Proceed at your own risk. Make a backup of the registry hive and the files:

  • %windir%/system32/drivers/gpt_loader.sys
  • %windir%/system32/drivers/mounthlp.sys
  • %windir%/system32/drivers/hfs*.sys (search for hfs*.sys)

From the registry’s SYSTEM hive delete keys and folders pertaining to the keys listed below1.

  • apmwin
  • gpt_loader
  • csvol
  • cs_vol
  • hfsplus
  • hfsplusrec
  • mounthlp

I did this by searching through the hive for each key. A number of keys had text pertaining to other stuff, so be careful to edit the keys and delete things only pertaining to what is listed above.

Also, here’s a guide for opening a registry hive from a slave drive.

It may also be possible that just deleting the files or registry entries alone may be a fix, itself. If you get a chance try deleting just the .sys files and leave a comment whether that was successful.

Share this:

  • Reddit
  • Twitter
  • Facebook
  • Pocket
  • Email
  • Print

Filed Under: Usability Tagged With: Windows

Comments

  1. Tsz Mun says

    2017/05/18 at 4:13 AM

    where is that directory(ies) located?

    Reply
    • Alex says

      2017/07/28 at 1:09 PM

      The %windir% directory? In C:/Windows, usually. But if you type %windir% in run or explorer or anywhere it will take you right to %windir%

      Reply
  2. James says

    2017/12/19 at 6:39 AM

    Thanks for this – I broke my WIndows 10 installation after installing Paragon HFS+ to access an external HDD. Couple of mistakes:

    * The sys files are in %windir%/system32/drivers
    * It’s csvol, not cs_vol

    However, after following the guide I was still unable to boot into windows. I then discovered while screwing around in the recovery console that windows keeps a backup of the registry hives in %windir%/system32/config/RegBack. I copied the SYSTEM hive from RegBack (which was only 5 days old) over the one in config, and now I’m back in.

    Reply
    • Alex says

      2017/12/19 at 5:34 PM

      Thanks for the corrections! I wrote this from memory and made a few mistakes. Your comment will surely help others find a resolution.

      Reply
    • Mitch says

      2018/03/18 at 1:55 AM

      Thank you so much James. You’ve saved for my life. I am eternally grateful.

      Reply

Leave a Reply to Tsz Mun Cancel reply

Your email address will not be published. Required fields are marked *

Affiliate Offers

Mint Mobile
  • Host a website with DreamHost
Bay Area Tech Pros
Walnut Creek, CA 94596
(925) 302-6312
alex@bayareatechpros.com

Local IT Services in:

Available in Walnut Creek, Concord, San Ramon, Lafayette, Danville, Clayton, Alamo, Pleasant Hill & the greater Bay Area.

Check out Bay Area Tech Pros on Yelp
  • General Contact
  • Computer Services & IT Outsourcing
  • About / Information
  • Blog
  • Remote Support

Copyright © 2021 · Terms of Use & Privacy Policy · Bay Area Website Design

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.