How do I enable a self-encrypting drive (SED) on Windows 7?

[Icthus_Tech]

Dennis, when the OP started using the SSDs, he found most worked properly, but 2 had the encrypting managed according to the DriveLock message.  MSED showed the LockingEnabled = N on the working drives, so this would be the normal state of the drives he received.  It was Y on the drives that didn't work properly. The reason I want to "see" if it is "N" after the revert was because A) I didn't know if the revert would do it and B) since the flag should not have been set I wanted to be sure it would be reset to N properly.  You have said that revert SHOULD do the job and since you seem to be more of an expert than I, I will presume that is correct.   However, I'd still like to see that the flag was reset to N, since it was not behaving the same as the "good" drives.  It never hurts to see.

Do you have any thoughts as to why some drives would have LockingEnabled Y and others N?  I would think they would have it all set to N by standard.  To have it randomly set either way is not good.

[Dennis_Handly]

>when the OP started using the SSDs

OP @kmccoy or or the most recent @masl_wm?

>You have said that revert SHOULD do the job and since you seem to be more of an expert than I

It will do the job IFF the SED was manufactured with the Locking SP in the Manufactured-inactive state.

>Do you have any thoughts as to why some drives would have LockingEnabled Y and others N?  I would think they would have it all set to N by standard.  To have it randomly set either way is not good.

This is vendor specific per TCG Standards.  It isn't random, it could vary by drive model or vendor.

But I would assume for SSC Opal, it should default to N, the Locking SP isn't in the Manufactured state.

And if it is Y, then ownership was taken and that's why there were problems.

[Icthus_Tech]

>>when the OP started using the SSDs

>OP @kmccoy or or the most recent @masl_wm?

Dennis, I suppose things do get more confused when there are multiple questions in the same forum thread.  I was referring to the OP of the question we are answering at this time.

>This is vendor specific per TCG Standards.  It isn't random, it could vary by drive model or vendor.

Since masl_wm used the same model drive made by the same vendor and the LockingEnabled flag was differrent and he says that he didn't do any kind of Opal management, then we may be looking at something hinkey with the vendor.  Perhaps  it is a refurbished drive or poor quality control issue.  If masl_wm didn't do anything to manage it, then this is something to keep in mind when purchasing the Crucial M500 240G drives (which I do all the time).

masl_wm, I look forward to hearing your results!

[Dennis_Handly]

>LockingEnabled flag was different and he says that he didn't do any kind of Opal management, then we may be looking at something hinkey with the vendor.

I doubt it.  This isn't something that a vendor would mess up.