bitlocker invalid syntax

[yusef88]

what's the right way to enter password in next command

Code: Select all

manage-bde -unlock k: -password MyPass

because i get this error message

Code: Select all

ERROR: Invalid Syntax.
"MyPass" was not understood.

[bdeshi]

pw prompts for a password. so you need to exec

Code: Select all

manage-bde -unlock k: -password

and you'll be prompted to enter a password. Enter the password (no bullets/*'s will be displayed).

piping or redirecting doesn't work here.

[yusef88]

I was hoping the batch enter the password and mount the drive without prompting like truecrypt,why microsoft doesn't make things easy..thanks

[PeterH]

I was hoping the batch enter the password and mount the drive without prompting like truecrypt,why microsoft doesn't make things easy..thanks

Maybe MS thinks that a PW specified in a script is about as secure as no password?
(For some software it wouldn't be hard to scan scripts for such strings. So the user may think he has added security...)

[bdeshi]

btw, you can pass a recovery file/key as an argument the way you want.
you need to have generated the recovery file first. (Manage Bitlocker->Save Recovery Key)
Find the recovery key in the saved/printed file (it should be the last readable line in the file), then use this either cmd:

Code: Select all

manage-bde -unlock K: -rp "000000-000000-000000-000000-000000-000000-000000-000000"
manage-bde -unlock K: -recoverypassword "000000-000000-000000-000000-000000-000000-000000-000000"

repalce the 00000-00000-... with the key.

(you can delete/shred the file afterwards!)

ed: this->either

[yusef88]

@SammaySarkar thank you
now i have a serious problem win 8.1 does not wake up from sleep i googled and the suggested solution is to update display drivers but windows tell me the best driver software is already installed

[highend]

And we now have to guess which graphic card you use, which driver is installed and whatever "the best" means in this case? oO

[yusef88]

reinstall driver fixed the problem
actually VirtualBox network driver was the problem not display driver
http://gurustop.net/blog/2013/09/11/win ... ox-bridge/