Solved bootmgr file appeared on the root of my 'C' drive

thecaretaker · 2026-10-30T01:10:30-0400

I've only just noticed that I have a bootmgr file on my 'C' drive dated 20/01/2023. It pre-dates when Windows was originally installed by 1 year, 8 months, and 12 days (02/10/2024).

I have a healthy EFI system partition, Recovery partition and Windows 11 on my NVM Express.

I can't understand how it got there or how it is over a year older than my system. I Googled it to see if it is safe to delete, but Google says although it isn't required on a modern EFI system, it said whatever you do, do not delete it Windows will not be able to boot.

I recently followed Garlin's instructions to update the boot manager from the post HERE and after doing so, I did have to rebuild Macrium boot on the drive I use for Macrium to boot ('I' drive).

Dare I delete it?

I just can't understand how I have never noticed the file before or how it pre-dates my system. Over to you knowledgable people.

garlin · 2026-10-30T01:27:37-0400

Run this command, to find the actual file version:

Code:

powershell -C (Get-Item C:\bootmgr.efi).VersionInfo.FileVersionRaw

The normal Windows boot files are kept in the folders C:\EFI\Boot and C:\EFI\Microsoft\Boot. But other tools may use C:\ path to temporarily stage files, which they're copying around.

If we get an idea of the file version, it might tell us where this copy originated from. A boot file which is too old means it was extracted from some archival source. Do you use Macrium or Hasleo for backups?

thecaretaker · 2026-10-30T01:31:30-0400

garlin said:
Run this command, to find the actual file version:

Code:

powershell -C (Get-Item C:\bootmgr.efi).VersionInfo.FileVersionRaw

The normal Windows boot files are kept in the folders C:\EFI\Boot and C:\EFI\Microsoft\Boot. But other tools may use C:\ path to temporarily stage files, which they're copying around.

If we get an idea of the file version, it might tell us where this copy originated from. A boot file which is too old means it was extracted from some archival source. Do you use Macrium or Hasleo for backups?

The file doesn't have a .efi extension.

zbook · 2026-10-30T01:34:52-0400

Please download and install: voidtools

Type: bootmgr

Post images or share links.

Entries may be related to:
Aoemi
Minitool
Macrium
Windows
etc.

thecaretaker · 2026-10-30T01:37:16-0400

Don't know if this helps.

Just noticed, it says it was modified the day before it was created????

garlin · 2026-10-30T01:41:20-0400

Change the "C:\bootmgr.efi" to "C:\bootmgr"

cereberus · 2026-10-30T01:42:33-0400

It's always been there but is normally hidden. Somehow, it has become unhidden.

thecaretaker · 2026-10-30T01:45:18-0400

garlin said:
Change the "C:\bootmgr.efi" to "C:\bootmgr"

I did garlin but got no results.

thecaretaker · 2026-10-30T01:46:09-0400

zbook said:
Please download and install: voidtools

Type: bootmgr

Post images or share links.

Entries may be related to:
Aoemi
Minitool
Macrium
Windows
etc.

Wow, it returned this lot.

garlin · 2026-10-30T01:47:28-0400

thecaretaker said:
I did garlin but got no results.

Try opening it with NotePad. The file is too short for a modern Windows boot file, it may be some other file type.

Banjoman301 · 2026-10-30T01:48:52-0400

I have a bootmgr file in C: root as well...

From what I have read, it's normal on Legacy/MBR systems (which it was originally)

zbook · 2026-10-30T01:54:09-0400

thecaretaker said:
Wow, it returned this lot.

See if any of the results display:

433 KB
or
01/20/2023

thecaretaker · 2026-10-30T01:54:40-0400

garlin said:
Try opening it with NotePad. The file is too short for a modern Windows boot file, it may be some other file type.

I just get gobbledegook

garlin · 2026-10-30T01:58:15-0400

OK. It's probably the legacy MBR bootmgr. Let's figure out which version:

Code:

powershell -C (Get-FileHash C:\bootmgr).Hash

thecaretaker · 2026-10-30T02:00:07-0400

zbook said:
See if any of the results display:

433 KB
or
01/20/2023

Only the 1 says "C:\bootmgr",442414 (size),133187048045496011(Date Modified),,0

Banjoman301 · 2026-10-30T02:01:51-0400

Mine -

PS C:\Users\Jim> (get-filehash C:\bootmgr).hash
674E67855209B3BA02F7DC87F0AA66B70E9D1E900338EC96A7A36D013094BCC3

Corresponds to Windows 10, Version 22H2 (OS Build 19045) and Version 21H2 (OS Build 19044).

Had 'em both when it was a legacy MBR system.

Non-issue.

thecaretaker · 2026-10-30T02:02:16-0400

garlin said:
OK. It's probably the legacy MBR bootmgr. Let's figure out which version:

Code:

powershell -C (Get-FileHash C:\bootmgr).Hash

Code:

C:\Windows\System32>powershell -C (Get-FileHash C:\bootmgr).Hash
09A8BAFE9441684EAB8450F71E8A175E2601E0C3D68B20600B49829851CBC9CF

garlin · 2026-10-30T02:08:28-0400

Winbindex identified this SHA-256 as the bootmgr file from W11 22H2's KB5022303 (Jan 2023).

If you never had 22H2 installed on this system, then it shouldn't be there and obviously not required for an EFI setup. Beats me why you have this file.

Banjoman301 · 2026-10-30T02:19:47-0400

garlin said:
W11 22H2

I believe that should be W10 22H2...

The SHA-256 hash 09A8BAFE9441684EAB8450F71E8A175E2601E0C3D68B20600B49829851CBC9CF corresponds to the official Windows 10, Version 22H2 (Build 19045.2965) bootmgr file, which was released as part of the May 2023 Update (KB5026361).

thecaretaker · 2026-10-30T02:21:23-0400

It's only 433kb. Should I just mark it as a hidden file. Maybe the last Windows update turned off the hidden file setting for it?

I am wondering if the shop that built my system for me used a new NVM drive that was flashed with a pre made (as of then unregistered) Windows 10 disk image. Hence the bootmgr file being earlier than the date when Windows was actually activated by me. If they frequently make PC's for people its probably the easiest way to do it.

Solved bootmgr file appeared on the root of my 'C' drive

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer