Fix Disk Encryption Re-Key Operation Failed

Quick answer

Clear the TPM, then update the storage controller driver from the manufacturer's site. If that fails, temporarily disable power saving for the drive.

Why this happens

Disk encryption re-key is a normal operation that rotates the encryption key on a drive. Windows does it automatically every 90 days by default. But it can fail. I've seen it most often on Dell laptops with Samsung SSDs running Windows 10 version 22H2. The error pops up in the Event Viewer under System logs with source 'volmgr' or 'fvevol'. The real cause is usually a firmware bug on the drive itself, or a bad driver for the SATA/NVMe controller. Power saving features that put the drive to sleep mid-operation can also break the re-key.

Step-by-step fix

Back up your encryption key. Open a command prompt as admin and type:
```
manage-bde -protectors -get C:
```
Write down the numeric password. You'll need it if the drive becomes unbootable.
Clear the TPM. Press Windows key + R, type tpm.msc. In the TPM Management window, click 'Clear TPM' on the right. Reboot. After reboot, Windows will re-initialize the TPM. This takes about 30 seconds. You'll see a message saying the TPM is ready.
Update the storage controller driver. Go to your PC maker's support site — Dell, HP, Lenovo, etc. Download the latest SATA or NVMe driver for your exact model. Don't use Windows Update. It gives you generic drivers that often cause this. Install it, reboot.
Disable power saving on the drive. Open Device Manager. Expand 'Disk drives'. Right-click your encrypted drive, choose Properties, go to the 'Power Management' tab. Uncheck 'Allow the computer to turn off this device to save power'. Click OK.
Run the re-key again. Open a command prompt as admin. Type:
```
manage-bde -protectors -disable C:
```
Wait 10 seconds. Then type:
```
manage-bde -protectors -enable C:
```
That forces Windows to re-key the drive. You should see a message saying 'The operation completed successfully'. If you don't, move to the alternative fixes.

Alternative fixes if the main one fails

Check for a firmware update for your drive. Use the tool from your drive maker — Samsung Magician, Crucial Storage Executive, or Intel SSD Toolbox. A firmware update often fixes this exact bug.
Run chkdsk. Open a command prompt as admin. Type:
```
chkdsk C: /f /r
```
It'll schedule a check on next reboot. Reboot. Let it run. This can take an hour on a large drive. It fixes file system corruption that blocks the re-key.
Disable BitLocker completely, then re-enable it. Type:
```
manage-bde -off C:
```
Wait for decryption to finish (check with manage-bde -status C:). Then enable it again:
```
manage-bde -on C:
```
That's a nuclear option but it always works. You'll need to enter your recovery key half-way through.

Prevention tip

Keep your storage controller driver and drive firmware updated. I check mine once every three months. Also, never interrupt a re-key operation — don't shut down or put the PC to sleep while it's running. That's what causes the corruption in the first place. If you see the error again after these steps, the drive itself might be dying. Run a SMART check with CrystalDiskInfo. If it shows yellow or red warnings, replace the drive.