| 100 | BitLocker Drive Encryption Filter Driver |
BitLocker Drive Encryption Filter Driver |
| 900 | 正在进行 BitLocker 转换。 |
BitLocker conversion is in progress. |
| 50001 | BitLocker |
BitLocker |
| 50003 | BitLocker 驱动器加密性能计数器 |
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 |
| 50009 | Max Read Split Size |
Max Read Split Size |
| 50011 | 最后一个间隔期间以字节表示的读取缓冲区最大拆分大小 |
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 |
| 50017 | Max Write Split Size |
Max Write Split Size |
| 50019 | 最后一个间隔期间以字节表示的写入缓冲区最大拆分大小 |
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 |
| 50025 | Read Subrequests/sec |
Read Subrequests/sec |
| 50027 | 最后一秒发出的读取子请求数 |
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 |
| 50033 | Write Subrequests/sec |
Write Subrequests/sec |
| 50035 | 最后一秒发出的写入子请求数 |
Number of write subrequests issued over the last second |
| 0x00006001 | 已开始加密卷 %2。 |
Encryption of volume %2 started. |
| 0x00006002 | 已停止加密卷 %2。 |
Encryption of volume %2 stopped. |
| 0x00006003 | 已完成加密卷 %2。 |
Encryption of volume %2 completed. |
| 0x00006004 | 已开始解密卷 %2。 |
Decryption of volume %2 started. |
| 0x00006007 | 开始转换卷 %2 的工作线程。 |
Conversion worker thread for volume %2 was started. |
| 0x00006008 | 暂时停止转换卷 %2 的工作线程。 |
Conversion worker thread for volume %2 was temporarily stopped. |
| 0x00006009 | 已启用卷 %2 自动解锁。 |
Auto-unlock enabled for volume %2. |
| 0x0000600A | 转换卷 %2 时出错。 |
An error was encountered converting volume %2. |
| 0x0000600B | 已禁用卷 %2 自动解锁。 |
Auto-unlock disabled for volume %2. |
| 0x0000600C | 卷 %2 上的转换操作遇到一个坏扇区错误。请验证该卷上的数据。 |
The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume. |
| 0x0000600D | 无法启用卷 %2 的自动解锁。 |
Failed to enable auto-unlock for volume %2. |
| 0x0000600E | 无法禁用卷 %2 的自动解锁。 |
Failed to disable auto-unlock for volume %2. |
| 0x0000600F | 卷 %2 的自动解锁失败。 |
Auto-unlocking failed for volume %2. |
| 0x00006010 | 试图自动重新启动卷 %2 上的转换失败。 |
An attempt to automatically restart conversion on volume %2 failed. |
| 0x00006011 | 元数据写入: 尝试修改元数据时卷 %2 返回了错误。如果继续出现错误，请解密卷。 |
Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume. |
| 0x00006012 | 元数据重建: 尝试将元数据的副本写入卷 %2 上失败，可能显示为磁盘损坏。如果继续出现错误，请解密卷。 |
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 | 卷 %2 包含无效群集。这些群集在转换过程中将被跳过。 |
Volume %2 contains bad clusters. These clusters will be skipped during conversion. |
| 0x00006014 | 重新启动时未找到卷 %2 的密钥文件。 |
No key file was found for Volume %2 during restart. |
| 0x00006015 | 重新启动时卷 %2 遇到损坏的密钥文件。 |
A corrupt key file was encountered for Volume %2 during restart. |
| 0x00006016 | 重新启动时未在密钥文件中检索到卷主密钥。 |
No volume master key was retrieved in a key file during restart. |
| 0x00006017 | 重新启动过程中没有启用 TPM。 |
The TPM was not enabled during restart. |
| 0x00006018 | 重新启动时发现 SRK 无效。 |
The SRK was found to be invalid during restart. |
| 0x00006019 | 重新启动时 PCR 不匹配。 |
The PCRs did not match during restart. |
| 0x0000601A | 重新启动时未从密钥文件中检索到卷主密钥。 |
No volume master key was retrieved from a key file during restart. |
| 0x0000601B | 重新启动过程中，启动应用程序哈希与预期的值不匹配。 |
A boot application hash did not match expected value during restart. |
| 0x0000601C | 重新启动时启动配置选项与期望值不匹配。 |
The boot configuration options did not match expected values during restart. |
| 0x0000601D | 重新启动时未从 PIN 检索到卷主密钥。 |
No volume master key was retrieved from a PIN during restart. |
| 0x0000601E | 重新启动时未从恢复密码检索到卷主密钥。 |
No volume master key was retrieved from a recovery password during restart. |
| 0x0000601F | 在上一次重新启动时找到有效密钥。 |
A valid key was found during the last restart. |
| 0x00006020 | 重新启动过程中，尝试检索卷主密钥时遇到错误。 |
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. |
| 0x00006022 | 元数据提交: 无法在卷 %2 上写入所有元数据的副本。如果继续失败，请解密卷。 |
Metadata commit: Not all copies of metadata on volume %2 could be written. If failures continue, decrypt volume. |
| 0x00006023 | 元数据提交: 无法写入卷 %2 上的元数据副本。如果继续失败，请解密卷。 |
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. |
| 0x00006025 | 元数据提交: 在尝试验证卷 %2 上的元数据更新时读取失败。如果继续失败，请解密卷。 |
Metadata commit: An attempt to verify metadata update on volume %2 failed at read. If failures continue, decrypt volume. |
| 0x00006026 | 元数据提交: 卷 %2 上的元数据更新验证失败。如果继续失败，请解密卷。 |
Metadata commit: Update verification of metadata on volume %2 failed. If failures continue, decrypt volume. |
| 0x00006027 | 元数据初始读取: 无法找到卷 %2 上的主元数据记录。需要恢复卷。 |
Metadata initial read: Primary metadata record on volume %2 could not be found. Volume needs recovery. |
| 0x00006028 | 元数据初始读取: 无法在卷 %2 上找到故障转移元数据记录。需要恢复卷。 |
Metadata initial read: Failover metadata record on volume %2 could not be found. Volume needs recovery. |
| 0x00006029 | 元数据初始读取: 使用卷 %2 上的故障转移元数据记录。如果继续失败，请解密卷。 |
Metadata initial read: Failover metadata record on volume %2 used. If failures continue, decrypt volume. |
| 0x0000602A | 元数据检查: 无法读取卷 %2 上的元数据记录并且已标记为重建。如果继续失败，请解密卷。 |
Metadata check: Metadata record on volume %2 could not be read and has been marked for rebuild. If failures continue, decrypt volume. |
| 0x0000602B | 元数据重建: 在 %2 上尝试建立新元数据集时提交失败，可能显示为磁盘损坏。如果继续失败，请解密卷。 |
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 | 加密卷检查: 无法读取 %2 上的卷信息。 |
Encrypted volume check: Volume information on %2 cannot be read. |
| 0x0000602D | 初始状态检查: 滚动 %2 上的卷转换事务。 |
Initial state check: Rolling volume conversion transaction on %2. |
| 0x0000602E | BIOS/TCG 内存覆盖控制: 查找 TPM 驱动程序时出错。 |
BIOS/TCG Memory Overwrite Control: Error finding TPM driver. |
| 0x0000602F | BIOS/TCG 内存覆盖控制: 注册 TPM 设备接口时出错。 |
BIOS/TCG Memory Overwrite Control: Error registering TPM device interface. |
| 0x00006030 | BIOS/TCG 内存覆盖控制: 更改值时出错。 |
BIOS/TCG Memory Overwrite Control: Error changing value. |
| 0x00006031 | 上次重新启动期间发现的 BitLocker 密钥有效。 |
A valid BitLocker key was found during the last restart. |
| 0x00006032 | 未从操作系统卷获取自动解锁主密钥。请通过 BitLocker WMI 接口重试操作。 |
The auto-unlock master key was not available from the operating system volume. Retry the operation via the BitLocker WMI interface. |
| 0x00006033 | 启动调试已在 Bootmgr 上启用，因此无法获取基于 TPM 的密钥。 |
Boot debugging is enabled on Bootmgr so TPM based keys cannot be obtained. |
| 0x00006034 | 分区表中指定的分区大小小于该分区中包含的文件系统的大小。除非按分区表计算的分区大小与按每扇区字节数和启动扇区中扇区字段的数量计算的文件系统大小相等，否则将不能使用基于 BitLocker TPM 的密钥。 |
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. |
| 0x00006036 | Bootmgr 未能找到卷 %2 的 BitLocker 密钥文件。 |
Bootmgr failed to find a BitLocker key file for Volume %2. |
| 0x00006037 | Bootmgr 已检测到卷 %2 的 BitLocker 密钥文件中的损坏。 |
Bootmgr detected corruption in the BitLocker key file for Volume %2. |
| 0x00006038 | Bootmgr 未能从密钥文件内容中获取 BitLocker 卷主密钥。 |
Bootmgr failed to obtain the BitLocker volume master key from the key file contents. |
| 0x00006039 | Bootmgr 已确定已禁用 TPM。 |
Bootmgr determined that the TPM is disabled. |
| 0x0000603A | Bootmgr 已确定 TPM 的 SRK 的授权数据与 BitLocker 不兼容。 |
Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker. |
| 0x0000603B | Bootmgr 未能从 TPM 获取 BitLocker 卷主密钥，原因是 PCR 不匹配。 |
Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match. |
| 0x0000603C | Bootmgr 未能从 TPM 获取 BitLocker 卷主密钥。 |
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. |
| 0x0000603E | Bootmgr 未能从 TPM + PIN 获取 BitLocker 卷主密钥。 |
Bootmgr failed to obtain the BitLocker volume master key from the TPM + PIN. |
| 0x0000603F | Bootmgr 未能从恢复密码获取 BitLocker 卷主密钥。 |
Bootmgr failed to obtain the BitLocker volume master key from the recovery password. |
| 0x00006041 | 重新启动期间尝试检索 BitLocker 卷主密钥时出现意外错误。 |
An unexpected error was encountered attempting to retrieve the BitLocker volume master key during restart. |
| 0x00006042 | 驱动器 %2 的内部 BitLocker 自我测试失败。BitLocker 无法继续加密数据。请与系统管理员联系。 |
An internal BitLocker self-test failed for drive %2. BitLocker cannot continue encrypting data. Contact your system administrator. |
| 0x00006043 | Bootmgr 无法从 TPM 和增强的 PIN 获取 BitLocker 卷主密钥。 |
Bootmgr failed to obtain the BitLocker volume master key from the TPM + enhanced PIN. |
| 0x00006044 | 从原始模式切换到筛选模式时，驱动器 %2 的内部 BitLocker 自我测试失败。BitLocker 无法继续在该驱动器上加密数据。请与系统管理员联系。 |
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 无法从网络密钥保护器获取 BitLocker 卷主密钥。 |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector. |
| 0x00006046 | 对卷 %2 上已用空间的加密已开始。 |
Encryption of the used space on volume %2 started. |
| 0x00006047 | 对卷 %2 上已用空间的加密已停止。 |
Encryption of the used space on volume %2 stopped. |
| 0x00006048 | 对卷 %2 上已用空间的加密已完成。 |
Encryption of the used space on volume %2 completed. |
| 0x00006049 | 已开始擦除卷 %2 上的可用空间。 |
Wiping of free space on volume %2 started. |
| 0x0000604A | 已停止擦除卷 %2 上的可用空间。 |
Wiping of free space on volume %2 stopped. |
| 0x0000604B | 已完成擦除卷 %2 上的可用空间。 |
Wiping of free space on volume %2 completed. |
| 0x0000604C | 恢复密码曾经用于启动 Windows。%n保护器 ID: %5。 |
A recovery password was used to start Windows.%nProtector ID: %5. |
| 0x0000604D | Bootmgr 无法从该密码获取 BitLocker 卷主密钥。 |
Bootmgr failed to obtain the BitLocker volume master key from the password. |
| 0x0000604E | 恢复密钥曾经用于启动 Windows。%n保护器 ID: %5。 |
A recovery key was used to start Windows.%nProtector ID: %5. |
| 0x0000604F | BitLocker 驱动程序已开始对卷 %2 的元数据执行自修复操作。 |
The BitLocker driver has started a self-healing operation on the metadata of volume %2. |
| 0x00006050 | BitLocker 驱动程序已成功完成对卷 %2 元数据的自修复操作。 |
The BitLocker driver has successfully completed a self-healing operation on the metadata of volume %2. |
| 0x00006051 | Bootmgr 无法从 TPM 获取 BitLocker 卷主密钥，因为已禁用安全引导。 |
Bootmgr failed to obtain the BitLocker volume master key from the TPM because Secure Boot was disabled. |
| 0x00006052 | Bootmgr 无法从 TPM 获取 BitLocker 卷主密钥，因为安全引导配置已意外更改。 |
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. |
| 0x00006054 | 已经为卷 %2 启动在写入时进行 BitLocker 加密。 |
BitLocker encryption on write started for volume %2. |
| 0x00006055 | 已经为卷 %2 启动 BitLocker 可用空间整理。 |
BitLocker free space sweep started for volume %2. |
| 0x00006056 | 已经为卷 %2 停止 BitLocker 可用空间整理。 |
BitLocker free space sweep stopped for volume %2. |
| 0x00006057 | 已经为卷 %2 完成 BitLocker 可用空间整理。 |
BitLocker free space sweep completed for volume %2. |
| 0x00006058 | 已经为卷 %2 启动 BitLocker 最终整理。 |
BitLocker finalization sweep started for volume %2. |
| 0x00006059 | 已经为卷 %2 暂停 BitLocker 最终整理。 |
BitLocker finalization sweep paused for volume %2. |
| 0x0000605A | 已经为卷 %2 恢复 BitLocker 最终整理。 |
BitLocker finalization sweep resumed for volume %2. |
| 0x0000605B | 已经为卷 %2 完成 BitLocker 最终整理。 |
BitLocker finalization sweep completed for volume %2. |
| 0x0000605C | 卷 %2 在写入时进行 BitLocker 加密失败，因为出现磁盘 I/O 错误。请检查磁盘中是否存在坏扇区。 |
BitLocker encryption on write failed for volume %2 due to disk I/O error. Check the disk for bad sectors. |
| 0x0000605D | 由于磁盘 I/O 错误，卷 %2 的 BitLocker 完成整理失败。请检查磁盘，以确定是否有损坏的扇区。 |
BitLocker finalization sweep failed for volume %2 due to disk I/O error. Check the disk for bad sectors. |
| 0x0000605E | 包含卷 %2 的磁盘正在使用非易失性缓存软件，该软件不支持对其缓存策略进行控制。这可能会暂时影响 BitLocker 充分保护你的数据的功能。 |
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 | 包含卷 %2 的磁盘正在使用的非易失性缓存软件出现问题。这可能会暂时影响 BitLocker 充分保护你的数据的功能。请与磁盘制造商联系以获取更新的软件。 |
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. |
| 0x00006061 | 驱动器 %2 不再由设备加密自动管理。 |
Drive %2 is no longer automatically managed by device encryption. |
| 0x00006062 | 现在，驱动器 %2 由设备加密自动管理。 |
Drive %2 is now automatically managed by device encryption. |
| 0x00006063 | 已为卷 %2 暂停 WIM 哈希生成。 |
WIM hash generation paused for volume %2. |
| 0x00006064 | 已为卷 %2 恢复 WIM 哈希生成。 |
WIM hash generation resumed for volume %2. |
| 0x00006065 | 已为卷 %2 完成 WIM 哈希生成。 |
WIM hash generation completed for volume %2. |
| 0x00006066 | 卷 %2 的 WIM 哈希生成失败。 |
WIM hash generation failed for volume %2. |
| 0x00006067 | 将为卷 %2 删除 WIM 哈希。 |
WIM hashes will be deleted for volume %2. |
| 0x00006068 | Bootmgr 无法使用 TPM 解封 VMK |
Bootmgr failed to unseal VMK using the TPM |
| 0x00006069 | Bootmgr 无法从网络密钥保护器获取 BitLocker 卷主密钥: 无法获取协议图柄。 |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to acquire protocol handle. |
| 0x0000606A | Bootmgr 无法从网络密钥保护器获取 BitLocker 卷主密钥: 无法获取 IP 地址。 |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to get IP address. |
| 0x0000606B | Bootmgr 无法从网络密钥保护器获取 BitLocker 卷主密钥: 无法创建请求。 |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to create request. |
| 0x0000606C | Bootmgr 无法从网络密钥保护器获取 BitLocker 卷主密钥: 无法发送请求。 |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: failed to send request. |
| 0x0000606D | Bootmgr 无法从网络密钥保护器获取 BitLocker 卷主密钥: 无效响应。 |
Bootmgr failed to obtain the BitLocker volume master key from the network key protector: invalid response. |
| 0x31000000 | 信息 |
Info |
| 0x31000001 | 开始 |
Start |
| 0x31000002 | 停止 |
Stop |
| 0x50000002 | 错误 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x90000001 | Microsoft-Windows-BitLocker-Driver |
Microsoft-Windows-BitLocker-Driver |
| 0x90000002 | System |
System |
| 0x91000001 | Microsoft-Windows-BitLocker-Driver-Performance |
Microsoft-Windows-BitLocker-Driver-Performance |