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.
Back when I dual booted, I had the most success keeping Windows on a separate drive completely. After making the Linux drive the primary boot device, GRUB would pick it up and I'd be off to the races. I now just keep a Windows VM -- it's been much easier to deal with.
Boy howdy, you best keep that BitLocker key handy, though.
I'm not following, do you need the bitlocker key when Linux is on a separate disk? is there something extra you need to keep in mind compared to just running windows?
Just when recovering a windows partition encrypted with bitlocker.
I was going to dual boot, to kind of test the waters of using Linux as my primary. Then I heard there were is with Windows not wanting to play nice, so now I just run Linux.
And to be honest I don't actually know what any of the issues are, I didn't care enough to even search it. I just said Fuck Windows and moved on with my life.
Windows is literally designed to break multi-boot setups. Funny enough, multibooting on a Mac was never a big problem. Microsoft has more of a reason to cooperate here and they just canβt help themselves.
Setting a BIOS password stops Windows from fucking with most things in your boot partition, Iβd open-mouth kiss whomever told me that tip
I told you. Now kiss me (β Β β Λβ Β β Β³β Λβ )
This info would have been so fucking useful a decade or two ago
you mean that password function actually had a use this whole time?!?
Windows only in a VM.
That is the only way.
Always keep a backup of your boot partition, when dual booting with windows. I wouldnβt encourage a windows boot though
I have dual boot for long time already. Win 11 + Ubuntu. Although there was no any critical issues so far, except some mess up with internet connection on my ubuntu few times.
I dual boot grub+linux from a wholly separate drive set as the boot drive, windows boot loader is unused, untouched, isolated on the windows drive.
Windows update still broke grub.
Pull my hair out for a few hours trying to find a fix, about to try something but have to reboot one last time.
Everything is fine, back to normal.
Windows is the virus
I'm glad I've always kept Windows on a separate disk.
Mine still got fucked.
Just stop dual booting. This is self-inflicted harm. Setup a VM or find a native workaround.
I've been dualbooting for over a year now. Made sure each system has its own separate drive. I've noticed that every time I had to reinstall Linux, my windows boot entry is gone and then I can't access it no matter what I tried. Turned out installing Linux first then windows was my mistake. When installing windows while there is a Linux install, windows will see the EFI partition already there and just decides to share it, and doesn't create its own.
I found that out by accident while I was in windows' storage management. There was no efi partition. Took a whole day to find out how to create one on the same drive where windows is installed and removing the one it created on the Linux partition. It was so painful.
Bottomline, install windows first if you want to dualboot. After that, even if windows takes over the boot after an update, all it does is resets the boot sequence and makes it default to it. You'd just need to access the bios and reset the sequence to prioritize Linux. That's it
When installing windows while there is a Linux install, windows will see the EFI partition already there and just decides to share it, and doesnβt create its own.
That's what it's supposed to do, it's a plain FAT32 partition, the bootloaders are just files you put in there.
Part of the issue is that while a well-made motherboard will look for all bootloaders on the partition and present them as options in the firmware UI, bad ones will only look for a specific file (\EFI\BOOT\BOOTX64.EFI) and use that. For an OS to have a chance of booting on those boards it has to overwrite that file, blowing away whatever other bootloader was there before.
It's annoying, since Windows is mostly well behaved here (It puts the main copy of the bootloader at \EFI\Microsoft\Boot\bootmgfw.efi and Linux bootloaders can see that and offer it, the reverse isn't true) and can co-exist with Linux well (Well...), but manufacturers cutting corners causes more problems for everybody.
Literally the only boot drive issue I've ever had dual booting was when I somehow accidentally deleted the GRUB partition (I'm still not entirely sure how)
Grub lives on the drive with Linux, windows on an extra one, select which I wanna use on boot. Windows just updated like yesterday, rebooted right to GRUB no issue
User reports having lost his GRUB partition mysteriously
User says not to worry about Windows randomly removing GRUB partitions through Windows Updates
What the heck is the origin of this meme template? And am I the only one who thought this was Roger Stone?
I know this one weird trick to avoid this..
I actually had a Linux update do this once when it updated grub. Took a bit to fix but nothing was lost.
Easily solved. Just run mkfs_ext4 on the windows partition, and mount it as an additional filesystem.
man this meme is als old as windows 7 or has been recreated in exact this form over and over again, i am not sure witch of those
Put Windows and Linux on two separate physical drives and this will never happen
To my own surprise, it can happen.
Oh it absofuckinglutely happens. If you install Linux first then Windows, windows will see the boot partition and use it instead of creating its own. Install windows first on its own, then install Linux. How I know? Hmmmmm
that's why i just deleted my entire hard drive and installed mint on the whole thing