Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.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.
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'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.
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.
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.
windows removed my grub bootloader at least 3 times even once after i started using seperate drives.
ive never had the opposite happen.