大网数据广告活动
账户与安全

BitLocker Recovery starts when OEMs perform firmware updates for TPM 1.2

· 52CE 我爱测

Provides a workaround for the issue where BitLocker Recovery starts when OEMs perform firmware updates for TPM 1.2.

This article provides a workaround for the issue where BitLocker Recovery starts when OEMs perform firmware updates for TPM 1.2.

Applies to:   Windows 10 - all editions
Original KB number:   3184518

Symptoms

For Trusted Platform Module (TPM) 1.2, Windows does not know if the system is going through a firmware update. In this situation, the computer reboots into BitLocker Recovery.

Manage-bde: protectors

To suspend protection, run the following command line:

manage-bde -protectors -disable c:

To resume protection, run the following command line:

manage-bde -protectors -enable c: 

Workaround

For IT managers who are performing firmware updates for TPM 1.2 through Windows Update, make sure that you suspend BitLocker before you run the updates. This prevents BitLocker Recovery from starting.

More Information

Use TPM 2.0, as PCR 7 performs all these measurements automatically.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Client · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。