Comment on Microsoft Is Now Being Sued Over Sunsetting Windows 10
BJ_and_the_bear@lemmy.world 1 day agoThis also why I don’t do whole disk encryption; it makes recovery impossible
Comment on Microsoft Is Now Being Sued Over Sunsetting Windows 10
BJ_and_the_bear@lemmy.world 1 day agoThis also why I don’t do whole disk encryption; it makes recovery impossible
conorab@lemmy.conorab.com 1 day ago
You can work around it in both cases. SecureBoot will only prevent you from running non-signed boot loaders. If that breaks then you just turn off SecureBoot while you work on the issue (assuming SecureBoot failing isn’t due to a compromised boot loader) and the machine will boot normally minus any data stored in the TPM such as the encryption key. For the encryption key, this is something you are supposed to keep a copy of outside the TPM for scenarios like this. On Windows consumer PCs, this is stored in your Microsoft account or the place you specify when enabling it. For Azure or AD-joined PC’s this can be stored in Azure or AD.
The only ways SecureBoot and encryption will burn you are if there is data stored in the TPM that you don’t have a backup of or way of re-creating, or if the encryption headers on the drive are lost. That said, if you aren’t using a TPM some Windows features will break regardless and if the drive is so messed up that the encryption headers are lost then you’re probably back to backups anyway.