Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vhd issue #5

Open
JiggiJag opened this issue Aug 31, 2023 · 1 comment
Open

vhd issue #5

JiggiJag opened this issue Aug 31, 2023 · 1 comment

Comments

@JiggiJag
Copy link

When using my own bitlocker VHD for the poc I recieve error status 0xC0210000/STATUS_FVE_LOCKED_VOLUME at boot. The reason is: 'The operating system couldn't be loaded because the BitLocker key required to unlock the volume wasn't loaded correcty'. I used 'manage-bde -on E:' on the vhd so that it is encrypted but there are no key protectors like with your vhd. The patch with your fve tool also seems successful. How can this be fixed? I'm using win 11 to prepare the vhd.

@Wack0
Copy link
Owner

Wack0 commented Aug 31, 2023

it probably depends on what bootmgr you're using.

old bootmgr will not support new crypto (for example win8.x bootmgr won't support any bitlocker volume crypted by aes-xts which was introduced in th2 iirc)

I'm not sure what error bootmgr returns in that case though.

Do you load bootmgr directly or through cdboot? What version of bootmgr are you using? Are you loading bootmgr from bootmgr or not?

Also please note: you cannot use a bitlocker partition image/vhd located inside a bitlocker volume directly (it may be possible to load the partition image as a ramdisk, although I haven't checked that yet). This is because the bitlocker volume open function cannot recurse at all due to how block IO device filters in the boot environment works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants