Two ssds is when you need to run stuff on windows that requires the bare metal.
Windows needs to be contained, controlled and told who is the boss, I suggest using Tiny11 or MicroXP in a VM for stuff that can't run in wine.
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo
in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Two ssds is when you need to run stuff on windows that requires the bare metal.
Windows needs to be contained, controlled and told who is the boss, I suggest using Tiny11 or MicroXP in a VM for stuff that can't run in wine.
Windows actually works better in a vm on Linux than on bare metal. And it's got a much smaller chance of breaking my PC that way too.
Both my drives are the same Linux distro, I have Windows and MacOS in a VM when I need them, and Windows To Go for rare cases where I actually need to boot win11.
I have three ssd and none of them boot windows. I do have a windows vm (and macos too) in virt-manager in case I need it, but I haven't boot them for about a year.
I have two ssds for raid1 boot,it's very nice
just wish my bios would stop making phantom uefi boot entries every boot
I haven't used my Windows drive in almost a year now, Thinking about throwing another distro on there right now.
I went out and bought a very cheap external SSD. Windows is not touching my physical hardware on the bare metal.
I have a real simple solution that involves not windows
Secure boot Linux bootloader Kernel update
Hear me out: Class action lawsuit
Heard you and that wouldnโt fly. Just like youโre not supposed to run Windows on mission critical systems like nuclear reactors (seriously, check the EULA), running multiple operating systems side by side is most likely out of a supported configuration and โuse at your own riskโ. Youโd have zero standing or less for any sort of lawsuit.
But just because it is in the EULA doesn't make it legal. At a time where big tech is being kept under a microscope for antitrust regulation, I'd say that an OS that actively destroys other competing OSes on the machine it is installed on should be considered an unfair anti-competitor tactic.
Never trusted this setup to begin with because I didn't trust Microsoft and I'm not all that capable or want to take time to sort this stuff out on a regular basis.
So I just setup my ThinkPad laptop with two removable SSDs and I just swap one or the other whenever I need. The drive is easily switched, from power down, remove drive, insert other drive and restart only takes about two minutes.
I'm not going to risk messing up my setup because two operating systems can't work with one another.
Besides I seldom switch, I use Windows if I really have to about three or four times a year.
Wine wonโt work?
I really wish Excel would work on wine. It's the only reason I do occasionally fire up windows on my duel boot. (And no the open source / browser based spreadsheet options don't always suffice, brilliant as they are).
I recently had this issue needing to run Excel macros. I ended up using Oracle Virtualbox to run Windows from inside linux. Even more linuxey is using Proxmox to run your Windows VMs but that's a bit more of a faff.
Don't use virtualbox, instead use virt-manager (KVM). KVM is faster and doesn't do awful stuff to their users.
With UEFI itโs waaayyyy less bad than it used to be. There is no more MBR in the traditional sense for windows to clobber. Windows and Linux can share an UEFI boot partition both dropping in their appropriate boot binaries.
Even if you install Linux and Windows on separate devices, unless you do something strange they will share the same UEFI boot partition.
Personally, I do 2 separate UEFI boot partitions. Grub is the default which can select the windows boot partition. Then Windows can do whatever it wants to it's own boot partition.
By something strange, I assume you mean installing Windows on a disk with the other disks disconnected so Windows will create its EFI partition on that disk (since it's dumb and will create EFI partition on the first disk it finds, even if it's an HDD). Though UEFI doesn't mind, will still list all the bootloaders from different disks without any problems. You can even unplug and plug them as you wish, it still won't be corrupted this way.
Man, when I first messed around with Linux I hosed the MBR more times than I can remember. Either through Windows smashing it with an update, or my dumb ass doing stupid shit in gparted.
Pretty sure I was able to recover the important files somehow, but my parents banished me to the old family desktop for that pretty quick.
Me too. Lol. It was almost a right of passage for people at the time.
Easy solution if you only have one SSD: instead of installing Windows as your second OS, install a different Linux distro.
i use a different drive for my windows installation because that happened to often,
and i swear it once managed to wipe the bootloader on the linux drive.
i have no idea how it did that,
but i avoided starting windows using the grub entry since then.
Having two drives is sometimes not enough, either. I have no idea why, but anytime Windows installs for the first time or goes through a major update (not the small security patches, but the periodic feature releases) there's a random D20 dice throw to determine if it will randomly decide to create the bootloader and recovery partitions in another drive, even though your main installation isn't there.
I kid you not, Windows 10 once decided that my external SSD enclosure was the best place to put the bootloader.
This happened to me! Did an update, unplugged my eSATA and BAM! Can't find bootloader. I literally, physically facepalmed when I realized what happened. At least the old one still worked from the primary.
I've done a ton of Linux updates and this has never happened to me once (yet).
Pfft, even 2 separate ssds for dual booting doesnt stop this from happening to me -___-
On the plus side, this is the first i recall hearing of someone encountering the same issue, so i guess i dont feel as alone now.
Windows has a lovely โfeatureโ where it installs the bootloader on a secondary drive if thereโs one connected. It doesnโt install it on drive 1 and drive 2, just drive 2. I always disconnect all secondary drives before installing windows for this very reason.
That said you can configure the windows bootloader to recognize your Linux (or grub) and just use that to manage booting two OSes and itโs less likely to not destroy things.
it stopped happening to me after i stopped using the grub entry to boot windows.
i now use my mainboards boot menu to select the windows entry when i need to boot it
Is that actually easily fixable? Was planning to go dual-boot soon on my laptop and haven't even considered this scenario.
My old thinkpads have this great feature where the hard drive is easilly accessible on the side, so I leave the cover off and just swap the drive to boot into a different os
iirc the last time it happened to me, i just needed to fix the uefi entry which wasnt that bad.
(just remember to have a usb stick with a live image ready)
if it were to overwrite your bootloader that would be a way harder fix.
i dont remember if the second ever happend to me