You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add instructions on how to disable BitLocker to the dual boot guide.
BitLocker is a feature available on newer versions* of Windows and encrypts everything on the drive Windows is installed on. Problems arise, when one tries to install Linux alongside Windows and disables secure boot in the BIOS. This prompts BitLocker to encrypt the drive, thus making it impossible to boot without the BitLocker recovery key. Since most people aren't even aware of the feature, finding the recovery key can be bothersome, if not impossible.
BitLocker should thus be disabled before disabling secure boot in the BIOS. This can be done by selecting Start > Settings > Privacy & security > Device encryption > BitLocker drive encryption
or searching for BitLocker in the settings.
*BitLocker is not available on Windows 10 Home edition, but on the Pro edition and all editions of Windows 11.
The text was updated successfully, but these errors were encountered:
We should add instructions on how to disable BitLocker to the dual boot guide.
BitLocker is a feature available on newer versions* of Windows and encrypts everything on the drive Windows is installed on. Problems arise, when one tries to install Linux alongside Windows and disables secure boot in the BIOS. This prompts BitLocker to encrypt the drive, thus making it impossible to boot without the BitLocker recovery key. Since most people aren't even aware of the feature, finding the recovery key can be bothersome, if not impossible.
BitLocker should thus be disabled before disabling secure boot in the BIOS. This can be done by selecting
Start > Settings > Privacy & security > Device encryption > BitLocker drive encryption
or searching for BitLocker in the settings.
*BitLocker is not available on Windows 10 Home edition, but on the Pro edition and all editions of Windows 11.
The text was updated successfully, but these errors were encountered: