[Solved] Bitlocker: The System Cannot Find The File Specified

Background

While REG ‘s Samsung 990 pro 2tb Keeps Crashing It have no choice to disable the Bitlocker and move the entire partition to backup. But when REG trying to reenable Bitlocker it comes with an error:

The System Cannot Find The File Specified.

Reasoning

What could cause this problem

  • The corrupted system files
  • The missing MSR partition
  • The TPM
  • The Unreadable ReAgent.xml file

Solutions

System files scan

First REG tried sys file scan chk

sfc /scannow

Since the sfc found error and fixed it, the problem remains

Create MSR partition

REG noticed that he didn’t create the MSR partition since he moved the system

so REG did this

On windows command prompt

Enter Diskpart cmd:

diskpart

List disk cmd:

list disk

Select your disk avec :

<!> replace “x” with your case

select disk x

before the next step make sure u have enough unallocated space like this

then create the msr with:

create partition msr size=128

the whole process looks like this in REG’s case:

C:\Windows\system32>diskpart

Microsoft DiskPart version 10.0.xxx

Copyright (C) Microsoft Corporation.
On computer: DESKTOP-VOJR2AE

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         1863 GB   254 GB        *
  Disk 1    Online          xxx GB   xxx GB        *
  Disk 2    Online          xxx GB      0 B        *
  Disk 3    Online          xxx GB  xxxx MB        *

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             xxx MB  xxx KB
  Partition 2    Reserved            xx MB  xxx MB
  Partition 3    System             xxx MB  xxx MB
  Partition 4    Primary            xxx GB  xxx MB
  Partition 5    Recovery           xxx MB  xxx GB
  Partition 6    Primary            xxx GB  xxx GB
  Partition 7    Reserved           xxx MB  xxx GB
  Partition 8    System             xxx MB  xxx GB
  Partition 9    Primary            xxx GB  xxx GB
  Partition 10   Primary            xxx MB  xxx GB

DISKPART>

DISKPART> create partition msr size=128

DiskPart succeeded in creating the specified partition.

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             xxx MB  xxxx KB
  Partition 2    Reserved            xx MB   xxx MB
  Partition 3    System             xxx MB   xxx MB
  Partition 4    Primary            xxx GB   xxx MB
  Partition 5    Recovery           xxx MB   xxx GB
  Partition 6    Primary            xxx GB   xxx GB
  Partition 7    Reserved           xxx MB   xxx GB
* Partition 10   Reserved           128 MB  xxxx GB
  Partition 8    System             xxx MB  xxxx GB
  Partition 9    Primary            xxx GB  xxxx GB

DISKPART> exit

Leaving DiskPart...

C:\Windows\system32>

we have just crete partition 10 a 128m msr partition

but REG still got the problem remains.

Chk the TPM

tpm.msc

seems Nothing wrong.

The key to this problem: The ReAgent.xml file

Things seems no way out Untill REG find this blog:

Solution for BitLocker Error: โ€œThe system cannot find the file specifiedโ€

so REG renamed

C:\Windows\System32\Recovery\ReAgent.xml

to

C:\Windows\System32\Recovery\ReAgent.xml.old

and restart the computer

Then it works!

And windows recreated this file:

How does this even work?

What is ReAgent.xml ?

ReAgent.xml is a system configuration file used by Windows Recovery Environment (WinRE). It contains information about:

  • The location of the recovery image
  • Recovery environment settings
  • BitLocker recovery support details

Why this happens to REG’s case ?

As mentioned earlier REG has moved his system partition to a backup and restored it .

While BitLocker tries to reference ReAgent.xml and itโ€™s misconfigured. Causing the problem.

Further tips

enable bitlocker via cmd

this helps to identify the problem

manage-bde -on c: -rp

In REG’s case, theoretically it will get the error code 0x80070002 which help find out the problem quickly

Special Thanks to

  • ChatGPT for his pro tips
  • drivestrike.com for his detailed solution


Leave a Reply

Your email address will not be published. Required fields are marked *