Windows 10: Interaction Between Bitlocker and a Virtual Hard Drive VHD in a RAID 1 Volume on Windows 10

I have a RAID 1 mirroring volume on two SSD's in my system, and I have gotten Bitlocker to encrypt this volume by setting up a virtual hard drive VHD on the volume and setting it to the size of the volume. This is a bit of a workaround because Bitlocker only works with hardware RAID configurations, where I am only able to run a software RAID configuration. Even though my VHD is in the software RAID, Windows recognizes it as a separate physical disk and allows encryption. Additionally, I am using a TPM through Intel Platform Trust Technology, though my system does not have a dedicated TPM.


I am curious as to how recovering my data will work, should the need arise; specifically:

1. If one of the SSD's fails, will the remaining drives and VHD function as normal?
2. Will the VHD and/or RAID configuration interfere with recovery in any way TPM/PIN/Recovery Key/Startup Key/Recovery Password?
3. Will migrating to a new system motherboard and CPU be affected?

I realize Bitlocker is likely not supposed to work with software RAID for these kinds of scenarios, but still seems like an arbitrary restriction on what I can do with my data.

:)

 

windows 10 bitlocker vhd connection error

Hello.

I'm using two physical hard drives encrypted with bitlocker as FDE(full disk encryption).

And I have one virtual hard drive encrypted with bitlocker in one of the two drives like below.

C:\ // bitlocker FDE, OS installed, Windows 10 Pro 1903 (64-bit)

D:\ // bitlocker FDE, for data storage

D:\my_secrets.vhd // virtual hard drive encrypted with bitlocker

And I assigned driver letter to X:\ for when the vhd file is connected.

last week, when I connected to the vhd file(my_secrets.vhd),

there are a error message with "the parameter is incorrect".

To solve this error, I looked disk management.

I could see X:\ drive file system is not NTFS but "unknown" (encrypted with bitlocker)

Then, I just removed assigned driver letter from registry and rebooted.

After rebooting, I connected the vhd file. And the connection was successful, assigned as F:\ drive letter.

But, today, the same problem is issued.

When I try to connect the vhd file, I can see same error message.

How can I solve this problem?

ps. I have copied vhd file to new one, but it's not solved after a few connections and booting.

Thanks.

 

Anniversary update & bitlocker encryted vhd drive problem

what i found about my case is almost exactly in this post:

BitLocker protected VHD volume corrupted

My case:

Drive C: encrypted with Mcafee, on this drive there is VHD file encrypted with bitlocker. After copying VHD file to drive E: and decrypting C: and then updating to Anniversary update all I can do is to mount VHD and OS ask me to format this virtual drive,
and it is seen as RAW partition. Deinstalling Anniversary update does not help.

Maciek

 

VHD to virtual PC

What does it mean? *Confused VHD is a hard drive of a virtual machine which (by default) can be opened by Microsoft Virtual PC