Help troubleshoot BCDboot error from WinPE 3.0

[Tripredacus]

Board: Intel DX79SI. UEFI Boot is disabled. BIOS is latest version.

PXE Boot to WinPE 3.0 x64, tested Windows 7 Home Premium x64.

AHCI = OK

IDE = OK

RAID using RAID1 = OK

Here are the scenarios that cause a problem.

1. Failure if OS volume is RAID0, BCDBoot returns error: "Failure when attempting to copy boot files" using this command:

bcdboot c:\windows

2. Failure if OS volume is RAID0, BCDBoot completes successfully, BOOTMGR is missing error on restart using this command:

bcdboot c:\windows /s c:

3. Same as #2 but different command:

bcdboot c:\windows /s c: /l en-us

4. Unexpected result if OS volume is on RAID0, BCDBoot completes successfully, Set OS Partition to Active. Result is OS boots but System Reserved partition is assigned a drive letter.

I've already got some emails out about this problem, but was wondering what I could possibly try or run from WinPE x64 to test and maybe find out what the problem is?

Update: 7PRO64 does not work on RAID1 or RAID0. I have tried getting a new BCDBOOT.EXE as well as building a boot image using WinPE 3.1 x64 from the WAIK Supplemental ISO.

Edited April 24, 2012 by Tripredacus
update for OS tested

[Tripredacus]

DX79SI would not boot if drive type set to IDE. It would POST, allowing access to the BIOS. If set to IDE, could not boot off HDD, LAN or USB. AHCI worked fine. In light of that, shelved that board for now.

DX79TO using single-part deployment on RAID1 using Windows 7 Home Premium x64 resulted in Bootmgr error.

DZ68BC using multi-part deployment on AHCI using Windows 7 Home Premium x86 resulted in Bootmgr error.

Using Windows 7 Home Premium x64 multi-part image worked!

Deploy 7HP32 multi-part using 32bit WinPE 2.1 resulted in Bootmgr error.

Update on DX79SI, using new BIOS update, 7PRO64 multi-part image on RAID0 works!

Update

DX79SI works with 7HP64 on RAID0.

DZ68BC BCD information seems incorrect! Example of BCD after 7HP32 deployment, but before reboot:

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  locate=unknown
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {a8b25961-0782-11e0-b9d9-e0dcc4139c77}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  locate=\Windows\system32\winload.exe
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-us
inherit                 {bootloadersettings}
osdevice                locate=\Windows
systemroot              \Windows
resumeobject            {a8b25961-0782-11e0-b9d9-e0dcc4139c77}
nx                      OptIn

This appears normal for the state of BCD after deployment but before Windows boots the first time. I will test using x64 and see what its BCD looks like post deployment (since x64 works on the DZ68BC).

Update2

BCD using x64 is the same, except a different resumeobject GUID.

Wanted to test recovery on DX79SI since the OS seemed to be working. After not getting the OS to activate (7PRO64 on RAID1) did a reimage. But then got a Bootmgr error. Reimage same OS, same error.

Edited May 2, 2012 by Tripredacus