this post was submitted on 14 Dec 2025
1096 points (98.8% liked)

linuxmemes

28505 readers
941 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    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.

    founded 2 years ago
    MODERATORS
    zephyr@lemmy.world
    rtxn@lemmy.world
    1096
    Not paying attention in the Grub menu (sopuli.xyz)
    submitted 6 days ago by bleistift2@sopuli.xyz to c/linuxmemes@lemmy.world
    129 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] cley_faye@lemmy.world 6 points 6 days ago (1 children)

    That's not a thing it can do in grub. It could do it with UEFI entries, but these days windows is not the biggest culprit of that. I had it happen on a BIOS update, where it simply nuked all stored entries, and the windows one is always checked as part of the standard.

    [–] Pika@sh.itjust.works 9 points 6 days ago* (last edited 6 days ago) (1 children)

    Yeah, I was gonna say I dual boot and I can't recall the last time that Windows nuked my UEFI bootloader.

    But back when Windows still did BIOS boot, it was like every major release without fail.

    edit: Rewreading your post it sounds like you meant updating the BIOS as a whole and not BIOS boot, so that's my bad. Yeah, I definitely haven't seen your circumstance, I had that happen consistently before Microsoft embraced the UEFI style booting

    [–] Don_alForno@feddit.org 1 points 6 days ago (1 children)

    I definitely had windows make some change at least twice that skipped grub on subsequent boots altogether.

    [–] Pika@sh.itjust.works 1 points 4 days ago

    So did I up until windows 10, which makes sense because my laptop that had run windows 8.1 had been upgraded from Windows 7 and had the issue every time it seems to have a version release. My windows 10 system was a factory install since I switched to a PC instead of a laptop at that time, and as such ran UEFI out of the box, I haven't had any issue with windows nuking a boot partition since.

    I'm assuming it's because bios boot still uses an MBR which means the actual boot record is at the beginning of the disk, which windows also tries to use for recovery and its boot. With GPT setups like how UEFI requires, there's a dedicated partition that is used instead for storing EFI files, so it allows for a much clearer co-existence.

    Basically if you are running a UEFI system, there's no excuse for Windows to actually nuke grub anymore, because the entire reason it was nuking it in the first place was it was overwriting the MBR at the beginning of the disk so the system no longer knew where grub was. With UEFI the system boot would be the UEFI loader -> windows loader or grub (or like how my system is brokenly setup UEFI -> grub -> windows because I like the traditional style of selecting windows from grub)