Installing any operating system is often a hassle. This comes in part from my own experience trying to understand the unguided partition recommendations of a Bazzite (basically Fedora on low level) install. I got through it, but it was certainly no easier than Windows.
Just to add another anecdatum, I had the exact same experience installing Windows 11 this year. I have never had this much trouble installing an OS in the 20 years I’ve been screwing with computers.
Yeah it’s not always that simple. You haven’t been around long enough to see the stuff that can go wrong with installing Windows. For example I recently had Windows refuse to see both SSDs in a machine. All because of something called Intel VMD. Took me a handful of attempts before I found the problem.
When Windows installs work they are fairly simple if long, but when they don’t work oh boy.
The unplugging of internet to get a local account?
Also they disabled that for Windows Home.
Some Lemmy users are actually just wankers. I would like it if you all stopped. It’s especially great when I have people like you who probably aren’t even experienced in tech.
They disabled the local account for offline devices on all versions including IOT. The solution is to hit shift + f10 for CMD and then running OOBE\BYPASSNRO which enables that feature. But 90% of people setting up windows for the first time just create an account or use one they already have. Not that it’s better to do it that way. Just that it isn’t that difficult.
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.
Why?
Installing any operating system is often a hassle. This comes in part from my own experience trying to understand the unguided partition recommendations of a Bazzite (basically Fedora on low level) install. I got through it, but it was certainly no easier than Windows.
Ubuntu install takes 20 mins, including download and burning the USB. Make it 30, maybe?
My only windows 11 install took 7 hours, multiple days, BIOS visits, searching for documentation and hair pulling, all with the same machine.
Yeah, there is a difference
Just to add another anecdatum, I had the exact same experience installing Windows 11 this year. I have never had this much trouble installing an OS in the 20 years I’ve been screwing with computers.
Damn, which part did you get stuck?
The clicking “next” part?
The unplugging of internet to get a local account?
Or the running of a debloating script?
Yeah it’s not always that simple. You haven’t been around long enough to see the stuff that can go wrong with installing Windows. For example I recently had Windows refuse to see both SSDs in a machine. All because of something called Intel VMD. Took me a handful of attempts before I found the problem.
When Windows installs work they are fairly simple if long, but when they don’t work oh boy.
Also they disabled that for Windows Home.
Some Lemmy users are actually just wankers. I would like it if you all stopped. It’s especially great when I have people like you who probably aren’t even experienced in tech.
They disabled the local account for offline devices on all versions including IOT. The solution is to hit shift + f10 for CMD and then running OOBE\BYPASSNRO which enables that feature. But 90% of people setting up windows for the first time just create an account or use one they already have. Not that it’s better to do it that way. Just that it isn’t that difficult.
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.