{"id":106468,"date":"2022-04-12T07:00:00","date_gmt":"2022-04-12T14:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=106468"},"modified":"2022-04-13T07:14:01","modified_gmt":"2022-04-13T14:14:01","slug":"20220412-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20220412-00\/?p=106468","title":{"rendered":"Notes on BitLocker and the TPM and the pre-boot password or PIN"},"content":{"rendered":"

I had an older system that had BitLocker configured with a pre-boot password because it didn’t have a Trusted Platform Module (TPM). I later discovered that the system did indeed have a TPM, but it was disabled by default, which is why BitLocker couldn’t find it.<\/p>\n

Here’s how I converted the system from a pre-boot password to TPM-managed protection.<\/p>\n

Step 1: Enable the TPM chip in the BIOS.<\/p>\n

This will vary from manufacturer to manufacturer. The tricky part is that some BIOS menus don’t refer to the TPM as a TPM. They call it an “Embedded Security Device” or a “Security Chip”. You want to Enable the TPM \/ Embedded Security Device.<\/p>\n

You also want to enable OS Management of Embedded Security Device<\/i> if you have that option.<\/p>\n

This web site walks you through the BIOS of many major manufacturers<\/a>.<\/p>\n

Step 2: Let Windows take control of the TPM.<\/p>\n

From an elevated command prompt, type tpm.msc<\/code> to run the TPM console snap-in. Over on the right-hand side, there will be an option called “Prepare TPM for use”. If prompted, reboot the system back into the BIOS, so that the BIOS can verify that you really want to let Windows use the TPM.<\/p>\n

After convincing the BIOS to let Windows manage the TPM, you can switch over to letting the TPM manage your BitLocker volume.<\/p>\n

Step 3: Enable TPM management of BitLocker.<\/p>\n

From an elevated command prompt:<\/p>\n

manage-bde -protectors -add C: -tpm\r\n<\/pre>\n
This tells BitLocker to allow the TPM to protect access to the volume.<\/p>\n
Doing this might regenerate the recovery key, so do a<\/p>\n
manage-bde -protectors -get C:\r\n<\/pre>\n
to get the new Numerical Password. The ID is a bunch of letters, digits, and dashes inside curly braces. This lets you remember which volume the password is for. The password is the sequence of six-digit blocks separated by dashes. Save both the ID and password in a safe place.<\/p>\n
Step 4: Remove the old password.<\/p>\n
manage-bde -protectors -delete C: -t Password\r\n<\/pre>\n
This last step is what stymied me. I had set up the TPM to unlock the volume, but I still kept getting prompted for the password. That’s because the password protector was still there, and the system insisted on using it.<\/p>\n
Delete the password protector, leaving just the TPM protector. That lets the TPM take over as the source of unlocking the system volume at boot.<\/p>\n
As an extra check, run<\/p>\n
manage-bde -protectors -get C:\r\n<\/pre>\n
and look for interactive protectors like Password, TPMAndPIN, or TPMAndPinAndStartupKey. If present, delete them. (But don’t delete TPM or Numeric Password!)<\/p>\n
Bonus chatter<\/b>: Sometimes, the TPM doesn’t play friendly, and I have to enter my 48-digit BitLocker key (ugh). I don’t know why this happens.<\/p>\n","protected":false},"excerpt":{"rendered":"
How to get BitLocker and the TPM to play friendly.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[104],"class_list":["post-106468","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-tipssupport"],"acf":[],"blog_post_summary":"
How to get BitLocker and the TPM to play friendly.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/106468","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=106468"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/106468\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=106468"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=106468"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=106468"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}