Windows 10 Cannot get Hardware Encryption with BitLocker (eDrive) working (Samsung 980 Pro 1TB)

[Niklas-Stadler]

Issue

I am failing to hardware encrypt my Samsung SSDs with BitLocker (eDrive). I tried this with a 980 Pro 1TB and a 970 Evo 1TB neither of those worked.


Hardware used

Motherboard ASUS TUF GAMING X570-PLUS (Bios Version 3001)

CPU Ryzen 9 3900X

RAM 2x CMW32GX4M2C3200C16 (4*16 = 64GB Corsair Vengeance RGB Pro - 3200MHz in total)

GPU Radeon RX 5700 XT GAMING X

SSDs Samsung 970 Evo 1TB; Samsung 980 Pro 1TB


Things I have tried - with 970 Evo and 980 Pro

• From a SATA Windows Boot drive:
  • Enabled Drive encryption with Samsung Magician (state is Ready To Enable)
  • The Firmware is up-to-date according to Magician
  • Created a Secure Erase Stick with Magician
  • Created a 64-bit Windows Installer USB (should be 20H2)
• Booted into the Secure Erase environment and secure erased SSD
• In the BIOS
  • Enabled Secure Boot
  • Disabled CSM Support
  • Set Windows Installer UEFI USB as only boot source
  • Enabled Disable SID Blocking (Also enabled the disable on every following boot)
• Rebooted to the Windows Installer
  • Installed Windows Education
  • only selected the drive, no manual partitioning at all
  • rebooted the system
• Let Windows reboot (Setup) - Enabled Disable SID Blocking as mentioned earlier
• Let Windows reboot again (Setup) - Enabled Disable SID Blocking as mentioned earlier
• Used Domain User
• In freshly installed Windows
  • Installed Magician checked state (Encrypt Device: Enabled)
  • Set BitLocker through policies to force HW encryption
  • Tried to enable BitLocker on C: Drive - failed
  • Installed AMD Drivers (Chipset, GPIO,...) with autodetect setup
  • Installed Samsung NVME drivers (only on the run with 970 Evo, because 980 Pro isn't supported)
  • Installed all Windows updates
  • rebooted
• Booted into Windows - Enabled Disable SID Blocking as mentioned earlier
  • retried enabling BitLocker - still fails with the same Error with both the 970 Evo and the 980 Pro

Conclusion

I am doing something wrong... Or maybe something is broken with BitLocker, Windows or my motherboard.


Questions

Has anyone same problems? Or even has fixed this in the past?


I appreciate any help

Continue reading...