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.
this post was submitted on 04 Jun 2025
1297 points (98.8% liked)
linuxmemes
25629 readers
821 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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 figures
We 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
My windows ssd died about 2 weeks ago, but I was dual booting.
Took out the windows drive, slapped in a new one and I was no longer getting failed smart checks.
Happy to say that the windows drive that died was replaced with a new 990β¦ thatβll be more storage for my Fedora Plasma system instead of getting windows 10 reinstalled. Win 11 was never a consideration but I did want to keep 10 around for as long as I could.
c'est la vie
I literally had the same thing happen to me last week. I'm done with windows. Hello ubuntu
I actually had a Linux update do this once when it updated grub. Took a bit to fix but nothing was lost.
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.
I don't even boot windows anymore and it still takes over the first boot spot randomly.