| 100 | BitLocker Drive Encryption Filter Driver |
BitLocker Drive Encryption Filter Driver |
| 900 | BitLocker conversion is in progress. |
BitLocker conversion is in progress. |
| 50001 | BitLocker |
BitLocker |
| 50003 | BitLocker Drive Encryption performance counters |
BitLocker Drive Encryption performance counters |
| 50005 | Min Read Split Size |
Min Read Split Size |
| 50007 | Minimum read buffer split size in bytes during last interval |
Minimum read buffer split size in bytes during last interval |
| 50009 | Max Read Split Size |
Max Read Split Size |
| 50011 | Maximum read buffer split size in bytes during last interval |
Maximum read buffer split size in bytes during last interval |
| 50013 | Min Write Split Size |
Min Write Split Size |
| 50015 | Minimum write buffer split size in bytes during last interval |
Minimum write buffer split size in bytes during last interval |
| 50017 | Max Write Split Size |
Max Write Split Size |
| 50019 | Maximum write buffer split size in bytes during last interval |
Maximum write buffer split size in bytes during last interval |
| 50021 | Read Requests/sec |
Read Requests/sec |
| 50023 | Number of read requests received over the last second |
Number of read requests received over the last second |
| 50025 | Read Subrequests/sec |
Read Subrequests/sec |
| 50027 | Number of read subrequests issued over the last second |
Number of read subrequests issued over the last second |
| 50029 | Write Requests/sec |
Write Requests/sec |
| 50031 | Number of write requests received over the last second |
Number of write requests received over the last second |
| 50033 | Write Subrequests/sec |
Write Subrequests/sec |
| 50035 | Number of write subrequests issued over the last second |
Number of write subrequests issued over the last second |
| 0x00006001 | Encryption of volume %2 started. |
Encryption of volume %2 started. |
| 0x00006002 | Encryption of volume %2 stopped. |
Encryption of volume %2 stopped. |
| 0x00006003 | Encryption of volume %2 completed. |
Encryption of volume %2 completed. |
| 0x00006004 | Decryption of volume %2 started. |
Decryption of volume %2 started. |
| 0x00006005 | Decryption of volume %2 stopped. |
Decryption of volume %2 stopped. |
| 0x00006006 | Decryption of volume %2 completed. |
Decryption of volume %2 completed. |
| 0x00006007 | Conversion worker thread for volume %2 was started. |
Conversion worker thread for volume %2 was started. |
| 0x00006008 | Conversion worker thread for volume %2 was temporarily stopped. |
Conversion worker thread for volume %2 was temporarily stopped. |
| 0x00006009 | Auto-unlock enabled for volume %2. |
Auto-unlock enabled for volume %2. |
| 0x0000600A | An error was encountered converting volume %2. |
An error was encountered converting volume %2. |
| 0x0000600B | Auto-unlock disabled for volume %2. |
Auto-unlock disabled for volume %2. |
| 0x0000600C | The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume. |
The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume. |
| 0x0000600D | Failed to enable auto-unlock for volume %2. |
Failed to enable auto-unlock for volume %2. |
| 0x0000600E | Failed to disable auto-unlock for volume %2. |
Failed to disable auto-unlock for volume %2. |
| 0x0000600F | Auto-unlocking failed for volume %2. |
Auto-unlocking failed for volume %2. |
| 0x00006010 | An attempt to automatically restart conversion on volume %2 failed. |
An attempt to automatically restart conversion on volume %2 failed. |
| 0x00006011 | Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume. |
Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume. |
| 0x00006012 | Metadata rebuild: An attempt to write a copy of metadata on volume %2 failed and may appear as disk corruption. If failures continue, decrypt volume. |
Metadata rebuild: An attempt to write a copy of metadata on volume %2 failed and may appear as disk corruption. If failures continue, decrypt volume. |
| 0x00006013 | Volume %2 contains bad clusters. These clusters will be skipped during conversion. |
Volume %2 contains bad clusters. These clusters will be skipped during conversion. |
| 0x00006014 | No key file was found for Volume %2 during restart. |
No key file was found for Volume %2 during restart. |
| 0x00006015 | A corrupt key file was encountered for Volume %2 during restart. |
A corrupt key file was encountered for Volume %2 during restart. |
| 0x00006016 | No volume master key was retrieved in a key file during restart. |
No volume master key was retrieved in a key file during restart. |
| 0x00006017 | The TPM was not enabled during restart. |
The TPM was not enabled during restart. |
| 0x00006018 | The SRK was found to be invalid during restart. |
The SRK was found to be invalid during restart. |
| 0x00006019 | The PCRs did not match during restart. |
The PCRs did not match during restart. |
| 0x0000601A | No volume master key was retrieved from a key file during restart. |
No volume master key was retrieved from a key file during restart. |
| 0x0000601B | A boot application hash did not match expected value during restart. |
A boot application hash did not match expected value during restart. |
| 0x0000601C | The boot configuration options did not match expected values during restart. |
The boot configuration options did not match expected values during restart. |
| 0x0000601D | No volume master key was retrieved from a PIN during restart. |
No volume master key was retrieved from a PIN during restart. |
| 0x0000601E | No volume master key was retrieved from a recovery password during restart. |
No volume master key was retrieved from a recovery password during restart. |
| 0x0000601F | A valid key was found during the last restart. |
A valid key was found during the last restart. |
| 0x00006020 | An unexpected error was encountered attempting to retrieve the volume master key during restart. |
An unexpected error was encountered attempting to retrieve the volume master key during restart. |
| 0x00006021 | A key was not available from required sources during restart. |
A key was not available from required sources during restart. |
| 0x00006022 | Metadata commit: Not all copies of metadata on volume %2 could be written. If failures continue, decrypt volume. |
Metadata commit: Not all copies of metadata on volume %2 could be written. If failures continue, decrypt volume. |
| 0x00006023 | Metadata commit: No copies of metadata on volume %2 could be written. If failures continue, decrypt volume. |
Metadata commit: No copies of metadata on volume %2 could be written. If failures continue, decrypt volume. |
| 0x00006024 | Metadata commit: Metadata update could not be flushed. |
Metadata commit: Metadata update could not be flushed. |
| 0x00006025 | Metadata commit: An attempt to verify metadata update on volume %2 failed at read. If failures continue, decrypt volume. |
Metadata commit: An attempt to verify metadata update on volume %2 failed at read. If failures continue, decrypt volume. |
| 0x00006026 | Metadata commit: Update verification of metadata on volume %2 failed. If failures continue, decrypt volume. |
Metadata commit: Update verification of metadata on volume %2 failed. If failures continue, decrypt volume. |
| 0x00006027 | Metadata initial read: Primary metadata record on volume %2 could not be found. Volume needs recovery. |
Metadata initial read: Primary metadata record on volume %2 could not be found. Volume needs recovery. |
| 0x00006028 | Metadata initial read: Failover metadata record on volume %2 could not be found. Volume needs recovery. |
Metadata initial read: Failover metadata record on volume %2 could not be found. Volume needs recovery. |
| 0x00006029 | Metadata initial read: Failover metadata record on volume %2 used. If failures continue, decrypt volume. |
Metadata initial read: Failover metadata record on volume %2 used. If failures continue, decrypt volume. |
| 0x0000602A | Metadata check: Metadata record on volume %2 could not be read and has been marked for rebuild. If failures continue, decrypt volume. |
Metadata check: Metadata record on volume %2 could not be read and has been marked for rebuild. If failures continue, decrypt volume. |
| 0x0000602B | Metadata rebuild: An attempt build a new set of metadata on %2 failed at commit and may appear as disk corruption. If failures continue, decrypt volume. |
Metadata rebuild: An attempt build a new set of metadata on %2 failed at commit and may appear as disk corruption. If failures continue, decrypt volume. |
| 0x0000602C | Encrypted volume check: Volume information on %2 cannot be read. |
Encrypted volume check: Volume information on %2 cannot be read. |
| 0x0000602D | Initial state check: Rolling volume conversion transaction on %2. |
Initial state check: Rolling volume conversion transaction on %2. |
| 0x0000602E | BIOS/TCG Memory Overwrite Control: Error finding TPM driver. |
BIOS/TCG Memory Overwrite Control: Error finding TPM driver. |
| 0x0000602F | BIOS/TCG Memory Overwrite Control: Error registering TPM device interface. |
BIOS/TCG Memory Overwrite Control: Error registering TPM device interface. |
| 0x00006030 | BIOS/TCG Memory Overwrite Control: Error changing value. |
BIOS/TCG Memory Overwrite Control: Error changing value. |
| 0x00006031 | A valid BitLocker key was found during the last restart. |
A valid BitLocker key was found during the last restart. |
| 0x00006032 | The auto-unlock master key was not available from the operating system volume. Retry the operation via the BitLocker WMI interface. |
The auto-unlock master key was not available from the operating system volume. Retry the operation via the BitLocker WMI interface. |
| 0x00006033 | Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained. |
Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained. |
| 0x00006034 | The partition size specified in the partition table is smaller than the size of the file system contained by that partition. BitLocker TPM based keys cannot be used until the size of the partition calculated from the partition table is consistent with the size of the file system calculated from the bytes per sector and number of sectors fields in the boot sector. |
The partition size specified in the partition table is smaller than the size of the file system contained by that partition. BitLocker TPM based keys cannot be used until the size of the partition calculated from the partition table is consistent with the size of the file system calculated from the bytes per sector and number of sectors fields in the boot sector. |
| 0x00006035 | The system firmware failed to enable overwriting of system memory on restart. The firmware should be upgraded. |
The system firmware failed to enable overwriting of system memory on restart. The firmware should be upgraded. |
| 0x00006036 | Bootmgr failed to find a BitLocker key file for Volume %2. |
Bootmgr failed to find a BitLocker key file for Volume %2. |
| 0x00006037 | Bootmgr detected corruption in the BitLocker key file for Volume %2. |
Bootmgr detected corruption in the BitLocker key file for Volume %2. |
| 0x00006038 | Bootmgr failed to obtain the BitLocker volume master key from the key file contents. |
Bootmgr failed to obtain the BitLocker volume master key from the key file contents. |
| 0x00006039 | Bootmgr determined that the TPM is disabled. |
Bootmgr determined that the TPM is disabled. |
| 0x0000603A | Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker. |
Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker. |
| 0x0000603B | Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match. |
Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match. |
| 0x0000603C | Bootmgr failed to obtain the BitLocker volume master key from the TPM. |
Bootmgr failed to obtain the BitLocker volume master key from the TPM. |
| 0x0000603D | A boot application hash did not match the expected value during restart. |
A boot application hash did not match the expected value during restart. |
| 0x0000603E | Bootmgr failed to obtain the BitLocker volume master key from the TPM + PIN. |
Bootmgr failed to obtain the BitLocker volume master key from the TPM + PIN. |
| 0x0000603F | Bootmgr failed to obtain the BitLocker volume master key from the recovery password. |
Bootmgr failed to obtain the BitLocker volume master key from the recovery password. |
| 0x00006041 | An unexpected error was encountered attempting to retrieve the BitLocker volume master key during restart. |
An unexpected error was encountered attempting to retrieve the BitLocker volume master key during restart. |
| 0x00006042 | An internal BitLocker self-test failed for drive %2. BitLocker cannot continue encrypting data. Contact your system administrator. |
An internal BitLocker self-test failed for drive %2. BitLocker cannot continue encrypting data. Contact your system administrator. |
| 0x00006043 | Bootmgr failed to obtain the BitLocker volume master key from the TPM + enhanced PIN. |
Bootmgr failed to obtain the BitLocker volume master key from the TPM + enhanced PIN. |
| 0x00006044 | An internal BitLocker self-test failed for drive %2 when switching from raw mode to filtering mode. BitLocker cannot continue encrypting data on this drive. Contact your system administrator. |
An internal BitLocker self-test failed for drive %2 when switching from raw mode to filtering mode. BitLocker cannot continue encrypting data on this drive. Contact your system administrator. |
| 0x00006045 | Bootmgr failed to obtain the BitLocker volume master key from the network key protector. |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector. |
| 0x00006046 | Encryption of the used space on volume %2 started. |
Encryption of the used space on volume %2 started. |
| 0x00006047 | Encryption of the used space on volume %2 stopped. |
Encryption of the used space on volume %2 stopped. |
| 0x00006048 | Encryption of the used space on volume %2 completed. |
Encryption of the used space on volume %2 completed. |
| 0x00006049 | Wiping of free space on volume %2 started. |
Wiping of free space on volume %2 started. |
| 0x0000604A | Wiping of free space on volume %2 stopped. |
Wiping of free space on volume %2 stopped. |
| 0x0000604B | Wiping of free space on volume %2 completed. |
Wiping of free space on volume %2 completed. |
| 0x0000604C | A recovery password was used to start Windows.%nProtector ID: %5. |
A recovery password was used to start Windows.%nProtector ID: %5. |
| 0x0000604D | Bootmgr failed to obtain the BitLocker volume master key from the password. |
Bootmgr failed to obtain the BitLocker volume master key from the password. |
| 0x0000604E | A recovery key was used to start Windows.%nProtector ID: %5. |
A recovery key was used to start Windows.%nProtector ID: %5. |
| 0x0000604F | The BitLocker driver has started a self-healing operation on the metadata of volume %2. |
The BitLocker driver has started a self-healing operation on the metadata of volume %2. |
| 0x00006050 | The BitLocker driver has successfully completed a self-healing operation on the metadata of volume %2. |
The BitLocker driver has successfully completed a self-healing operation on the metadata of volume %2. |
| 0x00006051 | Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot was disabled. |
Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot was disabled. |
| 0x00006052 | Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot configuration changed unexpectedly. |
Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot configuration changed unexpectedly. |
| 0x00006053 | Device Lock was triggered due to too many incorrect password attempts. |
Device Lock was triggered due to too many incorrect password attempts. |
| 0x00006054 | BitLocker encryption on write started for volume %2. |
BitLocker encryption on write started for volume %2. |
| 0x00006055 | BitLocker free space sweep started for volume %2. |
BitLocker free space sweep started for volume %2. |
| 0x00006056 | BitLocker free space sweep stopped for volume %2. |
BitLocker free space sweep stopped for volume %2. |
| 0x00006057 | BitLocker free space sweep completed for volume %2. |
BitLocker free space sweep completed for volume %2. |
| 0x00006058 | BitLocker finalization sweep started for volume %2. |
BitLocker finalization sweep started for volume %2. |
| 0x00006059 | BitLocker finalization sweep paused for volume %2. |
BitLocker finalization sweep paused for volume %2. |
| 0x0000605A | BitLocker finalization sweep resumed for volume %2. |
BitLocker finalization sweep resumed for volume %2. |
| 0x0000605B | BitLocker finalization sweep completed for volume %2. |
BitLocker finalization sweep completed for volume %2. |
| 0x0000605C | BitLocker encryption on write failed for volume %2 due to disk I/O error. Check the disk for bad sectors. |
BitLocker encryption on write failed for volume %2 due to disk I/O error. Check the disk for bad sectors. |
| 0x0000605D | BitLocker finalization sweep failed for volume %2 due to disk I/O error. Check the disk for bad sectors. |
BitLocker finalization sweep failed for volume %2 due to disk I/O error. Check the disk for bad sectors. |
| 0x0000605E | Disk containing volume %2 is employing non-volatile caching software which does not support control over its caching policies. This may temporarily impact BitLocker's ability to fully secure your data. |
Disk containing volume %2 is employing non-volatile caching software which does not support control over its caching policies. This may temporarily impact BitLocker's ability to fully secure your data. |
| 0x0000605F | Disk containing volume %2 is employing non-volatile caching software which is experiencing problems. This may temporarily impact BitLocker's ability to fully secure your data. Contact disk manufacturer for an updated software. |
Disk containing volume %2 is employing non-volatile caching software which is experiencing problems. This may temporarily impact BitLocker's ability to fully secure your data. Contact disk manufacturer for an updated software. |
| 0x00006060 | Device Lock was triggered due to Device Lockout state validation failure. |
Device Lock was triggered due to Device Lockout state validation failure. |
| 0x00006061 | Drive %2 is no longer automatically managed by device encryption. |
Drive %2 is no longer automatically managed by device encryption. |
| 0x00006062 | Drive %2 is now automatically managed by device encryption. |
Drive %2 is now automatically managed by device encryption. |
| 0x00006063 | WIM hash generation paused for volume %2. |
WIM hash generation paused for volume %2. |
| 0x00006064 | WIM hash generation resumed for volume %2. |
WIM hash generation resumed for volume %2. |
| 0x00006065 | WIM hash generation completed for volume %2. |
WIM hash generation completed for volume %2. |
| 0x00006066 | WIM hash generation failed for volume %2. |
WIM hash generation failed for volume %2. |
| 0x00006067 | WIM hashes will be deleted for volume %2. |
WIM hashes will be deleted for volume %2. |
| 0x00006068 | Bootmgr failed to unseal VMK using the TPM |
Bootmgr failed to unseal VMK using the TPM |
| 0x00006069 | Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to acquire protocol handle. |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to acquire protocol handle. |
| 0x0000606A | Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to get IP address. |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to get IP address. |
| 0x0000606B | Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to create request. |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to create request. |
| 0x0000606C | Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to send request. |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to send request. |
| 0x0000606D | Bootmgr failed to obtain the BitLocker volume master key from the network key protector: invalid response. |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: invalid response. |
| 0x31000000 | Info |
Info |
| 0x31000001 | Start |
Start |
| 0x31000002 | Stop |
Stop |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0x90000001 | Microsoft-Windows-BitLocker-Driver |
Microsoft-Windows-BitLocker-Driver |
| 0x90000002 | System |
System |
| 0x91000001 | Microsoft-Windows-BitLocker-Driver-Performance |
Microsoft-Windows-BitLocker-Driver-Performance |