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

Looks like yours is actually for Windows 10 22H2 Build 19045.2965...

I'd just leave it alone.

Mine's been there for several years (since Windows 10 21H2).

I wouldn't worry about.

EFI systems don’t need it. If you’re still concerned and want to prove it for yourself, move the file to a different folder and reboot. You still have use of the Recovery environment to move it back.

garlin said:

EFI systems don’t need it. If you’re still concerned and want to prove it for yourself, move the file to a different folder and reboot. You still have use of the Recovery environment to move it back.

Click to expand...

I put it into a folder, I was still able to boot to the desktop and also boot to my Macrium drive. I'm just gonna check I can access the recovery options and if I can, I will delete it.

Thanks everyone for your help. I shall mark this topic as solved

BIOS/MBR systems rely on a chain of boot sectors — the disk's Master Boot Record (MBR) and the active partition's Volume Boot Record (VBR) — with the MBR boot code using the active partition flag to locate the partition whose VBR boot code loads the bootmgr executable.

UEFI/GPT systems do not use the MBR/VBR boot sector chain or the active partition flag. Instead, UEFI firmware loads EFI executables (.efi) directly from the FAT32-formatted EFI System Partition, normally using a boot entry stored in NVRAM.

BIOS/MBR: BIOS firmware → MBR boot code → active partition's VBR boot code → bootmgr (reads BCD) → winload.exe

UEFI/GPT: UEFI firmware → NVRAM boot entry → bootmgfw.efi on the EFI System Partition (reads BCD) → winload.efi

Celery said:

UEFI/GPT systems do not use the MBR/VBR boot sector chain

Click to expand...

Garlin as much as said so in post #22...