wimboot: WinPE cannot find \Boot\BCD

[mpiechotka]

I'm stuck. I see that files are loaded correctly:

Code:

wimboot : 51392 bytes [bzImage] [SELECTED] "rawbcd pause"
BCD : 262144 bytes [PXE-NBP] "BCD"
boot.sdi : 3170304 bytes "boot.sdi"
boot.wim : 176787265 bytes "boot.wim"


wimboot v2.6.0 -- Windows Imaging Format bootloader -- http://ipxe.org/wimboot

Command line: "rawbcd pause"
Using BCD via 0x7541f074 len 0x40000
Using boot.sdi via 0x75460078 len 0x306000
Using boot.wim via 0x75767078 len 0xa898f41
...found WIM file boot.wim
...patching boot.wim
...patching WIM header at [0x0,0xd0)
...found file "\Windows\Boot\PXE\bootmgr.exe"
Using bootmgr.exe via 0x434a0 len 0xaaf60
...extracted  bootmgr.exe
Emulating drive 0x83
Entering bootmgr.exe with parameters at 0x2c4e0

I got files from Windows 8.1 ADK.

I was able to boot Windows 7 installer itself instead of WinPE but it didn't found iSCSI drive.

[NiKiZe]

So winpe starts, but you have no network? (the windows 7 install is still winpe)
Or does Winpe not start at all? if so what does happen?

Where does the boot.wim come from, and what (if any) are the modifications to it?


My guess is that you have simply not initialized the network in winpe, or that you are missing network drivers, Which nic are you using in the test machine?

From another post of mine: http://forum.ipxe.org/showthread.php?tid...2#pid13472

use this inside winpe:

Code:

wpeinit
wpeutil WaitForNetwork
net start dnscache

ipconfig /all

to make sure everything is up in regards to network and see what the result is.

[mpiechotka]

boot.wim got from Win 7 install disk works but it does not list sanhook'ed disk. boot.wim got from ADK (Windows Assessment and Deployment Toolkit) 8.1 cannot find \Boot\BCD.

I'll update rest soon when I boot the machine from Win 7 install disk

(2017-09-05 20:48)NiKiZe Wrote:  So winpe starts, but you have no network? (the windows 7 install is still winpe)
Or does Winpe not start at all? if so what does happen?

Where does the boot.wim come from, and what (if any) are the modifications to it?


My guess is that you have simply not initialized the network in winpe, or that you are missing network drivers, Which nic are you using in the test machine?

From another post of mine: http://forum.ipxe.org/showthread.php?tid...2#pid13472

use this inside winpe:

Code:

wpeinit
wpeutil WaitForNetwork
net start dnscache

ipconfig /all

to make sure everything is up in regards to network and see what the result is.

[NiKiZe]

Start with checking if win7 has network at all, if not then it won't be able to connect to any iSCSI device either.

"8.1 cannot find \Boot\BCD."
What is the _exact_ error message you get, and when do you get it?

If there is any issue with your BCD file then I would suggest to test using the PXEBCD found at https://github.com/NiKiZe/wimboot-bcd
This is a minimal clean generic BCD.

[mpiechotka]

Hmm. I got now the same error in Windows 7.

---

(2017-09-05 21:51)NiKiZe Wrote:  "8.1 cannot find \Boot\BCD."
What is the _exact_ error message you get, and when do you get it?

Status. 0xc000000e
Info: The Boot Configuration is corrupted or missing (I haven't managed to copy it all before system autoreboot)

---

(2017-09-05 21:51)NiKiZe Wrote:  Start with checking if win7 has network at all, if not then it won't be able to connect to any iSCSI device either.

"8.1 cannot find \Boot\BCD."
What is the _exact_ error message you get, and when do you get it?

If there is any issue with your BCD file then I would suggest to test using the PXEBCD found at https://github.com/NiKiZe/wimboot-bcd
This is a minimal clean generic BCD.

The same error with PXEBCD.

[NiKiZe]

(2017-09-05 21:54)mpiechotka Wrote:  Status. 0xc000000e
Info: The Boot Configuration is corrupted or missing (I haven't managed to copy it all before system autoreboot)

Good now we have something to work with

I would start with checking that the same boot.wim works when put and booted via a USB device instead of via wimboot, Just to make sure the basic works.

[mpiechotka]

This seems to be a bug in wimboot as downgrading to 2.3.0 fixed problem. It looks like I need to add network driver as per wiki page.

[NiKiZe]

Downgrading wimboot would have nothing to do with the network driver.

Have you tried anything between 2.3.0 and 2.5.0?
Is 2.3.0 the most recent version of wimboot that works? and which issue does it solve if you downgrade?
(someone else will need to reproduce this issue to be able to fix it, so non confusing steps needed to reproduce this would be really great)

[mpiechotka]

(2017-09-06 19:44)NiKiZe Wrote:  Downgrading wimboot would have nothing to do with the network driver.
Have you tried anything between 2.3.0 and 2.5.0?
Is 2.3.0 the most recent version of wimboot that works? and which issue does it solve if you downgrade?
(someone else will need to reproduce this issue to be able to fix it, so non confusing steps needed to reproduce this would be really great)

But has to do with \Boot\BCD error:

• On Wimboot 2.3.0 both boots without problem
• On Wimboot 2.5.0 both fail with error in bootmgr.exe
• On unspecified version I had at the beginning Windows 7 booted but Windows PE 8.1 failed
  

For the installation I will create a separate thread to not confuse things.

[mpiechotka]

I cannot reproduce it any longer on 2.6.