# Solution: Inaccessible Boot Device with Paragon HFS+

- Source: https://www.bayareatechpros.com/inaccessible-boot-device-paragon-hfs/
- Content-Type: post
- Language: en-US
- Last-Modified: 2022-06-21T08:37:45+00:00

## Content

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 below[1](https://www.reddit.com/r/techsupport/comments/36ies0/inaccessible_boot_device_after_uninstalling_hfs/cubslvn).

- 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](http://www.bleepingcomputer.com/forums/t/212597/edit-registry-of-a-slave-hard-drive/#entry1185724).

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.