Skip to content

\boot\bcd error

Featured Replies

I am on a deadline and desperately needs some experienced help.

 

We have a Windows Server 2003 R2 w/ SP2 that we installed WDS on. This server is on a virtual machine and DHCP is on a seperate server.

 

DHCP options 66 and 67 have been set.

Option 67 is set to: \boot\x86\pxeboot.com

 

I had to set the options otherwise my client system would not obtain an ip address.

 

I opened the TFTP ports on the WDS server and the Server is running in native mode.

 

I used the boot.wim from AIK and we are trying to deploy a XP pro image. The image was captured using imagex.

 

When I boot my client system, I get the ip address from DHCP, I press F12 to network boot, and then I get this errror:

 

File: \boot\BCD

Status: 0xc000000f

Info: An error occurred while attempting to read the boot configuration data.

 

I have been stuck on this for a week and desperately need some insight.

 

I have viewed my default.BCD file and this is what is shows:

 

Windows Boot Manager

---------------------------

identifier {bootmgr}

inherit {dbgsettings}

timeout 30

 

Debugger Settings

---------------------

identifier {dbgsettings}

debugtype Serial

debugport 1

baudrate 115200

 

Device options

-----------------

identifier {68d9e51c-a129-4ee1-9725-2ab00a957daf}

ramdisksdidevice boot

ramdisksdipath \boot\boot.sdi

 

 

Is there something missing and how do I correct it?

is there a switch of any sort in between the server and client ? if so try removing it to rule out the switch...

 

secondly is the client also virtual or is it real, if it's real is it 32bit or 64bit ?

  • Author
is there a switch of any sort in between the server and client ? if so try removing it to rule out the switch...

 

secondly is the client also virtual or is it real, if it's real is it 32bit or 64bit ?

 

Yes there are multiple cisco switches between the client and the server. The client is real and I am trying to load 32bit XP.

  • Author
is option 66 pointing to the ip of the WDS server ?

 

have you tried setting option 67 to boot\x86\wdsnbp.com instead of your current value =?

 

 

Option 66 does point to the wds server.

I did try pointing option 67 to wdsnbp.com however it kept searching for x64 instead of x86.

  • Author
as a test point it to the X64 boot file

 

could be that the bios is reporting 64bit capable...

 

I changed Option 67 to \boot\x86\wdsnbp.com and then added a 64-bit boot.wim.

 

So far everything is looking good. Thank you so much for the added insight.

  • 2 months later...
I changed Option 67 to \boot\x86\wdsnbp.com and then added a 64-bit boot.wim.

 

So far everything is looking good. Thank you so much for the added insight.

 

I'm having the same exact issue on an older computer. I have my PXE service roll to except unknown computers and i've placed my task sequence in the 'unknown computers' collection.

 

At first I was getting the same error about \boot\bcd error so I tried your recommendation on adding 64bit drivers for testing. And now i'm getting an whole new error:

 

File: \WINDOWS\system32\boot\winload.exe

Status: 0x000035a

Info: Attempting to load a 64-bit application, however the CPU is not compatible with 64-bit mode.

 

I've tried every possible driver for this machine. Not sure if it's a driver related issue or a hardware issue with this computer.

 

any help with be appreciated.

 

Thanks again.

  • 7 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.