this post was submitted on 04 Jun 2025
1265 points (98.8% liked)

linuxmemes

25381 readers
956 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.
  • 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
     
    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 5 points 2 days ago (2 children)

    I'll do you one better. Do you know what a windows update killed on my multi boot system? It killed the windows bootloader. I'm working on a permanent solution to fixing this bootloader fudgery.

    load more comments (2 replies)
    [–] [email protected] 5 points 2 days ago* (last edited 2 days ago)

    Pre-UEFI they were fighting over the boot sector, sure, but now that everything is more well defined, and every OS can read the FAT32 ESP? Never seen it...

    At worst the UEFI boot entry is replaced. There are some really shitty UEFI implementations out there which only want to load \efi\microsoft\boot\bootx64.efi or \efi\boot\bootx64.efi, or keep resetting you back to those.

    Assuming you were dumped into Windows suddenly, you can check if you have the necessary boot entries still with bcdedit and its firmware option

    bcdedit /enum firmware
    

    If you just have a broken order you can fix it with

    bcdedit /set {fwbootmgr} displayorder {<GUID>} /addfirst
    

    If you actually need a new entry for Linux it's a bit more annyoing, you need to copy one of the windows entries, and then modify it.

    bcdedit /copy {<GUID1>} /d "Fedora"
    bcdedit /set {<GUID2>} path \EFI\FEDORA\SHIM.EFI
    bcdedit /set {fwbootmgr} displayorder {<GUID2>} /addfirst
    

    Where GUID1 is a suitable entry from windows, and GUID2 is the one you get back from the copy command as the identifier of the new entry. Of course you will have to adjust the description and the path according to your distro and where it puts its shim, or the grub efi, depending on which you'd like to start.

    Edit: Using DiskGenius might be a little more comfortable.

    [–] [email protected] 5 points 2 days ago (6 children)

    Imagine dual booting in 2025.

    load more comments (6 replies)
    [–] [email protected] 6 points 3 days ago (3 children)

    Variations of this meme get posted every week, but I've never experienced it, despite having had tens of grub updates murder-suicide the Windows boot loader and grub itself across five or six different machines. Thankfully, it's pretty easy to rebuild a Windows boot partition, but the frequency that I'm hit with this problem is one of the major reasons I avoid using Linux. Eventually I'm going to have to switch, but that's driven mainly by Windows getting worse rather than any of the pain points I've had when trying to switch full time in the past having been fixed.

    [–] [email protected] 7 points 3 days ago

    windows removed my grub bootloader at least 3 times even once after i started using seperate drives.

    ive never had the opposite happen.

    [–] [email protected] 3 points 3 days ago* (last edited 3 days ago)

    Why do you not avoid using Windows instead?

    load more comments (1 replies)
    [–] [email protected] 4 points 3 days ago (1 children)

    Has never happened to me since using systemd-boot

    load more comments (1 replies)
    [–] [email protected] 2 points 2 days ago

    Never happened to me, but then again, most of the shit I see people complain windows does has never been my experience either.

    [–] [email protected] 2 points 2 days ago

    I don't even boot windows anymore and it still takes over the first boot spot randomly.

    load more comments
    view more: β€Ή prev next β€Ί