FVE_E_OVERLAPPED_UPDATE (0X80310024) BitLocker fix

Cause 1: Third-party disk encryption or filter drivers

The culprit here is almost always a driver conflict. You've got something like Veracrypt, McAfee Full Disk Encryption, or even an old Symantec endpoint agent stomping on BitLocker's control block. The error means two threads tried to update the encrypted volume simultaneously — and neither won.

I've seen this most often on Dell Latitude 5490s with a pre-installed Dell Data Protection agent that wasn't fully uninstalled. The fix? Strip out every non-Microsoft disk encryption tool.

1. Open an admin Command Prompt (Win+X, then A)
2. Run driverquery /v and look for anything with 'encrypt', 'protect', 'filter', or 'disk' in the service name
3. Check for these common offenders: veraCrypt.sys, symenc.sys, mfeaskm.sys, fvevol.sys (that last one is legit — don't touch it)
4. Uninstall the software through Programs and Features, then reboot
5. After reboot, run manage-bde -status to see if the error clears

Still stuck? Boot into Safe Mode and run fltmc to list active filter drivers. Anything suspicious needs to go. I've had cases where a legacy HP ProtectTools driver was the problem — long after the software was removed.

Cause 2: Corrupt TPM key or stale boot configuration

If the driver angle doesn't pan out, the TPM might hold a bad key. This happens after a firmware update or a failed BitLocker suspend/resume cycle. The volume thinks it's being updated by one thread, but the TPM key doesn't match.

You'll need to clear the TPM and reprovision BitLocker. Back up your recovery key first — if you don't have it, you'll lose the drive.

1. Open PowerShell as admin
2. Run (Get-BitLockerVolume -MountPoint C).KeyProtector — note the recovery key ID
3. If you have the recovery key: manage-bde -protectors -disable C
4. Then clear the TPM: Clear-Tpm (Windows 10/11) or reboot into BIOS and clear it there
5. Reboot, let Windows re-initialize the TPM
6. Re-enable BitLocker: manage-bde -protectors -enable C

A faster move if you're on Windows 11 22H2 or later: run Suspend-BitLocker -MountPoint C -RebootCount 0. This pauses protection without clearing the TPM. Reboot twice, then resume. I've fixed 0X80310024 with just that trick more than once.

Cause 3: Volume metadata corruption from a bad power loss or unsafe eject

This one's rare but nasty. If the system crashed while BitLocker was writing a metadata update (like during a drive optimization or a recovery key rotation), the volume control block gets left in a half-baked state. Any subsequent operation triggers the overlapping update error.

The fix is to force a full check and repair of the BitLocker metadata. Don't bother with chkdsk — it won't touch the encrypted metadata.

1. Boot from a Windows installation USB
2. At the setup screen, press Shift+F10 to open Command Prompt
3. Run manage-bde -unlock C: -RecoveryPassword [your-recovery-password]
4. Then run manage-bde -off C: — this decrypts the volume fully
5. Once decryption finishes (check with manage-bde -status), run fsutil dirty query C: — if it shows dirty, run chkdsk C: /f
6. After chkdsk passes, re-encrypt with manage-bde -on C:

This takes hours on large drives. I tell people to do it overnight. Yeah, it's a pain, but it's the only way to rebuild a corrupt metadata block from scratch.

Quick-reference summary

Start with Cause 1. That's where 80% of my cases land. Cause 2 is next. Cause 3 only if you've tried everything else and the error still shows up. And yes — always save the recovery key to a safe place before you do anything with BitLocker. Learned that one the hard way.