Microsoft-Windows-BitLocker-DrivePreparationTool

16 events across 2 channels

Event	Title	Channel	Sample
1	A problem occurred while running the BitLocker Drive Preparation Tool.	Admin	N
2	A problem occurred while running the BitLocker Drive Preparation Tool.	Admin	N
3	A problem occurred while running the BitLocker Drive Preparation Tool.	Admin	N
4	A problem occurred while running the BitLocker Drive Preparation Tool.	Admin	N
5	A problem occurred while running the BitLocker Drive Preparation Tool.	Admin	N
256	Warning Code: Warning_Code.	Admin	N
512	The BitLocker Drive Configuration Tool successfully completed.	Admin	N
4096	Found a candidate volume for shrink or merge.	Operational	N
4097	Found an unallocated extent large enough for the requested size.	Operational	N
4098	Disk extent located on the hard disk containing the System Drive.	Operational	N
4099	Command-line parameters for the BitLocker Drive Preparation Tool.	Operational	N
4100	Drive will shrink and new active drive PartitionNumber will be created.	Operational	N
4101	New drive ExtentOffset will be created from unallocated space.	Operational	N
4102	Drive will be set as the new system drive Volume Name.	Operational	N
4103	Detected Windows Recovery Environment volume Volume Path.	Operational	N
4104	A volume failed to meet the requirements for a target volume.	Operational	N

Event ID 1: A problem occurred while running the BitLocker Drive Preparation Tool.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Admin
Opcode: Initialization

Description

A problem occurred while running the BitLocker Drive Preparation Tool.

Message #

A problem occurred while running the BitLocker Drive Preparation Tool.
Error Code: %1
Error Text: %2

Fields #

Name	Description
`MessageCode` HexInt32
`MessageText` UnicodeString

Event ID 2: A problem occurred while running the BitLocker Drive Preparation Tool.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Admin
Opcode: Shrink

Description

A problem occurred while running the BitLocker Drive Preparation Tool.

Message #

A problem occurred while running the BitLocker Drive Preparation Tool.
Error Code: %1
Error Text: %2

Fields #

Name	Description
`MessageCode` HexInt32
`MessageText` UnicodeString

Event ID 3: A problem occurred while running the BitLocker Drive Preparation Tool.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Admin
Opcode: Create

Description

A problem occurred while running the BitLocker Drive Preparation Tool.

Message #

A problem occurred while running the BitLocker Drive Preparation Tool.
Error Code: %1
Error Text: %2

Fields #

Name	Description
`MessageCode` HexInt32
`MessageText` UnicodeString

Event ID 4: A problem occurred while running the BitLocker Drive Preparation Tool.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Admin
Opcode: Prepare

Description

A problem occurred while running the BitLocker Drive Preparation Tool.

Message #

A problem occurred while running the BitLocker Drive Preparation Tool.
Error Code: %1
Error Text: %2

Fields #

Name	Description
`MessageCode` HexInt32
`MessageText` UnicodeString

Event ID 5: A problem occurred while running the BitLocker Drive Preparation Tool.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Admin

Description

A problem occurred while running the BitLocker Drive Preparation Tool.

Message #

A problem occurred while running the BitLocker Drive Preparation Tool.
Error Code: %1
Error Text: %2

Fields #

Name	Description
`MessageCode` HexInt32
`MessageText` UnicodeString

Event ID 256: Warning Code: Warning_Code.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Admin

Description

Warning Code: Warning_Code.

Message #

Warning Code: %1
Warning Text: %2

Fields #

Name	Description
`MessageCode` HexInt32
`MessageText` UnicodeString

Event ID 512: The BitLocker Drive Configuration Tool successfully completed.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Admin

Description

The BitLocker Drive Configuration Tool successfully completed. The target hard disk is ready for BitLocker.

Message #

The BitLocker Drive Configuration Tool successfully completed. The target hard disk is ready for BitLocker.

Event ID 4096: Found a candidate volume for shrink or merge.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

Found a candidate volume for shrink or merge.

Message #

Found a candidate volume for shrink or merge.
Shrinkable: %1
Candidate Volume Name: %3

Fields #

