Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:BitLocker volume header

From ReverseEngineering.wiki
Format
On this wiki Facts · Code · Notes · Topics

Recognition notes for BitLocker-encrypted NTFS volumes: the boot sector carries "-FVE-FS-" at offset 3 instead of "NTFS ", the BPB fields stay readable, and three FVE metadata blocks (each starting "-FVE-FS-") are located by offsets in the volume header.

Recognition level only; no key recovery or bypass.

Volume header (libyal libbde documentation)

The first sector (512 bytes) looks like an NTFS boot sector with these differences:

  • Windows Vista: boot entry EB 52 90, signature at offset 3 is "-FVE-FS-" (instead of "NTFS "), the 64-bit field at offset 56 is the FVE metadata block 1 cluster block number; sector signature 0x55 0xAA at 510.
  • Windows 7 and later: boot entry EB 58 90, "-FVE-FS-" at offset 3, three 64-bit FVE metadata block offsets at 176, 184 and 192 (relative to the start of the volume).
  • Unverified which Windows editions: a variant that keeps a FAT-like "MSWIN4.1" signature with the FVE metadata offsets at 440, 448 and 456 (libbde documents this variant under the same header section).

The number of sectors in the header can be 1 lower than in the partition table.

FVE metadata blocks

There are three copies. Each begins with a 64-byte block header whose signature is again "-FVE-FS-", a size field, a version (1 for Vista, 2 for Windows 7 and later), then in version 2 the encrypted volume size (bytes still encrypted), the number of volume header sectors, the three metadata block offsets and the offset of the relocated original volume header. A metadata header and an array of metadata entries follow. BitLocker decrypts from the end of the volume towards the front, so a partially converted volume reports the remaining encrypted size.

Analyst notes

  • The original boot sector content is stored (encrypted) elsewhere; the on-disk first sector is a replacement header.
  • Identify with: bytes 2D 46 56 45 2D 46 53 2D at offset 3 of a partition's first sector.

Code & repositories

  • libyal libbde documentation/ (LGPL-3.0-or-later; Unverified exact SPDX).
  • https://github.com/libyal/libbde @ dd48d476e3da4a19d7bf1c4d16d14b3b6efeddf0 · license: LGPL-3.0
    documentation/: BitLocker Drive Encryption (BDE) format description (volume header, FVE metadata blocks)
    Tested on: source read, not run: documentation read only · checked 2026-10-19; last activity 2026-10-11