- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
cross-posted from: https://discuss.tchncs.de/post/38448230
Source (Furaffinity)
You must log in or register to comment.
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.
To be fair, windows does save its license key on ROM. It writes to the read-only memory. So it could.
Installing Linux is so simple nowadays that fixing the bootloader is a level higher now
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…
It always sucks dual booting in my experience. It’s an exercise in balancing maintenance and disk space management between two operating systems. You’re always likely patching if you actively switch between them.
I think it’s usually better to choose one and virtualize the other. I’d rather choose Linux + Windows VM than the other way around.
Sadly VMs don’t work with the Anti-Cheat rootkits, one of the only reasons I still have Windows
Ah yes, the classic dual-boot woes
I have Linux and Windows on separate drives.
The trick is to have a second EFI partition. One for windows to destroy, and one for linux to enjoy.
Good old switcharoo
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?
ish. if your boot priority is set to windows first and it decides it needs to repair the bootloader it can wipe other oses from the boot order.
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).
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.
