Fix FVE_E_CONV_WRITE 0x8031001C BitLocker Error

BitLocker hit a write error partway through encrypting or decrypting a volume, so the conversion stopped. The drive usually has bad sectors, a loose cable, or a dying SSD.

You kicked off BitLocker encryption on a 2TB drive (or maybe you're decrypting one to hand the laptop back to IT), and partway through, the progress bar freezes. manage-bde -status shows "Conversion Status: Failed" with FVE_E_CONV_WRITE (0x8031001C). Or the BitLocker control panel throws "A write operation failed while converting the volume." The volume is now in a half-converted state—neither fully encrypted nor fully plain—and Windows refuses to move forward.

I've seen this on everything from a 2019 Dell XPS 15 with a WD SN720 NVMe to a cheap USB 3.0 external Seagate that got bumped during the initial pass. The trigger is almost always the same: something interrupted a write to the disk, and BitLocker decided the volume wasn't healthy enough to keep writing encryption headers to.

What's actually happening here

BitLocker's conversion isn't a single operation. It walks the volume sector by sector, reads the plaintext, encrypts it, and writes it back. On a 1TB drive at typical consumer SSD speeds, that's roughly 3–6 hours of continuous writes. During that time, every single write has to succeed. If one fails—a bad sector, a dropped USB connection, a driver reset on a SATA controller—BitLocker can't just skip it. The encryption key metadata and the data have to stay in sync or you'd end up with unreadable garbage.

So the FVE (Full Volume Encryption) driver bails out. Error 0x8031001C is literally the driver saying "I tried to write to this volume and the hardware underneath me said no." The volume stays in a converted-but-broken state, which is why manage-bde -status shows a percentage that isn't 0% or 100%.

The reason step 3 works is that you're giving the driver a clean surface to resume onto. If the underlying disk keeps rejecting writes, no amount of retrying BitLocker will help—you have a hardware problem, not a BitLocker problem.

The fix

Check the physical connection first. If this is an external drive, swap the USB cable and try a different port—ideally one directly on the motherboard, not a hub. For internal SATA drives, reseat both the data and power cables. I've fixed this exact error twice just by replacing a marginal USB 3.0 cable that was dropping packets under sustained load.
Look at the SMART data. Run this in an admin command prompt:
```
wmic diskdrive get model,status
wmic /namespace:\\root\wmi path MSStorageDriver_FailurePredictStatus get InstanceName,PredictFailure,Reason
```
If PredictFailure is TRUE, stop. Back up what you can and replace the drive. Continuing to hammer a dying disk with BitLocker writes will finish it off.
Run CHKDSK in read-only mode. Don't skip this to save time—it takes minutes and tells you if the volume itself is the problem:
```
chkdsk C: /scan
```
If it reports bad sectors, you've found your culprit. Run chkdsk C: /f to mark them, then try the conversion again.
Resume the conversion. BitLocker usually picks up where it left off:
```
manage-bde -resume C:
```
Watch it with manage-bde -status C:. If it fails at the same percentage every time, that's a strong signal of a specific bad region on the disk.
If it won't resume, decrypt and start over. This is slower but reliable:
```
manage-bde -off C:
```
Wait for full decryption, confirm the drive is healthy with a fresh chkdsk /f, then re-enable BitLocker from scratch. Starting from a clean state avoids any leftover half-written metadata.

If it still fails

Check the BitLocker event log. Open Event Viewer and look under Applications and Services Logs → Microsoft → Windows → BitLocker-API → Management. Events 8530 and 8531 will show the exact sector or offset that failed, which is enormously useful if you're trying to decide whether it's one bad spot or the whole disk going.

Run a manufacturer diagnostic. CrystalDiskInfo for a quick SMART read, or the vendor tool (Samsung Magician, WD Dashboard, SeaTools) for a proper surface scan. If the scan finds uncorrectable sectors, the drive is on its way out. The real fix is replacement—BitLocker is just the messenger.

And if the drive is perfectly healthy but the error keeps coming back, suspect the controller. Some older USB-SATA bridges (looking at you, JMicron JMS578) don't handle sustained high-queue-depth writes and will silently drop them. Moving the drive to a direct SATA connection on a desktop often makes the error disappear entirely.

Don't retry the conversion more than two or three times without addressing the underlying cause. Each attempt writes more data to a possibly-failing disk, and if it corrupts the BitLocker metadata mid-conversion, you're looking at data recovery territory—not a support forum answer.