this post was submitted on 02 Jul 2026
928 points (95.7% liked)

linuxmemes

31957 readers
652 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 3 years ago
    MODERATORS
    zephyr@lemmy.world
    rtxn@lemmy.world
    928
    OP doesn’t like Linux (lemmy.world)
    submitted 1 day ago by cannedtuna@lemmy.world to c/linuxmemes@lemmy.world
    275 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Theoriginalthon@lemmy.world 2 points 1 day ago (1 children)

    Every time I've come across this it's because windows restore points have been disabled for some reason, or the only restore point happens to be from when it was first installed. Other times it's been when there are 2 hard drives installed and it somehow shits the bed and installs the bootloader to one and the os to the other, or upgrades to one disk but leaves a half valid install on the other, then boots the old install. Generally getting confused about multiple disks

    [–] Pika@sh.itjust.works 1 points 14 hours ago

    I had this issue when migrating to a new larger NVME a few years back, where there was technically 2 EFI partitions and it would fight which one was correct. I eventually just had to randomly nuke an EFI cause I wasn't sure which one it was using.

    Then my most recent was with the secure boot key update, windows would fail to update. By that I mean it would install updates, and then fail to update and rollback. So it never became unbootable, it just would stupidly keep trying the same update. So I investigated into it.

    I found that when I did work about a year ago I expanded my EFI partition. Since EFI's can't be expanded that involved backing the partition up, nuking it then making a larger partition.

    I apparently never marked the partition as an "EFI" ID when I did this, so it was marked EFI by type, but not via type id.

    I never caught the issue because grub didn't care that it lacked the proper typing, it knew where windows was, the EFI was "proper" in concept that it contained the right files to boot, and windows while didn't accept it as an EFI, also didn't care it didn't actually have an EFI so it would just silently fail on any update events to it. It wasn't until the update was pushed that forced the master key to change that it actually started to show signs of failing.

    I was amazed that there was no warnings at all that the currently booted system has no valid EFI partition. It was insane it was even able to boot in the first place.