- Hasleo bitlocker anywhere cannot use user password update#
- Hasleo bitlocker anywhere cannot use user password full#
- Hasleo bitlocker anywhere cannot use user password windows 10#
- Hasleo bitlocker anywhere cannot use user password password#
- Hasleo bitlocker anywhere cannot use user password windows#
ALWAYS back up to an image before enabling bitlocker.ģ. Why the whole situation failed is beyond me - but I definitely have some new rules:ġ. So replacing this bootloader with the actual backup The "hardware test" obviously set the main bootloader to mark the drive as "encrypted", but it clearly wasn't as encryption hadn't begun yet.
Why do the MS "MVP"s not even suggest something like this? I've seen tons of threads with my issue with no resolution.ģ. Why in the world does Automatic Repair not try an chkdsk /f in this kind of situation automatically, andĢ.
Hasleo bitlocker anywhere cannot use user password windows#
I know this sounds way too simple to be true, and trust me - I have 30 years of Windows experience and typically the "MVP" answers straight out of TechNet here are useless, and thinks like chkdsk and sfc /scannow NEVER work.īut this time it did - and I was in the exact situation as you.ġ.
I rebooted my machine, and EVERYTHING WORKED AND I GOT IN WINDOWS. But then when I ran manage-bdeĪgain, it told me my system drive was FULLY DECRYPTED! This made sense, as the encryption had never actually started. When doing so, chkdsk said it found errors and corrected them - basically, it said it couldn't read the primary bootloader (makes sense, perhaps it was encrypted?) so it loaded the secondary. I was five seconds away from giving up - when I decided to boot into recovery via the Windows installation USB one more time and do a simple chkdsk /f on the drive.
Hasleo bitlocker anywhere cannot use user password password#
Go into the "hardware test" phase, after which it rebooted and I got stuck in apparently limbo - my recovery keys did not work, my password did not work, I'd get in a recovery boot loop, and when I did put the password in I'd get UNMOUNTABLE BOOT Then tried enabling bitlocker, printed out my recovery key and backed it up to a USB stick, and let the machine
Hasleo bitlocker anywhere cannot use user password windows 10#
I tried to encrypt my drive in Windows 10 on a machine without TPM, so I set the mode to allow USB/Password authentication on boot via gpedit msc. Inaccessible boot drive after Win10 (build 14393 - so it's not the <1511 XTS-AES compatibility issue that many other threads show) - during the "hardware test" phase - and recovery keys/passwords I just spent hours going through the same issues as you. Summary = BitLocker is flawed and this is nothing else then a bug.
Hasleo bitlocker anywhere cannot use user password full#
So to sum up, drive was not yet encrypted but in test mode, good recovery key was available but didn't worked, I've lost the a whole day of work DATAs (lucky me i have a yesterday's full backup) and i'm reinstalling everything now. Tried as well all the "manage-bde/repair-bde" possibilities i've found to no success.
Unable to unlock this drive with the correct key!
Hasleo bitlocker anywhere cannot use user password update#
I've tried many things, like unmounting the drive and insert it (M1.2 to SATA cage/USB) in a same Windows 10 version plus super latest update patches to no success. Once key put in, system booted to "UNMOUNTABLEīOOTDEVICE" BSOD and fall back to RECOVERY whatever (which honestly never recovered ANYTHING for me)) At BitLocker sys check needed restart, my entered (and correct) PIN didn't workĪnd my computer stated after only one (1x) PIN input that i'd tried to many wrong PIN inputs and asked for my recovery key (which i've had since i've saved my key from the BitLocker wizard on a usb stick). Just acknowledged the exact same issue today, was encrypting my OS (and only laptop HDD) and checked "let BitLocker conduct system checks". Is there a way to tell that the container is ok? if i start the encrypted win10 i have to enter the bitlocker pw and this is working, but then a bluescreen appear and message "unmountable bootdevice" appears, then the computer restarts, and autorepair comes up and put a bitlocker window inįront, because i have to enter the recovery password, if i enter it it want work. if i look at other "manage-bde -status" examples there are more details displayed instead of unknown. Volume "D:" ĭifference is that I tried to access the bitlocker container from windows 10 version 1511 which normaly should understand the xts-aes 128 format.ĭo you know if the container is corrupt or is there a chance to decrypt that container. used bitlocker with windand used XTS-AES 128 for encryptionĬ:\Windows\system32>manage-bde -status D:īitLocker-Laufwerkverschlüsselung: Konfigurationstool, Version 1Ĭopyright (C) 2013 Microsoft Corporation. correct password and recovery key are not working when trying to unlock bitlocker container from other OS
0 kommentar(er)
