Windows 10 and 11 Wont Boot, How To Fix UEFI Partition

CyberCPU Tech · 2.4M views · 2023 · 19:30

Open on YouTube

Operating systems & kernelsTesting, debugging & developer toolstutorial

Why Super User recommends it

Super User users link it when answering or discussing Windows boot failures where the BCD or EFI partition needs to be rebuilt, such as after installing another OS.

Recommended by 1 people across 1 different months, 2023 to 2024.

What it is

A step-by-step tutorial from the CyberCPU Tech channel on rebuilding a broken UEFI/GPT bootloader on Windows 10 and 11. It walks through diskpart to assign a letter to the EFI partition, formatting it as FAT32, and regenerating boot files with bcdboot.

What people said

Recommends Joke · 2023-10 · Super User · on “Can I boot back into Windows 10 after installing Windows 11 on a separate drive?”

I had the same issue. I upgraded to Windows 11 but I had some important windows encrypted files on my machine. However, I managed to solve it. So the root issue is that the BCD file in the UEFI partition only points to the Windows 11 install. To fix this I followed this video: [this video] I noticed in Windows 11 that my drive letters changed, but in the windows 10 recovery console they were the old letters. Ended up regenerating the EFI folder (following the video above) pointing to my old C: drive. Currently haven't changed the BSD back to Windows 11 or looked into dual booting yet, but likely the steps will be similar but using the windows 11 installer instead

Cites meowington · 2023-11 · Super User · on “windows 10 BCD issue [UPDATE 11/3/23]”

Relevant specs: GPT format, ASUS Q503U (laptop 2016), UEFI, main drive is NTFS, boot drive partition is FAT32 First, the status of my hard drive seems okay-ish when I've checked the status of it through crystal disk and other means. I do plan to swap my HDD for an SSD when I can get this sucker running again and run a checkdisk, sfc and dism scan when I have access to even open safe mode. So leading to my current situation, all of a sudden one day my computer just went into recovery environment and didn't ever stop. The error I kept getting was something among the lines of "windows could not start properly" with no error code. I've been trying all sort of commands and nothing worked and then

Cites meowington · 2023-11 · Super User · on “windows 10 BCD issue [UPDATE 11/3/23]”

@Gantendo sorry I put the video in a link but it doesn't seem to be showing. The video is this [this video] as for the unreadable mess I'm trying my best I'm not too knowledgeable and just wrote what I found from my research, sorry. Let me know what you need cleared up please.

Cites xtian · 2024-01 · Super User · on “How does Windows BCDEdit work with multiple drives?”

BCDEdit lets you edit [LINK] , add and delete [LINK] boot options for Windows (10/11). Doing the work to understand UEFI I found good video explaining the big picture of UEFI [LINK] and two videos explaining how to fix [this video] the efi partition [LINK] . However, neither of these videos show a system with multiple drives. Following a post on SU [LINK] , I found this command for BCDEdit, bcdedit /enum all which shows both of my drive's efi partition data. How is this possible since the BCD data is installed in a partition on each drive. Please confirm if BCDEdit does indeed work to identify and manage all connected drives.

Cites RokeJulianLockhart · 2024-12 · Super User · on “How to restore a Windows Boot Loader entry (removed by installation of another OS) to my UEFI GUI (and GRUB2)?”

Problem I have an installation of Windows 11 (Build 27754, from the Canary channel [LINK] ) which was installed alongside a Fedora 41 KDE Spin installation (upgraded from F40, which it was installed as). Recently, that F41 installation became unbootable [LINK] (because an --offline dnf update did not correctly apply, rendering systemd-journald unable to invoke, outside the rescue kernel). To remediate this: I wrote Fedora-KDE-Live-x86_64-41-1.4.iso [LINK] (from [LINK] ) to a SANDISK USB-A (presumably USB2.0) storage device, via FedoraMediaWriter-win64-5.1.3.exe [LINK] . I replaced that F41 installation [LINK] with another Fedora 41 KDE Spin installation. All disk management in Anaconda was e