Windows 10: Unlock Bitlocker encrypted fixed drive in Standard user account

I have encrypted my fixed drive(non-OS drive) using manage-bde (with autounlock enabled) from Admin User account. After encryption is complete, then i switch user account to standard user account. But my fixed drive is still locked. Can you suggest why this is happening and how can I make fixed drive unlocked for Standard User account.


Any reply would be of great help.

Thanks

:)

 

Failure to unlock BitLocker encrypted HD after new windows 10 installation

Hello Kostas,

Thank you for bringing up your query on Microsoft Community.

We sincerely regret for the inconvenience caused.

You can use BitLocker Drive Encryption to help protect your
operating system drive (the drive where Windows is installed), a
fixed data drive (such as an internal hard drive), or a
removable data drive (such as a USB flash drive).

The way you unlock an encrypted drive depends on two things:

• What kind of drive it is.
• What kind of unlock method you chose when you set up BitLocker on the drive.
  

I suggest you to refer to the following article and check if it helps.

Unlock a BitLocker-protected drive

http://windows.microsoft.com/en-US/windows-8/unlock-bitlocker-protected-drive

(Applies to Windows 10 as well).

Hope it helps.

Let us know the status, we are glad to assist you further.

 

Can't unlock Bitlocker Encrypted Drive

I have a Bitlocker encrypted external HDD without any OS installed in it. I plugged it to pc with usb then i unlocked my drive on Win10 with my password as usual then i was copying the data from my unlocked
Bitlocker encrypted drive to another non-encrypted drive. Then power cut suddenly. After that i can't access my Bitlocker encrypted drive anymore.

-When i try to unlock that drive from Windows Explorer pop-up says "Encryption on this drive is not compatible with your Windows. Try to unlock it with newer version of Windows." without password and recoverypassword/recoverykey
input options. But my Win10 is fully updated (1703)

-Tried Win7 popup came without asking any password "Failed to unlock the drive. No protector keys found in this drive."

-I also tried manage-bde -bitlockerdrive -protectors -get the output is "ERROR: No key protectors found". But drive seems like encrypted already.

-I tried repair-bde with 48 digits recovery password for recovering data to another HDD. Recovery done without any errors. Then did "chkdsk
outputdrive: /f" it says "File system is NTFS. The first NTFS boot sector is unreadable or corrupt. Reading second NTFS boot sector instead. Unable to determine volume version and state. CHKDSK aborted." The disk shown as RAW and i can't access it.

-After that i also tried thirdparty recovery tools for recovering data on the drive that created after repair-bde (decrypted RAW one). I recovered all my files without any corruption. But all of them shown
as RAW files and had randomized names without folder structure. Somehow repair-bde can't transfer folder structure. I tried thirdparty recovery tools on unaccessable Bitlocker encrypted drive. It listed all my files with correct file names and folders. So
folder structure on encrypted drive is not corrupted i think but i can't recover them because they are encrypted and i can't open any file. I need folder structure, my files are too dispersed. What is the solution ? Thanks.

 

Failure to unlock BitLocker encrypted HD after new windows 10 installation

Hello Abdul,

In my case, I have a partition of a fixed data drive which is encrypted with bitlocker.

The problem happened after I replaced my damaged operating system drive (which is not encrypted) and installed windows again at a new operating system drive.

The problem is that, when I try to unlock the encrypted drive, is says that
"The password entered is incorrect", but I am absolutely sure that the password is correct.

Then I try to enter the recovery key, which I found in my microsoft account and it says that
"The key doesn't match this drive". Again, I am sure I used the correct 48 digit recovery key.

I hope this describes better my issue.

Thank you,

Kostas