Windows 10: Cannot enable BitLocker

Hi all,



I need help with drive encryption. The BitLocker keeps giving me an error with a message "The startup options on this PC are configured incorrectly. Contact your system administrator for more information".





I have attempted everything I could on my own, and finally decided to ask a support here. Here is the chronological list of event that led to current state:



* On my ZBook 15 g3, that originally came with mechancal drive, I had BitLocker enabled and working for a while now

* Sometime ago I got a system notificaiton to update the security processor (TPM) driver. As this meant decrypting the drive, and encrypting it again, I opted to postpone this

* Finally I bought an SSD and decided this was the moment to update the TPM

* I have disabled the BitLocker, cloned the drive and replaced the HDD with new SSD (everything went smooth)

* Then I have update the BIOS and TPM drivers to the newest version (also smooth)

* Afterwards I have cleared TPM and rebooted the system

* Currently TPM status is - Attestation: Not Ready, Storage: Ready





Last thing to be noted, as this is requirement from BitLocker, there are at least two partitions on the noted SSD.





I hope someone has an advice on how to proceed on, thanks!

Nenad

:)

 

BitLocker won't enable on Windows 10 after update on Aug 9

Hi Brenda,

I would be happy to assist you.

Before I assist you I would like to know the information below,

• 
  Do you have a Windows 10 copy of the operating system?
  

I suggest you check whether the Bit locker is ON or OFF using the steps below.

Can you verify if BitLocker is enabled or disabled on your device? You can Enable/disable BitLocker by going to Desktop and follow these steps:

• 
  Swipe Right to Left to bring up the Charm.
  
• 
  Choose Settings.
  
• 
  Choose Control Panel.
  
• 
  Select BitLocker Drive Encryption.
  
• 
  Verify whether BitLocker is on or off on each device.
  

Also I suggest you to enable the WinRE so that you can enter the bit locker key and proceed.

When WinRE is disabled, you cannot enable BitLocker, and you receive an error message that resembles the following.

This PC doesn't support entering a BitLocker recovery password during startup. Ask your administrator to configure Windows Recovery Environment so that you can use BitLocker.

The solution would be to manually enable the windows recovery environment:

• 
  Copying the winre.wim file from c:\windows\system32\recovery\ to a folder on a recovery partition. (The partition need to have a drive letter at this point.)
  
• 
  Set the RE Image path. Example: reagentc /setreimage /path r:\recovery\windowsre
  
• 
  Enable RE with command: reagentc /enable
  
• 
  (You may remove the drive letter for the recovery partition after you have done this.)
  
• 
  Bit locker will be enabled.
  

If the issue still persists, suggest you to post your query on the below link.

https://technet.microsoft.com/en-us/library/hh831507(v=ws.11).aspx

Hope this information was helpful and do let us know if you need further assistance. We will be glad to assist.

Thank you.

 

Bitlocker

Hello Nandana,

To enable BitLocker on your computer, you follow the steps below:

• Sign in to your Windows account with an administrator access.
• Press the Windows key.
• Type and enter BitLocker.
• Click Turn on BitLocker.
• If the system is asking to sing in to administrator access, please do so.

For additional information about BitLocker, we suggest that you check the frequently ask question on this
link. The link provided applies to Windows 8.1 to higher version.

If you have other concerns, don't hesitate to reach us.

 

BitLocker refuses to enable

SarahKong: Inserting a flash drive would help if I could at least get past the error that the GPO isn't set. Step 1 (Enable BitLocker) in the article you specified is where my issue lies ... I can't even turn on BitLocker. Step 3 is where the flash drive
would come into play, but I can't get past step 1.

Andrea Da Costa: We don't set these GPOs in our domain, and I've tried gpupdate /force and a reboot to no effect.