Windows has consistently nuked my bootloaders and installed its own bootloaders on random drives. I gave up dualbooting years ago.

Haven’t dual-booted in like 10 years, so I don’t have hands-on experience with it, but AFAIK that’s not really a problem since UEFI, or a much less common one.

Back then, with legacy BIOS computers, it booted by directly executing the first sector of the hard drive. This meant that there could only be one bootloader per disk, and so if Windows thought its bootloader was supposed to be used and it had an update, it just overwrote it. Or it would think it’s been corrupted/infected.

Now with UEFI, it’s its own partition and it supports having more than one there out of the box, so unless your boot process depends on detecting the default one rather than exactly which executable is the default, even if Windows updates it own as well as the default bootloader for a disk, it should be fine. Or at the very least it’s so much easier to just go to the firmware setup and change it back without having to reinstall LILO/syslinux/GRUB.

I’m running Arch. My laptop (MSI GT76 Titan) has 3 nvme and 1 SATA drive connector. So I have the nvme set up for Linux and the SATA for windows because: why not?

I mainly use Windows for… nothing these days. I try to remember to boot to it to update it every couple months. But I haven’t actually DONE anything in Windows in a while. I use Steam in Linux and play games there like Jedi Survivor, The Last of Us, Stray, Control, Hitman, … without issue. No need for Windows for me.

I’ve found that the only way to dual boot reliably is to have windows installed on a separate, dedicated drive, and to keep all drives used by Linux air-gapped from the windows drive. Fast start and hibernate must also be disabled within windows to prevent it from putting hardware in an undefined state.

That being said, I haven’t actually found any regular use for the windows install in years. mostly just keep it around as a sort of backup failsafe, or just in case there is a game that refuses to work in Linux. 99 times out of 100 it simply just collects dust.

Haven’t had a problem since I started using Linux full time in 2019 but I rarely boot to Windows (usually once every few months to update it). I have W10 and Kinoite (openSUSE before that) installed on separate SSDs. I used 2 EFI partitions (which I make backups of from time to time) on the respective drives the OSs are installed on.

No issues, as long as you have two separate drives. In worst case, you have to change your boot settings in UEFI, after a kernel update.

But I failed setting up Windows and Linux, both with drive encryption on one single SSD. I guess my failing prevented me from locking myself out of the system.

I use a lot of Windows, but I usually end up wiping the Windows partition to free space within six months, when I dual boot.

The performance is so much better on Linux on the same hardware, I just don’t boot to Windows, unless it’s the only OS that I have installed.

I’ve been dual booting Windows/Linux for 4 years on the same drive - no issues whatsoever.

I think as long as you use two separate boot EFI partitions, you’re fine.

Ever since I switched to UEFI boot, Windows has never taken over the bootloader. With MBR, it happened all the damn time and was super annoying. I think as long as you’re not relying on the default/fallback UEFI boot location you’ll be fine.

deleted by creator

I don’t recall Windows ever touching linux bootloader but I imagine it could if you had it scan & repair any potential boot problems. Installing any OS can result in bootloader being changed so I’ve always installed Windows first & then Linux, especially if only have a single drive. When dual booting with dedicated drive for each OS I install in the same order but I change the drive boot order in BIOS between installs as well. After installs are done I leave drive boot order so Linux bootloader is default. I can change the drive boot order if I ever have a need to use Windows bootloader.