I have Lenovo ThinkPad R61i with Windows 7 64bit installed running latest BIOS. I have enabled Bit Locker on it but now with every re-boot it will ask for Bit Locker key from USB drive. I tried to suspend/resume Bit Locker as suggested but no luck. My TPM is enabled and I have ownership of it

Hi, Thanks for the post! Please refer to http://technet.microsoft.com/en-us/library/ee424315(WS.10).aspx to turn off the BitLocker. Hope it helps! Best Regards, Miya YaoThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I did suspend and fully decrypt hard drive before but every time I re-enable Bitlocker on every re-boot it will ask for a key.

I spoke to my colleague, Tanner Slayton, who pointed me to a blog article he wrote about this issue. The scenarios in his blog are very similar and should resolve the issue (e.g the HDD needs to be the first boot device). The full article is locate here- http://blogs.technet.com/b/askcore/archive/2010/08/04/issues-resulting-in-bitlocker-recovery-mode-and-their-resolution.aspx If the article doesn’t resolve the issue then please run manage-bde –status and paste the output here. Thanks, Ron Stock - Microsoft Online Community Support Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

I did follow the above but it did not work for me. I think that at this point I'm just going to turn it OFF and seek alternate solution.

Dariusz - Bit Locker really gets the job done well so before you migrate away from Bit Locker can you run the following command and paste the output here? I'd like to check one more thing based on the output. manage-bde –status Also please have a look at the complete list of items that would cause the recovery mode http://cc.bingj.com/cache.aspx?q=http%3a%2f%2ftechnet.microsoft.com%2fen-us%2flibrary%2fee449438(WS.10).aspx%23BKMK_examplesosrec&d=4909426914100190&mkt=en-US&setlang=en-US&w=c326ce78,965de680 When you are using a Laptop or Desktop computer and do not have the 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 settings with the exception of the following items: BCDE_LIBRARY_TYPE_DESCRIPTION, FVE_BCD_UNPROTECTED_DATATYPE BCDE_DEVICE_TYPE_RAMDISK_IMAGE_OFFSET, FVE_BCD_UNPROTECTED_DATATYPE BCDE_MEMTEST_TYPE_PASS_COUNT, FVE_BCD_UNPROTECTED_DATATYPE BCDE_MEMTEST_TYPE_TESTMIX, FVE_BCD_UNPROTECTED_DATATYPE BCDE_MEMTEST_TYPE_FAILURE_COUNT, FVE_BCD_UNPROTECTED_DATATYPE BCDE_MEMTEST_TYPE_TEST_TO_FAIL, FVE_BCD_UNPROTECTED_DATATYPE Warning 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. Note 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. Note 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. Ron Stock - Microsoft Online Community Support Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”