Windows 10 error code BCD indicates a specific technical issue.

B

Black_Boyz
Member

66

01-12-2016, 02:37 AM

#1

Hey there, I'm facing a major issue with my PC. The boot sector got corrupted without any clear reason, and all my troubleshooting attempts didn't help. I've tried fixing it with various commands like bootrec, fixmbr, fixboot, rebuildbcd, bcdedit, and sfc, but nothing worked. Now I can still access my files using a live CD. If anyone can assist, I'd really appreciate it!

T

Tigrio
Member

54

01-12-2016, 03:54 AM

#2

Transfer all file types to the entire solid disk and set up Windows from zero.

L

los_dos
Member

50

01-13-2016, 03:53 AM

#3

I’d like to try, but there’s a lot of details here for work.

A

anonymous300
Member

63

01-20-2016, 08:37 PM

#4

I’ve been curious about whether it’s feasible to reinstall Windows from scratch and then swap the brand-new empty NTFS drive for an older one, essentially cloning the previous setup. Could that approach succeed?

A

atom_razor
Member

139

01-22-2016, 01:32 AM

#5

Consider your description carefully before proceeding.

O

omerneao111
Member

140

01-25-2016, 06:01 AM

#6

I noticed the error code shifting from 0xc0000098 to 0xc0000034—it’s worth checking if it matters. There are several partitions I’m unsure about, so creating a new one isn’t straightforward. You have three recovery partitions: two primary and one reserved.

T

Teddy_bear202
Member

180

01-25-2016, 09:10 PM

#7

Start a fresh BCD hive by using the Emergency Boot Kit. Select Mount & Boot Center from the main menu. Remove your outdated corrupted hive beforehand, or rename it to restore it later if needed.

J

JopperMan
Member

121

01-26-2016, 02:21 AM

#8

I’d really like to cover the cost, though I’m not sure it’ll be possible—at least it should locate the bootloader.

0

0sKHD
Member

226

01-30-2016, 03:48 PM

#9

Do you have a Windows installation available? In that setup you can launch a command prompt by pressing Shift + F10. Make sure to disconnect any additional drives like USB or external storage first. Execute these steps: diskpart sel disk 0 list vol You should now see something similar to this: In my case Volume 2 is the system partition. By default, it doesn’t have a mount point. Discover which partition holds your system drive. In Windows 10 it may not even be named "System," but usually it’s the one around 100–200 MB (Windows 10 tends to be bigger). It’s also typically the only Fat32 volume. Once you identify the correct volume, use DISKPART to select volume 2 and assign it a letter (S for example). The system drive now has a mount point. Proceed with bcdboot C:\Windows /S S: /F all. If the command completes successfully, new boot files have been generated from the windir data. You can attempt to start the system now.

S

Supa_MoMo
Junior Member

17

01-30-2016, 09:01 PM

#10

Typically when Windows fails to boot, the issue lies with the System or EFI partition, not the Windows partition itself. The System partition can be rebuilt, but it's best to use DISM to save the Windows partition as a .wim file, then clean the drive, repartition using GPT, and apply the image to a fresh NTFS partition.