03-29-2015 07:51 AM - edited 12-31-2017 02:23 AM
So it seems that I can share following workarounds that works on my systems in order to prevent silent TCG Opal activation on the drives during W8.x/W10 install:
- it works - create small partition at the end of the clean drive (with Parted Magic I have created 300 MB ntfs partition at the end of the empty drive) and then install Windows. This seems to be quite simple solution
- it works - set ATA HDD password on the drive if your motherboard/laptop supports it and then install Windows
- it works - Shift+F10 at the begining of install (for example at this screen) and run following command (this is single line command)
Reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Wi
* You can also create small batch file (.bat extension) with the above command, place it on USB thumbdrive, Shift+F10 at the begining of install and run that .bat file.
- it doesn't work - Shift+F10 at the begining of install and run following command - that didn't work on my system Reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contr
There is one more thing that actually worked on my test system and I have found that out quite accidentally. Usually at the begining of Windows install I load Intel AHCI driver from USB drive. For that system I have loaded Intel RST 22.214.171.1246 and to my surprise Windows install haven't switched the drive to TCG Opal mode. However I am not sure if that would work with other/all versions of Intel AHCI driver. It may work because it seems that in general older Intel RST drivers does not provide OPAL support to volumes.
Note: Before applying any of the workarounds above the drive should be in ATA Security mode. So if the drive is in TCG Opal mode you should PSID revert it first.
04-01-2015 02:59 PM
I have also been trying to figure out the way to solve this issue and I think I have figured it out, it has to do with switching the driver for the Marvell SATA 3 to AHCI. When you don't use the Marvell driver, the error occurrs, and when you put it back it is gone. In searching all the forums for this problem there was no concrete answer for this issue, but after doing my own research, I realized that I had changed the drivers out, as many people do, and it also causes freezing and other issues, probably because the chip for the Marvell is wired into the motherboard. Also, they only time that this does happen is with Crucial SSD's so maybe there should be a fix for the firmware, if that is possible.
04-02-2015 12:43 AM
it has to do with switching the driver for the Marvell SATA 3 to AHCI. When you don't use the Marvell driver, the error occurrs, and when you put it back it is gone.
The driver thing may be a good lead too, for example Intel RST AHCI drivers does not support eDrive (I am not sure about the latest revisions though). I have just updated my previous post.
04-29-2015 01:24 PM
04-29-2015 03:21 PM - edited 05-12-2015 12:51 AM
I am not sure, I have tested that trick the way it has been described. r0m30's idea was to put the small partition at the end of the drive in order to let the Windows installer create all its partitions the way it likes - that is small System Reserved Partition at the very begining of the drive and main/big OS partition. I have done that with free PartedMagic, you can download .iso file and create bootable USB thumbdrive with UNetbootin. It is usualy most convenient way for me
Keep in mind that before you start W8 installation you should PSID revert the drive (it will wipe all data from your drive). Without that step the drive will still be in TCG Opal mode.
07-08-2015 08:58 AM
So it seems that I can share following workarounds that works on my systems in order to prevent silent TCG Opal activation on the drives during W8 install: .....
What about deactivating TPM in BIOS, does this also solve the problem?
07-11-2015 01:48 PM
I am not sure but I think hardware TPM isn’t necessary for eDrive. Also knowing that Opal mode is silently activated by Windows installer my guess would be that deactivating TPM in BIOS wouldn't work as a workaround. But you can try that if you want
08-01-2015 06:51 PM
I just wanted to say thanks for the work you've put into this issue. I have a M550 and I went from Windows 7 to Windows 10 Insider and then 10 Pro this week and for a while I've been having random crashes 3-5 times a week followed by restarts that become unresponsive after the lock screen, even after a fresh install of the final build. I used the reg ad method on clean install after a psid revert, and I've had substantially less issues and unexplained event log entries today compared to the last clean install I did.
08-03-2015 12:41 AM
I went from Windows 7 to Windows 10 Insider and then 10 Pro this week [...] I used the reg ad method on clean install after a psid revert
Thanks for this information! I was just wondering if this registry modification works on Windows 10