[Bitlocker articles] BitLocker cannot encrypt the system disk, prompting that Bitlocker is being started, the system cannot find the solution for the specified file

First eliminate the inherent deficiencies (1. First, the computer hardware supports TPM; 2. The computer system supports BitLocker encryption; 3. BitLocker encryption can be enabled normally on other disks except the system disk), but still cannot start BitLocker to encrypt the system disk, and finally change REAGENT.XML The file parameters were successfully resolved, and I made a record of the pitfalls. —【suy】
insert image description here

Article directory

1. Experimental environment

system	Version
Windows 11 Professional Edition	21H2 (OS build 22000.652);
Trusted Platform Module	2.0

(1) Problem: Starting Bitlocker, ❌The system cannot find the specified file

When enabling BitLocker on the system disk (C drive), it prompts "The system cannot find the specified file", as shown below.
insert image description here

1. Start BitLocker Drive Encryption Service

This is the fastest troubleshooting solution. First check whether the service BitLocker Drive Encryption Service has been turned on. If not, click Start and set it to run automatically.
Win+R run the command services.msc -> Services -> BitLocker Drive Encryption Service -> Start the service.
After starting the service and restarting the computer, the problem remains, and the system disk still prompts that the specified file cannot be found.
insert image description here

(2) Solution: Change the contents of the ReAgent.xml file

Reference link: Bitlocker “The system cannot find the file specified” (microsoft.com) .

1. Enter the ReAgent.xml file path

Path: C:\Windows\System32\Recovery\ReAgent.xml.
insert image description here

2. Change the contents of the ReAgent.xml file as follows:

Delete or rename the ReAgent.xml file, and back up the data before operation! ! ! When you try to run bitlocker again, it will create a new ReAgent.xml file on its own; if you can do this, you are very lucky and congratulations; if not, just change the contents of the ReAgent.xml file directly .

Generally, system files require administrator rights to modify. If it cannot be saved, it is recommended to create a new ReAgent.xml file on the desktop and replace the original file. Change the code to look like this:

<?xml version='1.0' encoding='utf-8'?>

<WindowsRE version="2.0">
  <WinreBCD id="{00000000-0000-0000-0000-000000000000}"/>
  <WinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <ImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <PBRImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
  <PBRCustomImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
  <InstallState state="0"/>
  <OsInstallAvailable state="0"/>
  <CustomImageAvailable state="0"/>
  <IsAutoRepairOn state="0"/>
  <WinREStaged state="0"/>
  <OperationParam path=""/>
  <OsBuildVersion path=""/>
  <OemTool state="0"/>
  <IsServer state="0"/>
  <DownlevelWinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <IsWimBoot state="0"/>
  <ScheduledOperation state="0"/>
</WindowsRE>

The screenshot content is as follows:
insert image description here

3. Restart the computer and successfully start system disk encryption.

After restarting, start BitLocker to encrypt the system disk, no error is prompted, and the encryption process option appears directly! ! !
insert image description here

4. Problem possibility analysis

When we try to open the Bitlocker console to encrypt the system disk, the ReAgent.xml file has been filled with the specific GUID of the WinreBCD and WinreLocation paths, and these parameters may cause BitLocker to fail to boot correctly due to changes in the system environment.

Manually set both the GUID and offset.xml in ReAgent.xml to 0 to make Bitlocker work as expected.
insert image description here

(3) Other tried solutions - ineffective

I have tried the following methods, but still cannot solve it, and the problem remains. Of course, if the following method doesn't work, it doesn't necessarily mean that the following method won't work on other machines. It may be related to my local environment. I just want to make a record.

1. Turn on group policy: you need to attach an ID card when starting

Run the command in Win+R terminal gpedit.mscto open the group policy;

Path: Computer Configuration->Administrative Templates->Windows Components->BitLocker Drive Encryption->Operating System Drive->Require additional authentication at startup; Double-click the Require additional authentication at startup policy item, click the Enabled option and leave
insert image description here
it When compatible TPM allows BitLocker to tick, then apply and confirm;

WIN+R again enter gpupdate /force to update the modified policy, and restart the computer;

2. SFC scans disk integrity

Administrator terminal execution command:

bcdboot C:\Windows /s C: /l zh-cn /f all

bcdboot %systemdrive%\Windows

After using SFC to scan, the machine displays normally and no problems are found; if you try to fix the problem, restart the computer and try again to see if BitLocker can be enabled.

Summarize

The data is priceless, and the operation is risky. I am just making a personal record. Please be responsible for your own data! ! ! Each device is different, and it does not mean that all problems encountered can be solved by this method.

[1] Bitlocker “The system cannot find the file specified” (microsoft.com)

[2] When BitLocker is enabled on the WIN10 system disk, "The system cannot find the specified file" is displayed - Microsoft Community

name	time
Start editing date:	April 30, 2022
Last edited date:	May 1, 2022

insert image description here