> 2. Linux: There is an age old Ubuntu bug (which bleeds into many Ubuntu based Distributions) where the installer wipes out the bootloader of a drive that you

> 2. Linux: There is an age old Ubuntu bug (which bleeds into many Ubuntu based Distributions) where the installer wipes out the bootloader of a drive that you aren't even installing the OS on. Dear open source community: your desktop OSs are still hobbyist tweaker mode. Maybe that's true, but ... I had a very similar thing happen on Windows 10. I set up a new SSD in order to install a new version of Windows with the idea that I would switch out the old SSD to an external drive. No big deal. So, I installed Windows on the new drive. Set everything up. Life looked good. I removed the old SSD. And the system wouldn't boot. WTF?!?! Turns out that if there is already a Windows bootloader then the Windows installer will put your boot information on it even if you tell it otherwise. You can't force an install and bootloader onto a new drive if it detects an existing install anywhere. I had to remove the old drive, remformat the new drive, and completely reinstall so Windows would install the boot partition and boot loader properly. I was "rather cross" to quote my UK brethren.