This isn’t true. Try Linux Mint or Ubuntu, their installers are much better. Those installers used by Fedora, RedHat, and even SUSE can be a bit weird.
They specifically say unbloated Windows as well which while it’s not as difficult as they make out is still somewhat annoying.
I’ve recently had a Windows installer fail to see my NVMe drives until I changed some random UEFI setting because it was missing a driver. Linux could see it just fine, as could Hirens boot.
Not to make a “Gotcha”, but Linux Mint was the other distro I tried, as I’ve complained about before. The first release I tried, which was less than a year old (on a 2+ year old computer) didn’t even run the wifi, audio, or bluetooth drivers correctly.
And, I had that same type of UEFI setting on Linux; Mint wanted to install on a GPT drive record, when my old drives (on Windows) used an MBT. It’s a conversion process both OSes will help with, but Mint gave some errors with it, and it was honestly easier to use Windows’ tools to get it done. Not even sure why Mint was insistent on it. Oh, and a mostly distro-agnostic annoyance: While attempting that conversion and making extra space for the GPT format, I ended up wiping more of the drives than needed during conversion because the partition manager used on several distributions uses bad messaging, and incorrectly refers to an individual partition under /dev/nvmesda0# as a “device”.
UEFI won’t boot from MBR drives unless it’s in BIOS compatibility mode. What format the drive is in isn’t determined by a firmware setting, though it can affect the boot process. I don’t think you actually understand what you are talking about here. The easiest way to install OSes both Windows and Linux is by wiping the drive, which would have solved this issue. Dual boot on single drive configurations normally have issues and will always be more complicated. It’s better to use two drives where possible in most cases. I suggest you read up on BIOS vs UEFI and how partition tables work if you want to do a complex setup like that.
Mint is known for having older kernels and therefore not supporting the latest hardware. They have a different edition for newer computers called Linux Mint Edge edition. Something Arch derived like CachyOS or another distro using recent kernels will always have the best support for bleeding edge hardware. The CachyOS installer is also pretty friendly, though maybe not as much as Mint.
Note that my post said “old drives” - plural. Mint was being installed on a secondary, formatted drive, and refused because that drive was not GPT-formatted (that record exists outside of the filesystem formatting). At the time, the BIOS was not set to force UEFI, so this was Mint’s decision, not the BIOS’s, and I don’t understand it. I left Windows alone on a different drive.
Believe me, I did plenty of reading up on BIOS UEFI settings just to resolve the issue. I still don’t claim to be a master, but I at least know enough to express how annoying the reconfiguration can be - independent of which OS you’re choosing.
Actually no. It’s not Mint’s decision whether to start the install USB with UEFI or BIOS. It actually depends on what the firmware chose to start and how the install medium is formatted. Some install media is only setup for BIOS booting, some for only UEFI, and some can do both. If the firmware detects the medium as supporting both then it should choose UEFI first but this depends on what settings you have in the firmware, and if you choose an option at a boot menu as boot menus allow you to override the default. When it comes to actually installing the OS most sane installation software will look at how it booted and install that way. So if it detects it was starting with UEFI it will configure the install to be UEFI, same if it was started with BIOS it will install as BIOS. How does it know? UEFI variables are one way. They can normally only be accessed if the system was started with UEFI.
If you truly wipe a drive you wipe the partition table as well. You say the table is outside the file system formatting, and this is sort of true, but they are both just data on the disk. Disk don’t care where the partition table ends and the file system begins. In fact you don’t even need a partition table at all. Unlike some other systems Linux will let you put a file system straight on the disk, the whole disk, with no partition table in sight. It’s not recommended mind you, because it will freak Windows out if it sees it. Windows will see it as a blank disk and not so helpfully offer to format the thing. When I say format a disk, I mean the whole thing, partition table and all. It’s also not possible to make a partition tableless disk bootable in UEFI. In BIOS it’s possible though as BIOS doesn’t read partition tables. It just needs a boot sector and that’s it.
Also if you’re trying to change a disk from MBR to GPT, and you don’t care about data, you shouldn’t be converting it. You should be formatting/wiping the whole thing and making a new partition table. Which is normally what it offers to do if you tell it to erase everything and install it.
This isn’t true. Try Linux Mint or Ubuntu, their installers are much better. Those installers used by Fedora, RedHat, and even SUSE can be a bit weird.
They specifically say unbloated Windows as well which while it’s not as difficult as they make out is still somewhat annoying.
I’ve recently had a Windows installer fail to see my NVMe drives until I changed some random UEFI setting because it was missing a driver. Linux could see it just fine, as could Hirens boot.
Not to make a “Gotcha”, but Linux Mint was the other distro I tried, as I’ve complained about before. The first release I tried, which was less than a year old (on a 2+ year old computer) didn’t even run the wifi, audio, or bluetooth drivers correctly.
And, I had that same type of UEFI setting on Linux; Mint wanted to install on a GPT drive record, when my old drives (on Windows) used an MBT. It’s a conversion process both OSes will help with, but Mint gave some errors with it, and it was honestly easier to use Windows’ tools to get it done. Not even sure why Mint was insistent on it. Oh, and a mostly distro-agnostic annoyance: While attempting that conversion and making extra space for the GPT format, I ended up wiping more of the drives than needed during conversion because the partition manager used on several distributions uses bad messaging, and incorrectly refers to an individual partition under /dev/nvmesda0# as a “device”.
UEFI won’t boot from MBR drives unless it’s in BIOS compatibility mode. What format the drive is in isn’t determined by a firmware setting, though it can affect the boot process. I don’t think you actually understand what you are talking about here. The easiest way to install OSes both Windows and Linux is by wiping the drive, which would have solved this issue. Dual boot on single drive configurations normally have issues and will always be more complicated. It’s better to use two drives where possible in most cases. I suggest you read up on BIOS vs UEFI and how partition tables work if you want to do a complex setup like that.
Mint is known for having older kernels and therefore not supporting the latest hardware. They have a different edition for newer computers called Linux Mint Edge edition. Something Arch derived like CachyOS or another distro using recent kernels will always have the best support for bleeding edge hardware. The CachyOS installer is also pretty friendly, though maybe not as much as Mint.
Note that my post said “old drives” - plural. Mint was being installed on a secondary, formatted drive, and refused because that drive was not GPT-formatted (that record exists outside of the filesystem formatting). At the time, the BIOS was not set to force UEFI, so this was Mint’s decision, not the BIOS’s, and I don’t understand it. I left Windows alone on a different drive.
Believe me, I did plenty of reading up on BIOS UEFI settings just to resolve the issue. I still don’t claim to be a master, but I at least know enough to express how annoying the reconfiguration can be - independent of which OS you’re choosing.
Actually no. It’s not Mint’s decision whether to start the install USB with UEFI or BIOS. It actually depends on what the firmware chose to start and how the install medium is formatted. Some install media is only setup for BIOS booting, some for only UEFI, and some can do both. If the firmware detects the medium as supporting both then it should choose UEFI first but this depends on what settings you have in the firmware, and if you choose an option at a boot menu as boot menus allow you to override the default. When it comes to actually installing the OS most sane installation software will look at how it booted and install that way. So if it detects it was starting with UEFI it will configure the install to be UEFI, same if it was started with BIOS it will install as BIOS. How does it know? UEFI variables are one way. They can normally only be accessed if the system was started with UEFI.
If you truly wipe a drive you wipe the partition table as well. You say the table is outside the file system formatting, and this is sort of true, but they are both just data on the disk. Disk don’t care where the partition table ends and the file system begins. In fact you don’t even need a partition table at all. Unlike some other systems Linux will let you put a file system straight on the disk, the whole disk, with no partition table in sight. It’s not recommended mind you, because it will freak Windows out if it sees it. Windows will see it as a blank disk and not so helpfully offer to format the thing. When I say format a disk, I mean the whole thing, partition table and all. It’s also not possible to make a partition tableless disk bootable in UEFI. In BIOS it’s possible though as BIOS doesn’t read partition tables. It just needs a boot sector and that’s it.
Also if you’re trying to change a disk from MBR to GPT, and you don’t care about data, you shouldn’t be converting it. You should be formatting/wiping the whole thing and making a new partition table. Which is normally what it offers to do if you tell it to erase everything and install it.