Quick fix: 0% encryption stuck usually means BitLocker is waiting for TPM provisioning or for the drive to enter encryption-ready state. On new SSDs, the drive’s firmware may report “not ready” until first idle period. Wait 5 minutes. If still stuck, run manage-bde -on C: -used in elevated terminal to force the encrypt-used-only path which starts immediately.
You ran Turn on BitLocker on a fresh SSD. The wizard completed; encryption started; progress shows 0%. An hour later still 0%. The drive isn’t encrypted; the operation is stuck. Either TPM provisioning failed silently or the drive’s hardware encryption negotiation is hung.
Affects: Windows 11 with BitLocker on new (typically NVMe) SSDs.
Fix time: 15 minutes.
Why hardware-encryption-capable SSDs sometimes hang
Some SSDs report support for hardware self-encrypting drive (SED) operations. BitLocker tries to use that if the drive claims it. Buggy or partially-implemented SED firmware causes the encryption attempt to hang at 0% — BitLocker is waiting for the drive’s own encryption to start, but the drive isn’t responding.
Method 1: Force software encryption
- Cancel the current attempt:
manage-bde -off C:in elevated Command Prompt. - Wait for decrypt to complete (usually quick since nothing was encrypted).
- Force software encryption via Group Policy:
gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → BitLocker Drive Encryption → Operating System Drives → Configure use of hardware-based encryption for operating system drives. Set to Disabled. (For Home, set registry:HKLM\Software\Policies\Microsoft\FVE\OSAllowedHardwareEncryptionAlgorithms= 0.) - Run gpupdate /force.
- Re-enable BitLocker. Encryption starts and progresses.
Method 2: Use encrypt-used-only
- Cancel pending encryption.
- Re-enable with the “used disk space only” option:
manage-bde -on C: -used - This encrypts only the regions currently containing data; the empty space encrypts as it’s used. Much faster start; same security level on previously-unused drives.
Method 3: Update SSD firmware
- Visit the SSD manufacturer’s site (Samsung, Crucial, WD, Sabrent).
- Download Magician/Storage Executive/Dashboard tool.
- Update SSD firmware to the latest.
- Retry BitLocker.
Verification
manage-bde -status C:shows Conversion Status progressing past 0%.- Encryption Method shows XTS-AES (software encryption).
- The encryption progress increments steadily.
If none of these work
If encryption still hangs at 0% after firmware update and software-only mode, check Event Viewer → System log for BitLocker errors around the time you started. For SSDs in RAID configurations, BitLocker behavior is unpredictable — encrypt the underlying disks separately or migrate off RAID.
Bottom line: 0% hang = hardware encryption negotiation problem. Force software mode via policy, or use encrypt-used-only to bypass. SSD firmware updates often fix the root cause.