Jump to content

  • 0

\boot\bcd error


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?

Share this post

Link to post
Share on other sites

Recommended Posts

  • 0

I've configured a WDS server on Server 2008 R2. I've set the response policy to respond to all, I've configured DHCP correctly but when I do a PXE boot from some clients PC `s get the Following error,


PXE-T04: Access Violation

PXE-E36: Error received from TFTP server

PXE-M0F: Exiting PXE ROM

Share this post

Link to post
Share on other sites

  • 0

here's something interesting and i need help with.


In the reg, under HKLM\SOFTWARE\Microsoft\CCM\Logging\SMSPXE the key 'LogPath' is set to 'SMSPXE.log'


No full path, and no file can be located.


If I change the path, say, to 'C:\Logs\SMSPXE.log', and then reboot the server OR simply restart the WDS service, it changes the path back to the original key.


So, i cannot troubleshoot my Boot\BCD error because I have to log to reference. Any ideas?

Share this post

Link to post
Share on other sites

  • 0

We hit this issue recently when we went from a setup where the WDS server and clients were on the same subnet to one where they are on separate subnets. As our set had a Cisco router between the two subnets we resolved the issue by also adding the WDS server IP to the Cisco IP Helper-Address (in addition to MS's recommendations)

Share this post

Link to post
Share on other sites

Join the conversation

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

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...