Bitlocker encrypted system keeps asking for key at boot

I have an HP laptop with a TPM 1.2 level chip. I have successfully encrypted the C: drive with bitlocker. The OS is 32-bit Windows 7 Ultimate. However, every time I boot it, I have to enter the key.  

I have found several articles about this and they all pretty much say the same thing. I have decrypted the disk, reset and reinitialized the TPM module and reencrypted the disk and I get the same thing.

LVL 28
Who is Participating?
McKnifeConnect With a Mentor Commented:
Alright, I see.
"The system boot information" are a lot of things, please verify if any of the following could have changed:
What causes BitLocker to start into recovery mode when attempting to start the operating system drive?

The following list provides examples of specific events that will cause BitLocker to enter recovery mode when attempting to start the operating system drive:
 Changing any boot configuration data (BCD) boot entry data type settings with the exception of the following items:








When installing a language pack, an additional option in the language pack installation wizard asks if the user wants to apply language settings to All users and system accounts. If this option is selected, it will change the local computer BCD settings (if the user-only option is selected, BCD settings are not changed). This change will result in a modification of a BCD setting to the new locale value. If you are using a TPM with BitLocker, this is interpreted as a boot attack on reboot and the computer will require that the user enter the recovery password or recovery key to start the computer.

 We recommend that you suspend BitLocker before changing locales or installing a language pack, just as you would before making any major computer configuration change, such as updating the BIOS.


Changing the BIOS boot order to boot another drive in advance of the hard drive.

 Having the CD or DVD drive before the hard drive in the BIOS boot order and then inserting or removing a CD or DVD.

 Failing to boot from a network drive before booting from the hard drive.

 Docking or undocking a portable computer. In some instances (depending on the computer manufacturer and the BIOS), the docking condition of the portable computer is part of the system measurement and must be consistent to validate the system status and unlock BitLocker. This means that if a portable computer is connected to its docking station when BitLocker is turned on, then it might also need to be connected to the docking station when it is unlocked. Conversely, if a portable computer is not connected to its docking station when BitLocker is turned on, then it might need to be disconnected from the docking station when it is unlocked.

 Changes to the NTFS partition table on the disk including creating, deleting, or resizing a primary partition.

 Entering the personal identification number (PIN) incorrectly too many times so that the anti-hammering logic of the TPM is activated. Anti-hammering logic is software or hardware methods that increase the difficulty and cost of a brute force attack on a PIN by not accepting PIN entries until after a certain amount of time has passed.

 Turning off the BIOS support for reading the USB device in the pre-boot environment if you are using USB-based keys instead of a TPM.

 Turning off, disabling, deactivating, or clearing the TPM.

 Upgrading critical early startup components, such as a BIOS upgrade, causing the BIOS measurements to change.

 Forgetting the PIN when PIN authentication has been enabled.

 Updating option ROM firmware.

Upgrading TPM firmware.

 Adding or removing hardware. For example, inserting a new card in the computer, including some PCMIA wireless cards.

 Removing, inserting, or completely depleting the charge on a smart battery on a portable computer.

 Changes to the master boot record on the disk.

 Changes to the boot manager on the disk.

 Hiding the TPM from the operating system. Some BIOS settings can be used to prevent the enumeration of the TPM to the operating system. When implemented, this option can make the TPM hidden from the operating system. When the TPM is hidden, BIOS secure startup is disabled, and the TPM does not respond to commands from any software.

Using a different keyboard that does not correctly enter the PIN or whose keyboard map does not match the keyboard map assumed by the pre-boot environment. This can prevent the entry of enhanced PINs.

 Modifying the Platform Configuration Registers (PCRs) used by the TPM validation profile. For example, including PCR[1] would result in most changes to BIOS settings, causing BitLocker to enter recovery mode.


Some computers have BIOS settings that skip measurements to certain PCRs, such as PCR[2]. Changing this setting in the BIOS would cause BitLocker to enter recovery mode because the PCR measurement will be different.


Moving the BitLocker-protected drive into a new computer.

 Upgrading the motherboard to a new one with a new TPM.

 Losing the USB flash drive containing the startup key when startup key authentication has been enabled.

 Failing the TPM self test.

 Having a BIOS or an option ROM component that is not compliant with the relevant Trusted Computing Group standards for a client computer. For example, a non-compliant implementation may record volatile data (such as time) in the TPM measurements, causing different measurements on each startup and causing BitLocker to start in recovery mode.

Changing the usage authorization for the storage root key of the TPM to a non-zero value.


The BitLocker TPM initialization process sets the usage authorization value to zero, so another user or process must explicitly have changed this value.


Disabling the code integrity check or enabling test signing on Windows Boot Manager (Bootmgr).

 Pressing the F8 or F10 key during the boot process.

 Adding or removing add-in cards (such as video or network cards), or upgrading firmware on add-in cards.

 Using a BIOS hot key during the boot process to change the boot order to something other than the hard drive.

Please read the message carefully that tells you to enter your "key" (what key, the short PIN or the long recovery key?) and quote it here.
Normally, you will need to enter the recovery key only if something at bios level has changed or other low level hardware changes have taken place. Please quote.
jhyieslaAuthor Commented:
I'm not by the laptop at this moment, but what it wants is the long 48 character key. If I enter it, Windows boots just fine. I've installed bitlocker on other machines without issue, but this one fails to boot every time unless I enter the key. And the message, which I will post here on Monday when I am near the laptop, does mention that something has changed with the boot partition or something and all I am doing is merely shutting down the laptop, or restarting it, and then starting it up again. I even removed the HP tools partition and rebooted before installing any software beyond the OS and the HP drivers.
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

I am pretty sure the message tells you to disable bitlocker and enable it again (after once and only once typing in the recovery key). That would be normal if something had changed. But twice or even more often?
jhyieslaAuthor Commented:
So, I fired up the laptop after it sat all weekend and it went into Windows just fine. Then I rebooted it and got the message again. Here is what it says:

The system boot information has changed since bitlocker was enabled.

You must supply a bitlocker recovery key to stsart this system.

Confirm that the changes to the system boot information are authorized.

If the changes to the system boot information are trusted, then suspend and resume bitlocker. THis will reset bitlocker to use the new boot information.  Otherwise restore the system boot information.

I believe that I have done the suspend thing before.  But I get into Windows and I suspend and then resume.  Then I reboot and it comes up fine.  Then I log into Windows and then do a ShutDown from Windows. When I restart the laptop, I am presented with the message again.
jhyieslaAuthor Commented:
I figured it out. This particular model of HP laptop has a "bug" or something that is not compatible with the default cponfig of bitlocker. I followed the instructions on this web page :
to disable PCR 0. Now the laptop boots fine from restart as well as cold boot without asking for the key.
jhyieslaAuthor Commented:
Not a specific answer, but it did include pertinent information.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.