kingwaffle
Junior Member
- Apr 10, 2014
- 13
- 0
- 66
First off,
I just wanted to say that this thread is ridiculously informative. I've been Googling off and on all weekend regarding my particular issue and finally stumbled across this thread and learned quite a bit.
Hopefully someone here can provide advice, but I'm not hopeful as my issue is pretty specific...
A few weeks ago I purchased a TPM module for my motherboard and installed it. My goal was to enable Bitlocker on all of my volumes (my 1TB Evo & 2x3TB RAID-1 setup).
I quickly learned that this would likely entail a secure erase of my SSD to get the hardware encryption to work on my Evo. I used Magician to set the SSD into a "Ready to Enable" state and then used the Samsung secure erase ISO in order to prep the drive.
With my drive freshly wiped, I installed Windows 10 with a clean install. After trying (and failing) to get a clean install of Windows 10 to activate, I blew it away and installed/activated Windows 8 (not 8.1). From here, I installed Windows 10 using the "upgrade, keep nothing" option and now I'm typing this from my Windows 10 install.
Somewhere between the Windows 10 -> Windows 8 -> Windows 10 mess, I had some downtime so I was doing homework on requirements to enable the Bitlocker hardware encryption and realized that the SATA mode cannot be RAID, so I ultimately un-did my RAID setup and went to AHCI. I tested Bitlocker on my SSD and it successfully enabled with hardware encryption. A few minutes later, I turned it off and then began my Windows 10 upgrade.
Now that I'm on 10, I cannot re-enable Bitlocker without it asking what I want to encrypt (full drive/data only). I tried clearing the TPM, but that didn't work either.
I really don't know why/how I managed to get it work one time, but can't get it to work again. From what I understood, it sounds to me like once the drive is prepped, it should stick and turning off/on bitlocker should be seamless, but that doesn't appear to be the case.
I wonder if upgrading OS's makes the drive no longer eligible for hardware encryption?
tl;dr -- I succeeded in enabling Bitlocker hardware encryption once, but haven't been able to do it since. Anyone seen that before?
I just wanted to say that this thread is ridiculously informative. I've been Googling off and on all weekend regarding my particular issue and finally stumbled across this thread and learned quite a bit.
Hopefully someone here can provide advice, but I'm not hopeful as my issue is pretty specific...
A few weeks ago I purchased a TPM module for my motherboard and installed it. My goal was to enable Bitlocker on all of my volumes (my 1TB Evo & 2x3TB RAID-1 setup).
I quickly learned that this would likely entail a secure erase of my SSD to get the hardware encryption to work on my Evo. I used Magician to set the SSD into a "Ready to Enable" state and then used the Samsung secure erase ISO in order to prep the drive.
With my drive freshly wiped, I installed Windows 10 with a clean install. After trying (and failing) to get a clean install of Windows 10 to activate, I blew it away and installed/activated Windows 8 (not 8.1). From here, I installed Windows 10 using the "upgrade, keep nothing" option and now I'm typing this from my Windows 10 install.
Somewhere between the Windows 10 -> Windows 8 -> Windows 10 mess, I had some downtime so I was doing homework on requirements to enable the Bitlocker hardware encryption and realized that the SATA mode cannot be RAID, so I ultimately un-did my RAID setup and went to AHCI. I tested Bitlocker on my SSD and it successfully enabled with hardware encryption. A few minutes later, I turned it off and then began my Windows 10 upgrade.
Now that I'm on 10, I cannot re-enable Bitlocker without it asking what I want to encrypt (full drive/data only). I tried clearing the TPM, but that didn't work either.
I really don't know why/how I managed to get it work one time, but can't get it to work again. From what I understood, it sounds to me like once the drive is prepped, it should stick and turning off/on bitlocker should be seamless, but that doesn't appear to be the case.
I wonder if upgrading OS's makes the drive no longer eligible for hardware encryption?
tl;dr -- I succeeded in enabling Bitlocker hardware encryption once, but haven't been able to do it since. Anyone seen that before?
Last edited: