C:\boot missing

AdamElectriq said:

This thread looks like on each iteration, there are successful outcomes so I hope this may help me too please!
I wish if possible, to not lose my data please!

Have done up to the screenshot below,
Many thanks! @NavyLCDR




MY F drive is the original OS drive I am trying to fix btw.

Code:

diskpart
select disk 3
select part 1
assign letter=w
exit
bcdboot F:\Windows /s W: /f UEFI
exit

NavyLCDR said:

Code:

diskpart
select disk 3
select part 1
assign letter=w
exit
bcdboot F:\Windows /s W: /f UEFI
exit

Hey Navy!
Thank you so much man! Absolute hero! I need to understand though, what does the command

Code:

bcdboot F:\Windows /s W: /f UEFI

do, and how did you realise that was what the problem I was suffering with fixed it??
I mean how did you know, probably via experience but just from the surface..

Thanks in advance!

https://learn.microsoft.com/en-us/wi...iew=windows-11

AdamElectriq said:

Hey Navy!
Thank you so much man! Absolute hero! I need to understand though, what does the command

Code:

bcdboot F:\Windows /s W: /f UEFI

do, and how did you realise that was what the problem I was suffering with fixed it??
I mean how did you know, probably via experience but just from the surface..

Thanks in advance!

Just experience. the BCDBOOT command makes an entry in the Boot Configuration Data file which is what tells the boot loader about the operating systems that are available to load. I identified which partition was the EFI system partition because it is typically a small partition with FAT32 filesystem. I gave it the drive letter W:. The /s W: in bcdboot told the command where to create the BCD entry. /f means firmware type. It had to be UEFI because you were booting from a GPT disk and from an EFI partition. /f BIOS means legacy BIOS booting (or CSM) and can only boot from an MBR disk with an active partition. There is an /f BOTH option which means boot from an MBR type disk, usually with a FAT32 active partition which would be bootable in both UEFI and legacy BIOS modes (such as the standard Windows 10/11 installation flash drive created by Microsoft's Media Creation Tool).

NavyLCDR said:

In your command prompt, run the following commands. If any of the commands fail, stop and post which one failed:
diskpart
sel dis 0
sel par 1
del par override
cre par EFI
for fs=FAT32 quick
assign letter=T
exit
bcdboot C:\Windows /s T: /f ALL
exit

Then reboot the computer.

I signed up just to say I was trying to figure this out for 2 days after using Macrium Reflect to close a drive and this was the solution. NOT the bcdrebuild command so many others claimed. For me this exact steps solved the issue and the drive booted. I did take the old drive out and put the new (NVMe) directly into the old slot. Not sure that was part of the issue. Both drivers were GPT.

cybertri said:

I signed up just to say I was trying to figure this out for 2 days after using Macrium Reflect to close a drive and this was the solution. NOT the bcdrebuild command so many others claimed. For me this exact steps solved the issue and the drive booted. I did take the old drive out and put the new (NVMe) directly into the old slot. Not sure that was part of the issue. Both drivers were GPT.

Glad it worked well for you!

pepanee said:

I was skimming through all this, and oh my... this command really had me laughing!

for fs=FAT32 quick

I know something else that stands for "fs".
More specifically: ffs

Hahaha wow. Good one Microsoft!

=þ

If you want to assign a drive letter to a volume in diskpart the short command is, you guessed it:
ass letter=<whatever letter>