Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, February 22, 2020 12:06 AM
Drive D: is a freshly format NTFS drive connected via ESATA to Windows 10 Version 1903 (OS Build 18362.476).
When attempting to enable BitLocker on the drive, the message below is displayed.
BitLocker works as expected with the same drive installed internally via SATA.
I was referred here from the other Microsoft forum. I tried command line and received same error.
C:\WINDOWS\system32>manage-bde -on G: -pw
BitLocker Drive Encryption: Configuration Tool version 10.0.18362
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Volume G: [KAD BACKUP2]
[Data Volume]
ERROR: An error occurred (code 0x80070001):
Incorrect function.
NOTE: If the -on switch has failed to add key protectors or start encryption,
you may need to call "manage-bde -off" before attempting -on again.
Hi Karl D, |
Prakhar_Khare has replied to your question BitLocker "Incorrect Function" when attempting to enable on ESATA drive. in Microsoft Community. |
Hi Karl,
Thank you for writing to Microsoft Community Forums.
I understand your query related to not being able to enable BitLocker for ESATA drive.
One of the things that you can try is using the manage bde commands to enable BitLocker on the drive, and see if that helps.
However, we do have a dedicate forums where you should be able to find support. Let me help you in pointing towards the right direction, I would suggest you to post your query on TechNet forums, where we have support professionals with expertise on BitLocker to assist you with your query.
Regards, Prakhar Khare Microsoft Community – Moderator |
All replies (4)
Saturday, February 22, 2020 2:21 PM ✅Answered
Hi Karl.
"Incorrect function" should never happen.
Sometimes, certain adapters lead to buggy behavior. Could you retry the operation with a SATA2USB-adapter?
If that fails as well, but, as you write, it works with a direct SATA connection, we need to look at policies that set rules for removable devices. USB2SATA and eSATA connections would classify the drive as "removable", while SATA would classify it as "fixed". Are policies active that set rules for removable devices?
Saturday, February 22, 2020 5:34 PM
Good idea. I'm using this device, and it has USB and ESATA.
I chose the ESATA because I don't have USB3, and feared that the USB2 connection would be much too slow to handle a 1TB drive.
When the drive is connected via ESATA and I right click it to enable bitlocker, it has the little security shield and prompts for admin password before proceeding, and I then get the error described earlier.
When the drive is connected via USB, it didn't prompt for security, and proceeded through the other questions without error.
I have begun encrypting the entire drive, but it may take a couple days to finish at the rate it is going now. I wonder once it's encrypted if I'll be able to hook back up to ESATA for better performance?
Karl D
Sunday, February 23, 2020 9:50 AM
I have seen rare cases where an encrypted drive was only usable using the connection method that was used to encrypt it. But as long as you have a data backup, feel free to try out ESATA after encryption has finished.
Sunday, February 23, 2020 2:09 PM
Wow. I've never used BitLocker before, but I thought it would be a mature technology by now.
My drive finished encrypting. I disconnected it and reconnected it, and it prompts me for the password in one of the new, slide-out, card-type notification windows on the right side of screen (card).
I have a long, complex password, and if I take focus off of the notification card to copy password from password keeper, the window disappears with no way to get it back.
So to unlock the drive, I need to go to command line as admin and run
manage-bde -unlock g: -pw
After doing that, it works, and it works via ESATA or USB.
I guess BitLocker isn't 100% ready for normal home users in all situations yet. Thanks both for your help.
Karl D