Don’t do it on a machine that holds valuable data or one that you need the machine to stay functional for work. I repeatedly fucked up my installation trying to get dual boot setup initially. Bootloader are easy to mess up. Even on a working installation, a Windows update would sometimes break the dual boot.
Its not difficult to set up a virtual machine inside your Linux installation. That way you don’t have to reboot and lose your other workflow to access your windows apps.
Or if you make two efi partitions, one for Linux and one that Windows uses. Then use the Probe Foreign OS in Linux to make a chainloader entry to windows. Set Linux as UEFI bootloader. Windows doesn’t know about the other partitions and leaves them alone.
And then fuck it up by pointing Linux at your windows EFI partition, end up with neither system bootable and make things worse as you panic and try to rush a fix without understanding what you’re doing.
If you’re new to how it all works and having a working machine is important, best to keep it simple and as separated as you can.
I’m also not convinced that “Windows doesn’t know about the other partitions”, that sounds like the kind of thing that’s true until it isn’t and it overwrites your Linux bootloader.
Not if you separate into two EFI partitions and set Linux one in your UEFI boot options. Windows only gets access when grub hands over boot to windows via a chainloader entry, windows only knows about its EFI. I have run it 8 years like this…after dealing with windows killing my first shared EFI.
Don’t do it on a machine that holds valuable data or one that you need the machine to stay functional for work. I repeatedly fucked up my installation trying to get dual boot setup initially. Bootloader are easy to mess up. Even on a working installation, a Windows update would sometimes break the dual boot.
Its not difficult to set up a virtual machine inside your Linux installation. That way you don’t have to reboot and lose your other workflow to access your windows apps.
If you can, dual boot by having each OS on a separate physical drive.
Or if you make two efi partitions, one for Linux and one that Windows uses. Then use the Probe Foreign OS in Linux to make a chainloader entry to windows. Set Linux as UEFI bootloader. Windows doesn’t know about the other partitions and leaves them alone.
This sounds more complicated than it probably is.
And then fuck it up by pointing Linux at your windows EFI partition, end up with neither system bootable and make things worse as you panic and try to rush a fix without understanding what you’re doing.
If you’re new to how it all works and having a working machine is important, best to keep it simple and as separated as you can.
I’m also not convinced that “Windows doesn’t know about the other partitions”, that sounds like the kind of thing that’s true until it isn’t and it overwrites your Linux bootloader.
Windows is notorious for wiping Linux parts off a shared drive
Not if you separate into two EFI partitions and set Linux one in your UEFI boot options. Windows only gets access when grub hands over boot to windows via a chainloader entry, windows only knows about its EFI. I have run it 8 years like this…after dealing with windows killing my first shared EFI.
Too much hassle, would never recommend that for beginners
That’s a fair point. And probably true on many distros.
This is what I was planning, I added a small nvme drive to my desktop to put Linux on