Finding Why BitLocker Protection Stays Suspended on Windows
A BitLocker drive can stay fully encrypted while its protection is off. BitLocker is suspended before TPM firmware, UEFI, and Secure Boot changes so the PC can restart without a recovery prompt. Suspension keeps the data encrypted but protects the volume master key with a clear key stored unencrypted on the disk. Protection is meant to come back after a set number of restarts or a manual resume. This post covers how to find suspended drives, the three documented reasons protection stays off, and how to resume it.
A recent r/sysadmin thread describes PCs that stayed suspended after a suspend, with Resume-BitLocker failing with error 0x8031005F. The checks below start with that case and cover the other two causes Microsoft documents.
Find drives with protection off
Check the operating system drive from an elevated PowerShell window.
Get-BitLockerVolume -MountPoint C: | Select-Object MountPoint,VolumeStatus,ProtectionStatus,KeyProtector
A suspended drive has a VolumeStatus of FullyEncrypted and a ProtectionStatus of Off. The KeyProtector column holds the protectors the drive has now, for example Tpm and RecoveryPassword.
The number of restarts left before protection resumes can be read from the Win32_EncryptableVolume class.
Get-CimInstance -Namespace "ROOT/CIMV2/Security/MicrosoftVolumeEncryption" -ClassName Win32_EncryptableVolume -Filter "DriveLetter='C:'" | Invoke-CimMethod -MethodName GetSuspendCount
Suspend-BitLocker takes a -RebootCount from 0 to 15 and uses 1 when none is given. A count of 0 suspends protection until someone runs Resume-BitLocker. A script or vendor update tool that suspends with a count of 0 and never resumes leaves the drive suspended.
Read the BitLocker event logs
Microsoft's BitLocker troubleshooting guide points to the logs under "Applications and Services Logs", "Microsoft", "Windows", "BitLocker-API" in Event Viewer. The exact log names on a PC can be found with Get-WinEvent.
Get-WinEvent -ListLog *BitLocker* | Select-Object LogName,RecordCount
Pull the newest events from the management log around the time of the last suspend or restart.
Get-WinEvent -LogName "Microsoft-Windows-BitLocker/BitLocker Management" -MaxEvents 50 | Select-Object TimeCreated,Id,LevelDisplayName,Message
Look for warnings and errors near the restart that should have resumed protection. The same guide also says to check the System log for events from the TPM and TPM-WMI sources.
Cause one: Group Policy requires a recovery key
Error 0x8031005F is FVE_E_POLICY_RECOVERY_KEY_REQUIRED, "Group Policy settings require the creation of a recovery key." A recovery key here is the 256-bit key saved as a file, which is a different protector from the 48-digit recovery password. When policy requires the key file and the drive only has Tpm and RecoveryPassword protectors, Resume-BitLocker fails with this error and protection stays off.
Find the GPO that sets the requirement on an affected PC.
gpresult /h C:\Temp\gp.html
Open the report and search for "Choose how BitLocker-protected operating system drives can be recovered". The setting lives under Computer Configuration, Administrative Templates, Windows Components, BitLocker Drive Encryption, Operating System Drives. The report shows which GPO set it and how the 256-bit recovery key option is configured.
I'd change that option from required to allowed when nobody manages key files for these PCs. Run gpupdate /force on the PC and resume protection.
Resume-BitLocker -MountPoint C:
If the requirement has to stay, add the key file protector first and resume after it. Write the key to a folder off the encrypted drive, such as a removable drive or a secured share.
Add-BitLockerKeyProtector -MountPoint C: -RecoveryKeyPath "E:\Recovery\" -RecoveryKeyProtector Resume-BitLocker -MountPoint C:
The related error 0x8031005E, FVE_E_POLICY_RECOVERY_KEY_NOT_ALLOWED, is the reverse case. It means policy forbids the key file that a script tried to add.
Cause two: the recovery key backup failed
Microsoft's BitLocker FAQ covers devices joined to Microsoft Entra ID. When BitLocker is suspended automatically or without -RebootCount, Windows tries to resume protection at the next restart. If a policy requires the recovery key to be backed up, Windows waits up to 60 seconds for a network connection. Protection won't resume when the backup can't be made.
Connect the PC to the network, confirm it can reach Entra ID, and resume protection by hand. The FAQ also says an event recording the success or failure of the backup is written on the client, so the management log above should hold the failed attempt.
Cause three: setup never finished
Microsoft's operations guide says resuming protection only works on devices that have accepted the Windows license terms. A Microsoft Core Infrastructure and Security post describes the case in a Configuration Manager task sequence. BitLocker is suspended with a reboot count of 1 before a driver or BIOS update. The PC then restarts before the out-of-box experience is complete. Protection stays off after that restart even though the count was reached.
Resume protection manually at the end of the task sequence or after the first sign-in.
manage-bde -resume C:
Confirm protection is back
Run the first check again. ProtectionStatus should read On. The KeyProtector column should list every protector your policy requires. Restart the PC once and check again.
Where ET Ducky shows it
I build ET Ducky. You can open a Live Session shell to each affected PC from the browser without the need for a VPN and run the Get-BitLockerVolume, gpresult, and Get-WinEvent checks there.
When some PCs resume and others don't, you'd start a Multi-Agent Session across one PC that resumed and one that stayed suspended. It compares the kernel events from both to find the outlier. The raw events stay on the hosts.
Try it on one server
One Windows or Linux server costs $5 a month with no query subscription.
See pricing