So, I have a newish HP (Small Form Factor) "Business" machine.
It was previously running Windows 8.1 Pro on a spinner, but I have now upgraded it to Windows 10 Pro on an SSD drive.
When I installed Windows 10, I disconnected the other drive, because I've run into situations in the past where Windows will put the system partition on the old drive. I want to make sure that the new installation can run self-sufficiently entirely and exclusively from the new drive.
Now, when I plug the old drive back in (because I want to be able to access the files from the previous install), the system is always booting to the Windows 8.1 Pro drive.
So there are some obvious solutions here:
1. Unplug the old drive. Yes, then I can boot to Windows 10 just fine. But then I can't access my files on the old drive.
2. Put the old drive in a USB enclosure. OK. But I don't wanna!
3. Wipe out the old drive (after copying the files off). I will do that. But I want to figure out the cause of this problem!
There is another obvious solution, but it is not working and I want to know how to make it work
Change the boot order in the BIOS. Well, the SSD with Windows 10 is plugged into SATA0 and the spinner with Windows 8.1 is plugged into SATA1. I have specifically disabled SATA1 in the BIOS boot order, and moved SATA0 to the top, but that is only under "Legacy Boot Devices". "UEFI Boot Devices" is still at the top of the list, and under that is "Windows Boot Manager". I'm guessing that Windows Boot Manager is choosing the 8.1 Pro install for some reason.
(By the way, I know that SATA0 is functional in this configuration, because if I invoke the boot menu at startup, and manually choose SATA0, I can boot to Windows 10 just fine).
So my question is, how can I get the "Windows Boot Manager" to choose the Windows 10 SSD when there are two Windows installs available?
I tried running bcdedit in my Windows 10 install, but it only seems to be aware of itself (this may arise from the fact that I installed Windows 10 with the old drive disconnected). So am I right to assume that there are two Windows Boot Managers, one on each disk, each with no knowledge of the other?
In that case, what is making the BIOS choose the Windows 8 boot manager first, especially when it is installed on SATA1?
It was previously running Windows 8.1 Pro on a spinner, but I have now upgraded it to Windows 10 Pro on an SSD drive.
When I installed Windows 10, I disconnected the other drive, because I've run into situations in the past where Windows will put the system partition on the old drive. I want to make sure that the new installation can run self-sufficiently entirely and exclusively from the new drive.
Now, when I plug the old drive back in (because I want to be able to access the files from the previous install), the system is always booting to the Windows 8.1 Pro drive.
So there are some obvious solutions here:
1. Unplug the old drive. Yes, then I can boot to Windows 10 just fine. But then I can't access my files on the old drive.
2. Put the old drive in a USB enclosure. OK. But I don't wanna!
3. Wipe out the old drive (after copying the files off). I will do that. But I want to figure out the cause of this problem!
There is another obvious solution, but it is not working and I want to know how to make it work
Change the boot order in the BIOS. Well, the SSD with Windows 10 is plugged into SATA0 and the spinner with Windows 8.1 is plugged into SATA1. I have specifically disabled SATA1 in the BIOS boot order, and moved SATA0 to the top, but that is only under "Legacy Boot Devices". "UEFI Boot Devices" is still at the top of the list, and under that is "Windows Boot Manager". I'm guessing that Windows Boot Manager is choosing the 8.1 Pro install for some reason.
(By the way, I know that SATA0 is functional in this configuration, because if I invoke the boot menu at startup, and manually choose SATA0, I can boot to Windows 10 just fine).
So my question is, how can I get the "Windows Boot Manager" to choose the Windows 10 SSD when there are two Windows installs available?
I tried running bcdedit in my Windows 10 install, but it only seems to be aware of itself (this may arise from the fact that I installed Windows 10 with the old drive disconnected). So am I right to assume that there are two Windows Boot Managers, one on each disk, each with no knowledge of the other?
In that case, what is making the BIOS choose the Windows 8 boot manager first, especially when it is installed on SATA1?