I would like to something about BCDBOOT

[Rbcc56]

While I was on the web trying to get a piece of code to work

for %%i in (A B C D E F G H I J K L M N O P Q R S T U V W X Y Z) do ( if exist "%%i:\fartyname.txt" set usbletter=%%i )

Dism /apply-image /imagefile:%usbletter%:\sources\install.wim /index:6 /ApplyDir:C:\

bcdboot c:\windows /s S: /f all

I keep getting an error that seems to point to the [S:]

https://commandmasters.com/commands/bcdboot-windows/: 

/s S:: Denotes the system partition where the boot files should be installed.

Is this where the boot file are copied or where they are Originated?
/f all: This argument instructs bcdboot to prepare the boot files to support UEFI firmware type.
C:\Windows: Again, this specifies the Windows directory from which to copy the required boot files. Should this be where they are originally [C:\Windows]?

Should the S: Partition be active??

John

[Tripredacus]

You only use the /s or /f option on GPT disk partition layout. You cannot make a partition active on a GPT disk.

[Rbcc56]

5 hours ago, Tripredacus said:

You only use the /s or /f option on GPT disk partition layout. 

but not both?  am I right?

 

[TSNH]

21 hours ago, Rbcc56 said:

Is this where the boot file are copied or where they are Originated?

/s is the destination (in MBR disk S: should be active partition)

21 hours ago, Rbcc56 said:

C:\Windows: Again, this specifies the Windows directory from which to copy the required boot files. Should this be where they are originally [C:\Windows]?

Yes - it should be the C:\Windows of the windows installation that you want to add to the bootloader

21 hours ago, Rbcc56 said:

Should the S: Partition be active??

Based on my limited knowledge of GPT (and this alligns with what @Tripredacus said) there is no such thing as active partition for GPT disk

Instead you may have to (or maybe this will be done automatically) make a FAT32 efi partition instead, but I don't know the details about that cause I don't have much experience with GPT disks, so look that up

[Tripredacus]

12 hours ago, TSNH said:

Instead you may have to (or maybe this will be done automatically) make a FAT32 efi partition instead

If using Diskpart, you just make the FAT32 efi partition on a GPT disk. You don't set anything, so I'm guessing Windows (or bcdboot) just works with it as is.

I think Diskpart will actually show an error message if you try to make a partition active on a GPT disk

[jaclaz]

Only to clarify, making a partition active doesn't touch at all the partition itself, what "make active" means actually "mark the partition as active in the corresponding MBR partition table entry (by writing 0x80 in the appropriate field)", it is essentially flipping a flag to allow the MBR code to know which partition boot record is to be chainloaded .

On a GPT partitioned disk there is not really a MBR, its place is taken by a "protective MBR" that has only a table  with a single entry with a special partition type (0xEE) that spans the whole disk and is there to tell older programs that they shouldn't touch the MBR partition table.