building ISO after customizing unattend image causes BCD error 0xc000000e on EFI system

when use iso file created after issuing makewinpemedia command odd error on efi system i'm trying load.

however, when use unaltered installation cd, have no problems.

i need configure autounattend install.wim, packages, drivers, etc... , (so build new iso).  happens either amd64 winpe custom build , ws2012 x64 attempts.

what missing...  bcd files (matter of fact, files in efi directory structure) identical original installation iso.

still trying figure out wrong.. here contents of bcd used on iso:

windows boot manager
--------------------
identifier              {bootmgr}
description             windows boot manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
timeout                 30

windows boot loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.efi
description             windows setup
locale                  en-us
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
detecthal               yes
winpe                   yes
ems                     yes

ok (major edit)

so, bit more details here.  have been trying setup uefi "lab" of sorts familarize myself more how works , creating autounattended installation cd headless server utilizes efi.  have been using virtualbox emulate efi firmware, seems experimental (as of version 4.2.2r81494).  i'm able start setup process manually via believe nvram boot manager , executing bootx64.efi fs1; however, installation hangs on first logo load screen after several minutes.

when entering efi internal shell, found odd...  there 2 alias (i'm guessing fs0: nvram?)

uefi interactive shell v2.0.  uefi v2.31 (edk ii, 0x00010000).  revision 1.02

fs0: alias(s): f9a:;blk0

       pciroot (0x0)/pci (0x1f,0x1)/ata(0x0)

fs1: alias(s) :cd9a0:;blk1:

       pciroot (0x0)/pci (0x1f,0x1)/ata(0x0)/cdrom(0x0)

blk2: alias(s):

      pciroot(0x0)/pci (0x1f,0x2)/sata(0x0,0x0,0x0)

fs1 iso build, blk2 vhd, fs0 ?  (i guessing shell or ram disk boot manager)

strange thing see different bootx64.efi versions follows:

fs0: \efi\boot\bootx64.efi  (00/00/000 00:00   1,354,480 bytes)  - causes 0xc000000e  error

fs1: \efi\boot\bootx64.efi  (7/25/2012 21:57  1,108,208 bytes)  - launches, cd detected, install fails, slow , appears hang badly

have no idea why bootx64.efi file in fs0 correct size (in bytes) 1 found on iso, yet has no date/time stamp , fails execute, while version in fs1 (supposedly cd) has correct date/time stamp, wrong size (in bytes) 1 in iso, yet loads , fails install...

so, have scrapped continuing battle virtualbox , got vmware player (adjusted firmware efi) , far have had 0 problems launching efi cd build. >.<

Windows Server  >  Windows Server 2012 Setup