Bitlocker when starting encryption it gets the following error "JSON value not found"

Question

Bitlocker was not registering so did a decrypt on the hard drive. Then restarted bitlocker to encrypt the drive and got the following error. JSON value not found. Tried rebooting the computer and tried again to start it. Had an old document that said to go out and delete the file C:\Windows\System32\Recovery - delete the REAgent.xml and try again. That didn't work.

Answer 1

Hello Schneider, Linda (OMA-GIS),

Thank you for posting in Q&A forum.

Here are some steps you can take to troubleshoot and resolve this issue:

1. Reset TPM (Trusted Platform Module):

• Open the Run dialog (Win + R), type tpm.msc, and press Enter.

• In the TPM Management console, select "Clear TPM" from the right-hand pane.

• Restart your computer and try enabling BitLocker again.

2. Run the following commands to check and repair disk errors:

chkdsk /f /r

sfc /scannow

dism /online /cleanup-image /restorehealth

After running these commands, restart your computer and try enabling BitLocker again.

3. Rename or Delete the ReAgent.xml File (maybe you have tried):

• Open Command Prompt as an administrator. Navigate to the Recovery folder:

cd C:\Windows\System32\Recovery

• Rename the ReAgent.xml file: ren ReAgent.xml ReAgent.old

• If renaming doesn't work, you can try deleting the file: del ReAgent.xml

• Restart your computer and try enabling BitLocker again.

4. Reinstall BitLocker:

• Open PowerShell as an administrator. Uninstall BitLocker:

Disable-WindowsOptionalFeature -Online -FeatureName BitLocker -NoRestart

• Restart your computer.

• Reinstall BitLocker:

Enable-WindowsOptionalFeature -Online -FeatureName BitLocker -All

• Restart your computer again and try enabling BitLocker.

5. Check Group Policy Settings:

• Open the Group Policy Editor (gpedit.msc). Navigate to Computer Configuration -> Administrative Templates -> Windows Components -> BitLocker Drive Encryption.

• Ensure that the policies are configured correctly and that there are no conflicting settings.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best Regards,

Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

Had this issue yesterday and resolved this by changing the registry.

Very simple solution, at least for our Organization.

Open registry and go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\FVE

Check if the Encryption Method value is the same for these 3.

In this case you can see that the value for EncryptionMethodWithXtsRdv is set on 4

Our organization is using this Encryption method: XTS-AES-256-bit which is value 7

Changed the value and rebooted the machine and after that Bit locker was working properly again.

Had one machine where the problem persisted so I turned of Bit Locker and turned it back on and rebooted the machine. Problem solved.