Name	Description
`Shrinkable` Boolean
`ContainsWinRE` Boolean
`VolumeName` UnicodeString
`VolumeSize` UInt64
`VolumeFreeSpace` UInt64
`VolumeMaxShrinkSize` UInt64
`VolumeFlags` HexInt32
`DriveLetter` UnicodeString
`DiskNumber` UInt32
`PartitionNumber` UInt32

Event ID 4097: Found an unallocated extent large enough for the requested size.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

Found an unallocated extent large enough for the requested size.

Message #

Found an unallocated extent large enough for the requested size.
Offset: %3
Size: %4

Fields #

Name	Description
`DiskId` GUID
`Type` HexInt32
`Offset` UInt64
`Size` UInt64
`VolumeId` GUID

Event ID 4098: Disk extent located on the hard disk containing the System Drive.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

Disk extent located on the hard disk containing the System Drive.

Message #

Disk extent located on the hard disk containing the System Drive.
Offset: %3
Size: %4

Fields #

Name	Description
`DiskId` GUID
`Type` HexInt32
`Offset` UInt64
`Size` UInt64
`VolumeId` GUID

Event ID 4099: Command-line parameters for the BitLocker Drive Preparation Tool.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

Command-line parameters for the BitLocker Drive Preparation Tool.

Message #

Command-line parameters for the BitLocker Drive Preparation Tool:
   %1

Fields #

Name	Description
`RawCommandLine` UnicodeString
`ShowUsage` Boolean
`DisplayDriveInfo` Boolean
`TargetDriveLetter` UnicodeString
`TargetAction` UInt32
`NewSystemDriveLetter` UnicodeString
`ShrinkSize` Int64
`QuietMode` Boolean
`AutoRestart` Boolean

Event ID 4100: Drive will shrink and new active drive PartitionNumber will be created.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

Drive will shrink and new active drive PartitionNumber will be created.

Message #

Drive will shrink and new active drive %6 will be created. 
Volume Name: %1
Shrink Size: %5 Bytes

Fields #

Name	Description
`VolumeName` UnicodeString
`DriveLetter` UnicodeString
`DiskNumber` UInt32
`PartitionNumber` UInt32
`ShrinkSize` UInt64
`NewDriveLetter` UnicodeString

Event ID 4101: New drive ExtentOffset will be created from unallocated space.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

New drive ExtentOffset will be created from unallocated space.

Message #

New drive %3 will be created from unallocated space
Unallocated extent offset: %1
New partition size: %2 Bytes

Fields #

Name	Description
`ExtentOffset` UInt64
`NewPartitionSize` UInt64
`NewDriveLetter` UnicodeString

Event ID 4102: Drive will be set as the new system drive Volume Name.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

Drive will be set as the new system drive.

Message #

Drive will be set as the new system drive
Volume Name: %1

Fields #

Name	Description
`VolumeName` UnicodeString
`DriveLetter` UnicodeString
`DiskNumber` UInt32
`PartitionNumber` UInt32

Event ID 4103: Detected Windows Recovery Environment volume Volume Path.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

Detected Windows Recovery Environment volume.

Message #

Detected Windows Recovery Environment volume
Volume Path: %1

Fields #

Name	Description
`WinREVolumeName` UnicodeString
`DriveLetter` UnicodeString
`DiskNumber` UInt32
`PartitionNumber` UInt32

Event ID 4104: A volume failed to meet the requirements for a target volume.

Provider: Microsoft-Windows-BitLocker-DrivePreparationTool
Channel: Operational
Opcode: Initialization

Description

A volume failed to meet the requirements for a target volume.

Message #

A volume failed to meet the requirements for a target volume.
Volume Name: %3
Reason: %2

Fields #

Name	Description
`MessageCode` HexInt32
`MessageText` UnicodeString
`VolumeName` UnicodeString
`DriveLetter` UnicodeString
`DiskNumber` UInt32
`PartitionNumber` UInt32

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID 632f767e-0ec3-47b9-ba1c-a0e62a74728a

Defined in BdeHdCfgLib.dll, which carries the event manifest.

Observed on:

Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02

Downloads

Microsoft-Windows-BitLocker-DrivePreparationTool registered manifest XML (in the Win11-26200.6584 manifest pack, 2.0 MB) manifest-xml

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)