BCD is damaged, the PC won't start, assistance required to resolve BCD issue
BCD is damaged, the PC won't start, assistance required to resolve BCD issue
I attempted to transfer Windows from my old HDD to a new SSD. Rushing through the process, I didn’t verify I was booting from the SSD first. After removing the Windows image from the HDD, I tried to start from the SSD but it wouldn’t boot. The system reported an I/O error and couldn’t power on. Once I created a Windows installation tool on another machine, I booted from USB using the creation media and Windows recognized the SSD. Still, every installation attempt ended with the same error—mostly 0x000000f. When I tried to fix it in the command prompt, it warned about a corrupt BCD/MBR. The error messages changed occasionally, sometimes pointing to boot files or the EFI directory. I’ve used Bootrec before, but it didn’t resolve the issue. I also ran attrib and ren commands without success. I’m seeking guidance, as I’ve followed many online tutorials. Attached are photos from the process. NOTE: I managed to rebuild the boot files from a hidden 100MB partition on the SSD, but after exiting and trying to boot, the same error appeared. Updated May 4, 2023 by Cgmstan Added more details
You might attempt a portable Macrium version and run the boot repair tool. If that fails, manually adjusting the BCD or partitions could introduce further complications. As a fallback, consider swapping to a different SSD or HDD (not the one with your files) and installing Windows fresh on that new drive. Then use AOMEI Partition Assistant to replace the primary partition with your data. Afterward, clone the contents from the other drive to the SSD and run a Macrium boot fix if needed. Always verify functionality before deleting again.
It's really messed up now because the boot is damaged, there are missing files or errors, and the original drive was completely erased. The best approach is to grab the original Windows boot image, download it or save it as a disc, then copy the boot files from there into your saved operating system image where the boot files are stored. Merge them together. If your drive doesn't have the same files from the Windows download or disc, just add those missing ones manually and merge them. Restart with the drive containing your image as the first boot device and check if it loads properly. Good luck!
Both storage devices have been cleaned up, and the HDD was taken off power after I removed the operating system. I don’t have any connection to the information stored on either drive. The SSD underwent several formatting steps during this process to ensure it wasn’t completely set up. Windows installs on the SSD, but bootrec fails to detect Windows when trying to fix the BCD.
Both storage devices have been cleaned up, and the HDD was taken off power after I removed the operating system. There’s nothing attached to the data on either drive. The SSD underwent several formatting steps during this process to ensure it wasn’t completely done. Windows installs on the SSD, but bootrec fails to recognize Windows when trying to fix the BCD with bootrec.
Use Bootrec.exe in the Windows Recovery Environment to resolve boot problems. Microsoft Support notes that similar fixes have been needed before, such as after a faulty Windows update or when Signature Driver Enforcement was accidentally enabled. The advanced startup settings might help get you to Windows, and the 100MB space is likely the EFI partition—guides exist for rebuilding it. I’ve had to perform this during disaster recovery when the EFI partition wasn’t restored.
I’m ready to give it a shot! Losing data on any drive isn’t a big deal. The SSD has been completely erased several times during fixes. The HDD is unplugged and cleared of the three Windows partitions, though personal files remain. I’m open to wiping the HDD and reinstalling Windows there instead of the SSD, and if that works, I can try again. If not, I’ll stick with the SSD as storage.
Right, I do believe the efi partition is that hidden volume. I think maybe the efi partition has the boot files or some of them. When I attempted to bcdboot, I chose the efi partition as the drive, and it was successful in creating new BCD files, but attempting to boot right after did not work and gave the same errors and such
The EFI partition seems quite ordinary—it mainly handles basic mapping tasks. When I rebuilt it, I used a bare metal SDR without copying the EFI partition. After running some commands in cmd, I was able to boot normally once it was set up. It’s hard to find a detailed guide, but I found some useful info on diskpart.com.