119
Windows just fucked up my bootloader...
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Apr 2024
119 points (93.4% liked)
Linux
48199 readers
1269 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I've spent the last two nights trying to rescue a windows installation from a rescue usb, and no amount of BCD recovery seems to help. It has forced me to take a closer look at the EFI partition, but even deleting it outright and recreating it from scratch still won't boot. I think there must be something corrupted and I should just give up and reinstall. That's windows for ya...
An example of something I just don't understand, after deleting and recreating the EFI partition, and using bcdboot to repopulate it, I now see two Windows Boot Manager BBS entries listed in BIOS. No idea why, no idea how to find out. One site said I must have multiple entries in my BCD, but bcdedit just shows the standard
{bootmgr}and{default}OS entries.