So I recently upgraded some parts, including getting an NVMe SSD, which I'd like to make into my primary system drive.
Currently I'm dual-booting the old and the new windows, while in the process of transferring all settings, documents and data.
One thing I've noticed while playing around with the disks and partitions is that the old drive has the EFI system partition, which presumably holds the windows boot manager. (Is this correct?)
What's gonna happen when I finish the migration and format that drive (thus wiping out the EFI partition)?
Follow-up question:
The old install was having trouble booting when I switched the storage mode from AHCI to RAID. After messing around, and forming some hypotheses on how the windows boot process works, I was able to find a workaround. I do not exactly know how everything works, so I've been working on conjecture and extrapolation.
Conjecture: The EFI partition contains the windows bootloader which is like its own mini-OS with its own drivers and stuff.
My drive was failing to boot in RAID mode, because the bootloader was lacking raid drivers to access that drive and initiate the kernel from it.
So what I did was boot from a windows install USB, as if starting a new windows install, got to the part where it asks me to choose which drive to install the OS on - at that point you get a "Load driver" option. I loaded the drivers, then aborted the OS install process - lo and behold, my old install was now booting in RAID mode (presumably because I'd just installed the RAID drivers to the bootloader).
So the question is: Is there an easier way to install drivers on the bootloader?
Currently I'm dual-booting the old and the new windows, while in the process of transferring all settings, documents and data.
One thing I've noticed while playing around with the disks and partitions is that the old drive has the EFI system partition, which presumably holds the windows boot manager. (Is this correct?)
What's gonna happen when I finish the migration and format that drive (thus wiping out the EFI partition)?
Follow-up question:
The old install was having trouble booting when I switched the storage mode from AHCI to RAID. After messing around, and forming some hypotheses on how the windows boot process works, I was able to find a workaround. I do not exactly know how everything works, so I've been working on conjecture and extrapolation.
Conjecture: The EFI partition contains the windows bootloader which is like its own mini-OS with its own drivers and stuff.
My drive was failing to boot in RAID mode, because the bootloader was lacking raid drivers to access that drive and initiate the kernel from it.
So what I did was boot from a windows install USB, as if starting a new windows install, got to the part where it asks me to choose which drive to install the OS on - at that point you get a "Load driver" option. I loaded the drivers, then aborted the OS install process - lo and behold, my old install was now booting in RAID mode (presumably because I'd just installed the RAID drivers to the bootloader).
So the question is: Is there an easier way to install drivers on the bootloader?