Still, I don’t get why’d you do that, all my windows installation automatically put boot files onto C: and did not allow me to touch them afterwards.
G: also seems completely arbitrary, and I’m the majority of windowa setups wouldn’t exist or be an external drive.
Simple as.
The boot directory on your file system is where the system gets it from to put on G. It’s left there for recovery/repair
But you still have a G partition for the boot. It lets the computer itself have an easier time finding it (think labeled as boot). Your ssd is divided, it’s not a 2nd physical disk
The letter is arbitrary, so is C. It’s just the default
Why do you copy the boot files from C and put them in G during install then?
I don’t think anybody does that, honestly.
You can have a helper script do it for you (the gui) but it still happening in the background
The boot files go into C:, not G:.
Windows can’t operate if you did that, it doesn’t let you.
Copy Boot Files to EFI Copy the boot files to complete the EFI partition to boot into our windows.
bcdboot c:\Windows /s G: /f ALL
Source: https://christitus.com/install-windows-the-arch-linux-way/
Fijn article, thanks for sharing!
Still, I don’t get why’d you do that, all my windows installation automatically put boot files onto C: and did not allow me to touch them afterwards.
G: also seems completely arbitrary, and I’m the majority of windowa setups wouldn’t exist or be an external drive.
Simple as.
The boot directory on your file system is where the system gets it from to put on G. It’s left there for recovery/repair
But you still have a G partition for the boot. It lets the computer itself have an easier time finding it (think labeled as boot). Your ssd is divided, it’s not a 2nd physical disk
The letter is arbitrary, so is C. It’s just the default