Fixing the MBR (or something) when running two drives?

[stockhausen]

I have a system with Windows 10 Pro 64-bit installed on a 250GB SSD in the NVMe M.2 slot.

Because I wanted to “experiment” with Windows 10 and also because I wanted to set up a “Data” partition I decided also to install a shiny new 1TB SSD as a SATA III drive and to install Windows 10 in a dedicated partition on that drive.

Since I am lazy and it is tricky to do as it is hidden by the CPU cooler, I didn’t bother to remove the M.2 SSD when installing Windows on the 1TB SSD - I probably should have done

As a result of loading Windows 10 on to the new 1TB drive (while the M.2 SSD was still in place) I seem to have altered the MBR on the M.2 SSD such that when the system boots it asks whether I now want to boot

Windows 10 on volume 5

-or-​

Windows 10 on volume 2
​

With me so far?


90% of the time I just want to boot Windows from the M.2 SSD (on volume 5). When I do not want to boot from there I would press [F12] and choose to boot from the 1TB SSD (on volume 2) instead.

Can someone please tell me how I can (easily) correct this tiresome situation? Back in the day I could have edited the Linux GRUB but I don't know where to start with Windows.

Thanks

 

[stockhausen]

Many thanks for that @thenewoc, I am/was very familiar with MSconfig - it has of course now been superseded by the all-encompassing "settings" App.

I tried working through your suggestion but stopped when I realised that I might end up with a totally borked system.
I have decided to persevere with the current strategy; I have set a password on the 1TB SSD system and set the background image on it to a threatening "DO NOT USE" reminder.
I may move the M.2 SSD to a PCI Express M.2 SSD Adapter card when I have time.