1482
submitted 1 year ago by drbi@lemmy.world to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] MTK@lemmy.world 13 points 1 year ago

It tends to happen if you are not using the windows bootloader (GRUB for example) but if you use the windows bootloader it should be fine

[-] themusicman@lemmy.world 13 points 1 year ago

Oh it just changes the bootloader? That's not a big deal. Easy to fix from any live usb.

Also, for any distro hoppers out there... Do yourself a favour and put Ventoy on a USB. You can thank me later

With EFI systems this doesn't matter. It was an issue with the legacy BIOS bootloader systems about a decade ago though.

[-] JackbyDev@programming.dev 2 points 1 year ago

I don't remember if Windows updates would cause it but installing Windows second definitely would. Likewise, I think upgrading (from say Windows 7 to 10) might. Basically Windows is just like "this MBR? It's actually mine, thanks." With no option to not erase it.

EFI systems don't use the MBR. Windows will default to using the whole disk if you don't use the "advanced" button, but so will most linux distro installers.

[-] JackbyDev@programming.dev 1 points 1 year ago

I'm talking about BIOS, yeah, sorry if it was unclear. My 2009 CPU is still hanging on. Barely.

[-] MTK@lemmy.world 1 points 1 year ago

Pretty sure it happened to me on UEFI as well

this post was submitted on 27 Sep 2023
1482 points (95.9% liked)

linuxmemes

20705 readers
620 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS