I'm trying to use BitLocker eDrive hardware encryption, but Intel RST 188.8.131.521 is confilicting. I know this because when I uninstall RST, it works, but when it's installed it uses software encryption (BitLocker asks if I want to encrypt whole drive or only used portion)
This problem existed with an older version of RST on Windows 8.1 too and was fixed in version 13.2 (not entirely sure of exact version) but seems to be back.
Discussion about the issue earlier: https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/T440s-How-to-enable-the-Windows-eDrive-feature/td-p/1364811 T440s: How to enable the Windows eDrive feature? - Lenovo Community
Using Windows 10 x64 and Samsung 850 EVO SSD...
New observations: IRST conflicts even after being removed:
How to reproduce:
1 Clean Windows install
2 Install mentioned IRST version
3 Try Bitlocker: uses software encryption
4 Uninstall IRST
5 Try Bitlocker: Wizard uses hardware encryption, but after system check reboot, Bitlocker dissapears from Windows. No lock sign on drive. It asks for a password on boot, but pressing ESC just boots the pc, meaning it's not encrypted. Doing 'manage-bde -status C:' in CMD gives:
ERROR: The volume C: could not be opened by BitLocker. This may be because
the volume does not exist, or because it is not a valid BitLocker volume.
The only way I have found to get everything back to normal is reinstalling Windows. You can't disable or properly enable it without reinstalling
When I just clean install Windows and then encrypt, without ever having IRST, it works as expected.
I can confirm same issue.
Installing latest Intel AHCI Driver during WiX setup process, it is impossible to use bitlocker Hardware encryption.
It is possible to install these drivers later, but then WiX is loosing the bitlocker settings, but is still encrypted.
I' tried more then 10 times to install with Intel drivers without succss.
There are new RST drivers.
Can someone confirm that these drivers are working with bitlocker eDrive under Windows 10 ?
Thanks in advance.
I am using Windows 8.1 Pro x64 with a Samsung 850 Pro SSD. The hardware encryption is no problem when Intel RST 184.108.40.2063 is installed.
When I install the new RST 220.127.116.119, the system is very very slow and the hardware encryption is not detected anymore.
The only way back is to do a system recovery of an older recorvery point.
If you want to use the eDrive with BitLocker, please don't install Intel RST 18.104.22.1689!
The Intel RST 22.214.171.1243 has no problem with eDrive and BitLocker.
Thank you very much.
This was the reason for my question here.
The new drivers are crap and cannot be used for Bitlocker eDrive.
The RST Driver release 126.96.36.1993 worked with Win 8/8.1 but these drivers do not working with Windows 10.
The native Windows 10 SATA AHCI drivers deliverd by Microsoft are working very well.
Please try with the latest Intel® RST https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver Intel® Download Center and let me know of the results.
You may also try the native Windows* 10 SATA AHCI drivers from by Microsoft.
The Microsoft native drivers are working very well.
No need for me to test Inteldrivers for the moment.
But I want to know for future Windows 10 Installation, do these Intel drivers work with bitlocker......or which release is working with Windows 10?
You can read here the latest Intel RST drivers do not work with bitlocker under Windows 8.1 Pro ....
I would like to know when Intel is fixing these Bitlocker problems?
I'm not able to activate hardware encryption with the latest drivers.
Are there any news.... or is Intel not interestet to spread fully working drivers?
The windows native drivers have some problems with the sleeping modes...
As of now, the recommendation would be to wait for a new driver release that could have a fix for this issue.
Please refer to the release notes in the link below, where all the known and fixed issues are noted (for future references to check if this is added in the fixes).
https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver Download Intel® Rapid Storage Technology (Intel® RST) RAID Driver
I would like to gather some additional information regarding this to further investigate the situation and possible specific scenarios where the issue is present.
-Storage devices present (brand and model):
-RST driver versions tested:
If any additional information that you think is important or relevant to the issue is present, please do add it.
I look forward to your reply on this.
-OS: Windows 10
-CPU: i7 4790k
-Motherboard Model: Asrock z97 Extreme 4
-BIOS Version: 1.30 (it's out of date, but it affects the latest one too)
-Storage devices present (brand and model): 2x Toshiba DT01ACA300 (3TB) & 1x 1TB Samsung Evo 840 EVO
-RAIDs? Which?: None
-RST driver versions tested: 188.8.131.521, 184.108.40.2069, 220.127.116.112
All drives are encrypted w/ Bitlocker (the EVO is hardware encrypted w/ eDrive).
If I install any RST driver, I continue to get prompted for the Bitlocker PIN on startup but once I'm in Windows, Bitlocker says none of the drives are encrypted. The Standard SATA AHCI Controller driver works fine.
I am currently running tests on this.
I would like to know, did you install the Intel(R) Rapid Storage driver once the drives were encrypted already?
I added all drivers before encrypting the drives, so it is to get the nearest scenario to yours.
Scenario 1: If I install the RST drivers prior to encrypting, Bitlocker asks whether or not I want to encrypt used space or the entire drive. Since this drive is already hardware-encryption capable, I shouldn't even see this prompt.
Scenario 2: If I'm using the regular Microsoft drivers (i.e. not RST), I don't get the "encrypt used space or entire drive" question above. Bitlocker just asks me for my pin and then turns on.
If I go back and retroactively install RST after having already enabled Bitlocker (in scenario 2), the next time my PC boots up all volumes appear as un-encrypted and Bitlocker reports that it's turned off
It seems to me that the RST drivers are interfering with the SSD's ability to report that it is hardware-encryption capable. As soon as you introduce the RST drivers into the equation, hardware encryption stops working.