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

Windows 10 BitLocked volume fails to unlock - "volume header size in FVE Volume header block does not match number of volume header sectors." #52

Open
arcticforensics opened this issue Nov 6, 2020 · 5 comments
Assignees

Comments

@arcticforensics
Copy link

bdemount 20200724 fails to mount BitLocker volume created by Windows 10 (version 1903). Error "volume header size in FVE Volume header block does not match number of volume header sectors." (calculated volume header size = 0). See attached log.

log.txt

@joachimmetz
Copy link
Member

@brucemarkey must have missed this earlier, thx for the report

looks like the bytes per sector value in the volume header is 0

libbde_io_handle_read_volume_header: signature                          : -FVE-FS-
libbde_io_handle_read_volume_header: bytes per sector                   : 0
libbde_io_handle_read_volume_header: sectors per cluster block          : 0
libbde_io_handle_read_volume_header: unknown1
00000000: 00 00 00 00 00                                     .....

@joachimmetz
Copy link
Member

One option is to fall back to 512 if the bytes per sector is set to 0

@joachimmetz
Copy link
Member

the question is why would it be set to 0, a BDE image created with https://github.com/dfirlabs/bde-specimens on Windows 10 20H2

libbde_io_handle_read_volume_header: signature                          : -FVE-FS-
libbde_io_handle_read_volume_header: bytes per sector                   : 512
libbde_io_handle_read_volume_header: sectors per cluster block          : 8
libbde_io_handle_read_volume_header: unknown1
00000000: 00 00 00 00 00                                     .....

@joachimmetz
Copy link
Member

joachimmetz commented Dec 8, 2020

@brucemarkey could you indicate to me how it was created, with manage-bde?

@arcticforensics
Copy link
Author

It was created using the Windows GUI (Manage BitLocker). But I can't repeat the issue since upgrading to Windows 10's October 2020 update (20H2). It appears that only Windows 10's May 2020 update (20H1) is responsible.

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

No branches or pull requests

2 participants