Search results

Ok, I should have seen that. Thanks again for your help, and patience.

Good idea on that f: drive. I plan to completely format it and will run your suggested diagnostics. But the issue I'm having with lock/unlock happens with other encrypted drives as well that haven't had any corruption issues. What's the simplest way to cleanly remove the registry entry your...

Update: I checked for Windows 10 updates and it says I'm current at the release I posted above. So, no idea what's causing the odd behavior on my system. Even with the persistent "Lock drive" option you gave me after the first unlock/lock cycle it stops working correctly.

Good to know. That particular drive has a bit of bad history. I was bitlocker encrypting it when it lost power. Totally corrupted it. I ran a data recovery utility and was able to salvage some data which I copied to another drive, and formatted the f: drive. Copied the salvaged data back...

Sure. I wasn't aware of a newer update. I'm doing another drive encryption now, and also discovered corruption on that f: drive I was locking/unlocking. Perhaps the force lock was a bad idea. In any case, it will take me a couple of days to get to a point where I can reboot, so will do the...

I'm on Version 1511 (OS Build 10586.545)

Ok, I fixed the problem with "Lock drive" not working with both "Lock drive" and "Unlock drive" being displayed. I had modified the lock-bde.vbs script and removed the force option, so that's why it didn't work initially. Put force back in and both Lock and Unlock work now with your workaround...

Yes. Both "Lock drive" and "Unlock drive" show up but "Lock drive" doesn't do anything. If I click on it and then click on "Unlock drive" I get the message the drive is already unlocked.

Tried this: manage-bde -lock -ForceDismount f: It worked. The "Unlock drive" option shows up in Explorer. Unlocked the drive, but have the same issue as with the script. Since it had been unlocked/locked previously Explorer still says "Unlock drive" instead of "Lock drive".

Ok, understood on that initial mistake. Just tried the manual lock command and got this: C:\WINDOWS\system32>manage-bde -lock f: BitLocker Drive Encryption: Configuration Tool version 10.0.10011 Copyright (C) 2013 Microsoft Corporation. All rights reserved. ERROR: Access was denied when...

Thanks again for your help. I'm copying a large folder to my encrypted drive at the moment so can't test the manual command, but will try it soon and let you know. One more thing that may have caused my problem, when I initially ran the reg edit script and used the "Lock drive" option I had...

Ok, rebooted, tried it again with the new script and it's doing the same thing. First iteration works fine but if I unlock the drive a 2nd time the "Lock drive" option isn't displayed. The option still says "Unlock drive". Clicking on it or the drive letter gives a message that the drive is...

Thanks for the quick response. I'm encrypting some drives at the moment so have to wait a day or so to test out the new script. I'll let you know how it goes. Appreciate your help.

Thanks for the utility. Works ok, but found an issue. If I unlock a drive, the "Lock drive" option works fine. But if I lock it and then unlock the drive again the "Lock drive" option doesn't show up, and instead the option still says "Unlock drive". Clicking on that or the drive letter in...