Ah yes, the classic dual-boot woes
The supposed update that fixed it (windows update) broke it worse than ever, took me quite awhile to figure it out.
If you’re lucky, it’s still on the disk and you just need to “repair” the bootloader.
If not, well, that traumatised Mr Incredible pastiche might be at least a circle of hell too pleasant.
You have backups, right?
There’s no way Windows would just access non-readable partition, and do anything with it, let alone delete it. No operating system does this.
Replacing the bootloader is of course much more likely, but the general rule is that if you can manage to install Linux, you probably can follow basic instructions to fix GRUB or whatever your bootloader is.
There’s no way Windows would just access non-readable partition
I knew that was true back in the day, but I haven’t tried dual booting in a long, long time. Also, I wouldn’t put it past Microsoft’s current incarnation to “accidentally” decide that that “empty” partition would be great for virtual memory and the hibernation image.
Oh Windows knows this is the EFI partition, there is a flag for that. Windows just doesn’t care when it decides to nuke your bootloader with its own…
And yes, it’s still happening…
Installing Linux is so simple nowadays that fixing the bootloader is a level higher now
To be fair, windows does save its license key on ROM. It writes to the read-only memory. So it could.
The trick is to have a second EFI partition. One for windows to destroy, and one for linux to enjoy.
deleted by creator
This should not happen unless you booted into windows and ran an update.
Ladies and gentleman we got em
Well, but you could update windows, then reboot but boot into linux. That means the windows update can’t fully complete yet. Now if you start up your PC the next day and it boots into Windows by default, the update process will continue.
Same thing. You’d have to boot into windows at some point.
I have Linux and Windows on separate drives.
I that why I never relate to this issue? I’ve had a dual boot setup for years by now and have always been able to choose either windows or Linux at startup, but they are on separate drives
Yeah, Windows has a habit of borking bootloaders whenever it’s on a partitioned drive.
Gaming. Want a quick round in a pause? Mount error: go boot Windows to fix it. But i have multiple tools and sessions and stuff open…
And Windows still can’t handle anything reliable.
Me too, the windows drive is in the garage
*garBage
With super cheap SSD’s and motherboards with multiple m.2 slots, there’s rarely an excuse not to have different drives anymore. Laptops might be an exception.
Some gaming laptops come with a second nvme slot. Mine does and I did exactly this. Was wayyy simpler.
Don’t dual boot, flatten and rebuild.
“B-but my gaaaaaamez!!!”
I constantly tell people the dangers of dual booting. They don’t listen and then it breaks.
I constantly tell people the remedy of the dangers of dual booting, using a separate drive for Linux. They sometimes listen and then have a dual boot system that doesn’t break.
Eh, Windows has broken grub before even if it’s on a separate drive, some Windows update did that last year.
Can that actually happen like this? If Windows killed the bootloader wouldn’t that mean that you couldn’t boot into Kubuntu either? Or can it somehow kill the bootloader when the PC is turned off?
What definitely did happen to me is I booted into windows, shut down, on the next startup there was no more grub menu, just instant boot into windows. (Separate physical drives).
Grub had/has this issue every time windows does a cumulative monthly update. Systemd doesn’t have this issue.
While microsoft has admitted to bugs causing exactly this scenario. I personally have a stabe 6 months with dual-boot. And only updating cachos once a month or every two weeks has been fine. The server and rog ally exclusively runs linux.
Separate ssd’s lets go
