-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Archived Topics
- Notebooks Archive
- Windows 11 BitLocker Fatal Error 0x120 After Update + Hibern...

Create an account on the HP Community to personalize your profile and ask a question
05-14-2026 04:00 PM
I ran into a Windows 11 boot failure after an automatic Windows update. The laptop initially worked after the update, but later I put it into Hibernate to move locations. When I turned it back on, it failed with:
BITLOCKER_FATAL_ERROR 0x120
The system would not boot normally.
What did not fix it by itself
These did not fix the issue by themselves:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows DISM /Image:C:\ /Cleanup-Image /RestoreHealth chkdsk C: /f Deleting C:\hiberfil.sys Startup Repair Uninstall latest quality update
The Windows partition was still readable from recovery, and BitLocker could be unlocked with the recovery key, but the machine still would not boot.
What finally fixed it
The successful fix was to remove both the BitLocker/TPM problem and the stale hibernation resume state.
In my case, that meant:
Delete hiberfil.sys Fully decrypt BitLocker Remove the BCD resumeobject Delete the Resume from Hibernate BCD entry Cold boot normally Disable hibernation after Windows boots
Deleting hiberfil.sys alone did not fix it, but I still consider it part of the fix because the original failure happened while resuming from hibernation.
Fix steps
I did this from Windows Recovery / Windows USB Command Prompt.
1. Confirm the Windows drive
dir C:\Windows
In my case, Windows was on C:. If your Windows folder is on a different letter in recovery, use that letter instead.
2. Unlock the BitLocker drive if needed
Check status:
manage-bde -status C:
If the drive is locked, unlock it with the 48-digit recovery key:
manage-bde -unlock C: -RecoveryPassword YOUR-48-DIGIT-KEY
3. Delete the hibernation file
attrib -h -s C:\hiberfil.sys del C:\hiberfil.sys
If the file is not found, that is okay. It may already be gone.
4. Fully decrypt the drive
manage-bde -off C:
Then monitor progress:
manage-bde -status C:
The important lines are:
Conversion Status Percentage Encrypted Protection Status Lock Status
The goal is:
Conversion Status: Fully Decrypted Percentage Encrypted: 0.0% Protection Status: Protection Off Lock Status: Unlocked
At one point, my decryption appeared stuck at the same percentage. Running this kicked it back into progress:
manage-bde -pause C: manage-bde -resume C:
Then I waited until the drive was fully decrypted.
5. Assign a drive letter to the EFI/System partition
diskpart list vol
Find the small FAT32 EFI/System partition, then assign it S::
sel vol X assign letter=S exit
Replace X with the volume number for the EFI partition.
6. Check the BCD for hibernation resume entries
bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum all
In my case, the Windows Boot Loader had a resumeobject, and there was also a full Resume from Hibernate section.
That matched the history of the failure: the machine broke when trying to resume from hibernation after a Windows update.
7. Remove the stale hibernation resume pointer
bcdedit /store S:\EFI\Microsoft\Boot\BCD /deletevalue {default} resumeobject8. Delete the separate Resume from Hibernate BCD entry
In the bcdedit /enum all output, find the section named Resume from Hibernate.
It will have an identifier like:
identifier {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}Delete that entry:
bcdedit /store S:\EFI\Microsoft\Boot\BCD /delete {GUID-FROM-RESUME-FROM-HIBERNATE-SECTION}Replace {GUID-FROM-RESUME-FROM-HIBERNATE-SECTION} with the actual identifier from the Resume from Hibernate section.
9. Reboot
After full BitLocker decryption and removing the hibernation resume entries, Windows booted again.
10. After Windows booted, disable hibernation
From an Administrator Command Prompt:
powercfg /h off
I also left BitLocker off for the time being, created a restore point, and planned to fully update Windows before considering whether to re-enable device encryption.
My conclusion
In my case, this appeared to be a bad interaction between:
Windows update BitLocker / TPM validation Hibernate resume BCD resumeobject / Resume from Hibernate entry
The working fix was:
Delete hiberfil.sys Fully decrypt BitLocker Remove the BCD hibernate resume references Cold boot normally Disable hibernation
This is not guaranteed to fix every BITLOCKER_FATAL_ERROR 0x120, but it resolved mine when Windows was still readable from recovery and the failure began immediately after trying to resume from hibernation.