Search Knowledge Base
KB #240127: Encrypted Databases Inaccessible After Adding, Removing, or Changing Load Order of Hard Drive
After adding, removing or changing load order of hard drives, encrypted databases may become inaccessible after a reboot. This may also happen if the SQL instance is on a Cloud server (for example, AWS, Azure, RackSpace, etc) since the hard drive load order may change at any time.
This issue has been fixed however may affect SQL instances Secured with earlier versions of Encryptionizer. To fix this condition upgrade to the latest version of Encryptionizer or apply patch KB240127.
Note that hard drive load order is internal to Windows and does not affect the drive letter.
Last modified: 1/13/2019