Windows asks for the BitLocker recovery key after installing Omarchy or Arch alongside it
Re-read the raw Arch wiki Dual_boot_with_Windows and both quattro manual pages. The wiki supports PCR 7 binding, recovery when Secure Boot is disabled, re-enabling Secure Boot restoring unlock, refusal of PCR 7 binding with non-Microsoft certificates in the chain (so not launching Windows from a Linux boot manager), default device encryption, Windows Hello methods being disabled, and 'permanent data loss'. manual/02-getting-started.md says 'You must turn off Secure Boot and/or TPM in the BIOS' and manual/50-dual-boot-install.md gives the Settings > Privacy & Security > Device encryption route. The cause and the manage-bde forms stand as the earlier audit found. One defect in the fix: step 3 told a reader at the recovery screen to re-enable Secure Boot, but the same Omarchy manual says Omarchy cannot be installed with it on, and an unsigned Limine will not boot with it on, so following step 3 trades the Windows prompt for an Omarchy that does not boot. The fix now says so and makes re-sealing from Windows the route for a machine that keeps Secure Boot off. Not exercised: no Windows here.
Changing Secure Boot keys or settings without the BitLocker recovery key saved can lock you out of the Windows partition permanently, which is **permanent data loss** in the Arch wiki's words. Get the key first. Turning BitLocker off removes encryption from the Windows partition, and may disable Windows Hello sign-in methods, so know your Windows password before doing it.
Symptom
"Since I installed Linux, Windows boots to a blue BitLocker recovery screen asking for the 48-digit key." It happens on every Windows boot, or only when Windows is started from the Limine or GRUB menu. Separately, the Omarchy installer refuses to install alongside Windows because BitLocker is enabled.
Cause
Windows seals the BitLocker key in the TPM against measured boot state, specifically PCR 7, which covers the Secure Boot state and the enrolled certificates. Omarchy's getting-started manual tells you to turn off Secure Boot and/or the TPM before installing. Turning Secure Boot off changes PCR 7, and turning the TPM off removes the key's store entirely, so either one sends Windows to the recovery screen. Changing the Secure Boot databases (for example sbctl enroll-keys) changes PCR 7 too. The Arch wiki also notes that Windows refuses PCR 7 binding when non-Microsoft certificates are in the boot chain, so launching Windows from a Linux boot manager can trigger recovery as well. Windows 11 and recently updated Windows 10 often have device encryption on even when Settings looks off, and Omarchy's dual-boot manual states its install method is not compatible with BitLocker.
Fix
## Before installing, or before touching Secure Boot
Save the recovery key somewhere off the machine. Then, in an elevated Windows command prompt, suspend protection for the next reboot:
manage-bde -protectors -get C:
manage-bde -protectors -disable C: -rc 1
Make the firmware change and boot Windows once. Protection resumes automatically after the count of reboots you set. This suspend-and-resume is the same path Windows uses for firmware updates.
For the Omarchy dual-boot installer, the manual's route is to turn BitLocker off completely: **Settings > Privacy & Security > Device encryption**, toggle it off, and wait for decryption to finish.
## Already at the recovery screen
- Enter the recovery key, taken from your Microsoft account's BitLocker recovery keys page or from wherever you saved it.
- Start Windows from the firmware boot menu (often F12) rather than from Limine or GRUB, so only Microsoft-signed code is in the chain.
- Re-seal the key to the current firmware state from inside Windows. This is the route for an Omarchy dual boot, which keeps Secure Boot off:
manage-bde -protectors -delete C: -type tpm
manage-bde -protectors -add C: -tpm
- The Arch wiki notes that re-enabling Secure Boot restores automatic unlock. On an Omarchy machine that stops Omarchy from booting, because the Omarchy manual requires Secure Boot off and its Limine is not signed. Only do it if you have set up your own Secure Boot signing for Linux, or no longer need Linux to boot.
Verify
Windows boots to the login screen without the recovery prompt across two consecutive boots, and manage-bde -status C: in Windows shows Protection On with a TPM protector listed.
Sources
- https://wiki.archlinux.org/title/Dual_boot_with_Windows
- https://github.com/Foxboron/sbctl/wiki/Linux-Windows-Dual-Boot-with-Windows-Bitlocker
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/manage-bde-protectors
- https://github.com/omacom/omarchy/blob/quattro/manual/50-dual-boot-install.md
- https://github.com/omacom/omarchy/blob/quattro/manual/02-getting-started.md