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) <noreply@anthropic.com>