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
Friday, December 11, 2015 8:15 PM
Hi All,
I'm on Windows 10 Pro, Bitlocker (without TPM) is enabled and working for Removable drives, as well as the OS Drive.
I have an additional 2TB internal SATA drive that Bitlocker does not see. I do not get the option to enable Bitlocker, in the right click context menu for the drive.
If I go to Manage Bitlocker, the drive is not listed as a fixed data drive. It's not even listed at all.
There is nothing wrong with the drive itself. In its current unencrypted state, I have data stored on it, and can access, read and write to all of the drives contents.
I've checked through the bitlocker group policy options, and I've googled this to extensively with no solution found. Any help, short of a format/reload would be greatly appreciated.
All replies (3)
Tuesday, December 15, 2015 9:43 PM âś…Answered | 1 vote
Ok, I've managed to resolve this issue.
I found this thread
which pointed me to the source of the problem. The only partition on my secondary fixed drive was marked as the system partition, so Windows was unable to boot without it. No idea why this was the case, but it was. During the isntall of 10, it must have automatically chosen the wrong drive. The answer on this other thread
http://superuser.com/questions/989923/move-system-reserved-partition-windows-10
provided me the solution to move the system partition to the OS drive.
I've just finished doing this, and have been able to enable Bitlocker on my secondary fixed disk, and it is encrypting as we speak.
Over and out.
Sunday, December 13, 2015 9:55 PM
Is this a clean install of the latest TH2 release? It has been reported that Bitlocker does not work in that situation.
Bitlocker missing on Windows 10 Threshold (Build 1511)
Bitlocker hardware encryption cannot be activated on Win10 10586/1511
Hopefully there is some suggestions in those thread beyond the re-install the latest release.
Tuesday, December 15, 2015 8:44 AM
I am on Build 1511, but it wasnt a clean isntall. I ran the cumulative update from 10240.
I have found another thread that seems to point out the source of the problem. I am troubleshooting now. If it does in fact fix the problem, I will post the solution and relevant thread here.
I appreciate the help though, Mr. Happy.