From 7c5b97aa30226c79b1574d13f2c5133902ea413e Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Mon, 10 Aug 2026 04:46:48 -0700 Subject: [PATCH] Tell BitLocker users to decrypt, not suspend The free-space install detects BitLocker by the -FVE-FS- signature at offset 3, and suspending BitLocker leaves that signature in place: the volume stays encrypted, it just gains a clear-key protector. So the old message sent users to do something that could never let the install proceed. Aborting on a suspended volume is deliberate, so only the wording needed fixing. Fixes #99 Co-Authored-By: Claude Opus 5 (1M context) --- configs/airootfs/root/configurator | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/configs/airootfs/root/configurator b/configs/airootfs/root/configurator index 112a0dd..44e428b 100644 --- a/configs/airootfs/root/configurator +++ b/configs/airootfs/root/configurator @@ -507,8 +507,9 @@ run_partition_decide() { bl_part=$(detect_bitlocker || true) if [[ -n "$bl_part" ]]; then say --foreground 1 "BitLocker signature detected on $bl_part." - say "Suspend or disable BitLocker in Windows before installing alongside it." - abort "Aborted: BitLocker is active on this disk." + say "Turn BitLocker off in Windows and wait for the drive to finish decrypting, then try again." + say "Suspending BitLocker is not enough — the drive stays encrypted." + abort "Aborted: BitLocker is enabled on this disk." fi # Omarchy always creates its own dedicated ESP in free space and never