What is the most painless and minimal way to dual boot these days?
I've been happily Windows-free for about 5 years, but lately I need some Win-only software including a few games that don't work at all on Linux. My main questions:
How to avoid Windows messing with my Linux install? Having a separate PC is not possible for me right now. I'm considering uninstalling grub and instead selecting the boot device I want from UEFI, idk if this is advisable though.
I'm also interested in how to get a Windows install that's as minimal as possible: I don't want to log in to a Microsoft account, I don't want telemetry etc, I only want whatever is strictly required to make my system functional. The one thing I do want is Windows Defender cause ain't no way I'm dealing with an antivirus.
Should I go for Win 11 or stick to 10?
Any tips or experiences are welcome!
Ps: I know this information is probably all out there, but I thought a post in this community about it would be useful for others as well.
UPDATE: I ended up going with a regular old dual boot using Windows 10 iot LTSC - there's a few games I wanted to run and a driver as well so I chose to install directly on hardware as opposed to a VM. I created the install media using Ventoy, and UNPLUGGED EVERY OTHER DRIVE during installation except the one Windows was supposed to come on. Afterwards I had to boot in with a live Linux USB (the nice thing about Ventoy is that you can write multiple ISOs to your USB so it came in handy) to manually install rEFInd onto the original EFI partition that my Linux install uses, then I just had to set up the correct boot order in UEFI and everything is working. I also had to fuck around on the boot partition and with efibootmgr to remove all traces of grub so things don't get tangled up which was a bit scary but things are working perfectly now.
Two physical drives. Install windows first in one, then Linux on the other. If you don't do this order windows boot manager will take over and you'll have to boot Linux from bios.
I'm not using dual boot anymore, but when I did, I always selected the partition from BIOS, which was totally fine for me. Are there arguments against it?
Only an issue if you don't disable fast shutdown on Windows. A hibernated system might get surprised if another OS moves files about while it was asleep.
Windows is never going to like an NTFS that has been touched by another OS even if it windows was completely shutdown during that time. Reading the NTFS partition might be okay. But, last I checked none of the Linux drivers could write without windows noticing and fouling things up. If that has changed it would be welcome news to me despite my warning use of windows.
If windows (and to a lesser extent that other OS) came bundled with some ability to mount, read, and write filesystems popular with other operating systems this wouldn't be such a problem. One shouldn't have to involve the network stack or 3rd party drivers just to share a partition on the same hardware or a portable drive with a modern file system.
One problem with that is that you will end up with two EFI partitions. This is not supported very well by anything, really, so you will run the risk of Windows messing with the wrong partition anyway.
i've been running two drives two EFI partitions dual boot for some time now and it never posed a problem specific to it. on the contrary it makes it easier to distro-hop since you can format the Linux EFI Drive and resize it however you want depending on the distro.
Yep, dual disks with the Windows installation done first is how I did/do it. GRUB/systemd-boot worked just fine from then on, and I am not on Windows 11, so I didn't get hit with that fuck-up Microsoft did just a few days ago.