07-01-2024 09:36 PM - last edited 07-01-2024 09:44 PM
The Samsung 990 PRO 4TB specifications state that it supports AES 256-bit TCG/OPAL and IEEE1667: I try to enable Bitlocker hardware encryption, but it does not work and it looks like the drive is not, in fact, an Opal drive.
This is what I did to try to encrypt my whole system drive:
gpedit.msc
) "Configure use of hardware-based encryption for operating system drives
" to Enabled.Then it failed :
2.16.840.1.101.3.4.1.42
in the above policy.manage-bde -on C: -fet Hardware
I bought this SSD precisely to use the hardware encryption.
23-01-2024 06:42 PM
You need to get it to where the PCR7 binds. You can get more info from the Bitlocker logs under event viewer too.
23-01-2024 06:45 PM
Interesting. That's something I can try to troubleshoot.
Thanks, OBXMike.
23-01-2024 06:46 PM
No worries. I'm working on that part myself (that's how I know 😆)
23-01-2024 06:48 PM
Got it))
11-02-2024 06:43 AM - last edited 11-02-2024 06:43 AM
Has anyone had luck getting this to work. I think I am having issues with Blocking SID but I am not sure. I have tried it via the bios and windows2go but next boot and try to install it works then upon reboot the drive disappears.
14-07-2024 02:08 PM
I had the same problem.
I solved the problem in this way:
14-02-2025 10:08 PM
So I fought with this for a few hours. I have hardware encryption with Bitlocker setup and working - that in itself wasn't too difficult. What I couldn't do is get the encryption working using AES 256 which the tech specs claim.
Restricting the hardware encryption type to AES 256 CBC using OID 2.16.840.1.101.3.4.1.42 would not work. I also tried other OID's, entering all in the region 2.16.840.1.101.3.4.1.41 - 2.16.840.1.101.3.4.1.49 in the restricted algo field in the group policy object, to cover all possible variations of AES 256 (https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registration#External). No luck, it simply failed and complained that it could not fall back to software encryption due to group policy.
When I allowed the OID for AES 128 CBC it worked fine.
Eventually I gave up and now I have no desire to rebuild the system so guess I'm settled with AES 128 for the foreseeable future. For the benefit of future readers of this thread, has anyone gotten this working with the claimed supported AES 256 or is that incorrect/missleading markting info?
15-03-2025 05:44 PM - last edited 16-03-2025 02:23 AM
Finally I succeeded, thanks to the help of this thread. Indeed, cmd ps1 helped me to get on the right track. Unfortunately, on Dell F10 it shows up, but does not work - thanks to that I found this option in the new bios "XXX...Block SID...YYYY" and turned it off. I did it without "Windows Go" - I installed it and at the first start Shift + F10, I launched gpedit.msc from cmd (I set force hardware encryption), installation with starting Samsung Magician and ps1 - restart. After the restart I did the installation. It really only encodes in AES 128, but the problem is (at least on Dell) that every time it starts it asks for the HDD password (bios question window) - just give cancel, but it is quite irritating - especially when working remotely. Has anyone managed to solve the problem of this password prompt in Dell?