Jump to content











Photo
- - - - -

Windows PE 5.x boot problem


  • Please log in to reply
85 replies to this topic

#1 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 03 May 2015 - 07:08 AM

Hi

 

With Windows ADK and its MakeWinPEMedia utility, I created an ISO image of Windows PE 5.x but when I start it, it does not boot.

 

His BCD is:

 

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>bcdedit /store "C:\Users\Public\Documents\Windows_PE\ISO_debug\x32-x64\Boot\BCD"
Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {551baeb5-f0aa-11e4-826f-000c29e7d067}
toolsdisplayorder       {memdiag}
timeout                 30
Windows Boot Loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot_x32.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Windows PE a 32 bit
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot_x32.wim,{default}
systemroot              \windows
detecthal               Yes
winpe                   Yes
ems                     No
Windows Boot Loader
-------------------
identifier              {551baeb5-f0aa-11e4-826f-000c29e7d067}
device                  ramdisk=[boot]\sources\boot_x64.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Windows PE a 64 bit
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot_x64.wim,{default}
systemroot              \windows
detecthal               Yes
winpe                   Yes
ems                     No
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>

 

Where am I wrong?

 

Thanks

 

Bye



#2 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 04 May 2015 - 07:18 AM

I created the iso image with MakePEMedia utility and put it on a CD.

Now, if I boot from CD with some computer (with BIOS or UEFI), I have only a black screen. Why?

Thanks

Bye



#3 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 04 May 2015 - 10:35 AM

I modified the BCD file:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>bcdedit /store "C:\Users\Public\Documents\Windows_PE\x32-x64\Media\Boot\BCD"
Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {dd8eca84-f241-11e4-826f-000c29e7d067}
toolsdisplayorder       {memdiag}
timeout                 30
displaybootmenu         Yes
Windows Boot Loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot_x32.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Windows PE a 32 bit
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot_x32.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No
Windows Boot Loader
-------------------
identifier              {dd8eca84-f241-11e4-826f-000c29e7d067}
device                  ramdisk=[boot]\sources\boot_x64.wim,{dd8eca84-f241-11e4-826f-000c29e7d067}
path                    \windows\system32\boot\winload.exe
description             Windows PE a 64 bit
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot_x64.wim,{dd8eca84-f241-11e4-826f-000c29e7d067}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>

but I have the same problem. Why?

Thanks

Bye

#4 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 04 May 2015 - 01:47 PM

 

 

Now, if I boot from CD with some computer (with BIOS or UEFI), I have only a black screen. Why?

 

 

Does that means the CD boots fine on some system and not on others ?. If that is the case, it could be a compatibility issue. "WinPE 5" is based on "Win8.1" and it may not boot on systems which can't run "Win8.1". Try "WinPE 3" on that systems. 



#5 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 08 May 2015 - 08:40 AM

I noticed a very curious detail:

If I visualize the contents of the original BCD, this is displayed:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>bcdedit /store "C:\Users\Public\Documents\Windows_PE\x32-x64\Media\EFI\Microsoft\Boot\BCD"
Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
flightsigning           Yes
default                 {default}
displayorder            {default}
toolsdisplayorder       {memdiag}
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
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>bcdedit /store "C:\Users\Public\Documents\Windows_PE\x32-x64\Media\EFI\Microsoft\Boot\BCD" /v
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
flightsigning           Yes
default                 {7619dcc9-fafe-11d9-b411-000476eba25f}
displayorder            {7619dcc9-fafe-11d9-b411-000476eba25f}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30
Windows Boot Loader
-------------------
identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.efi
description             Windows Setup
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>

When, however, I modify the device and osdevice elements, with the bcdedit /store "C:\Users\Public\Documents\Windows_PE\x32-x64\Media\EFI\microsoft\boot\BCD" /set {7619dcc9-fafe-11d9-b411-000476eba25f} device ramdisk=[boot]\sources\boot_x32.wim,{7619dcc9-fafe-11d9-b411-000476eba25f} and bcdedit /store "C:\Users\Public\Documents\Windows_PE\x32-x64\Media\EFI\microsoft\boot\BCD" /set {7619dcc9-fafe-11d9-b411-000476eba25f} osdevice ramdisk=[boot]\sources\boot_x32.wim,{7619dcc9-fafe-11d9-b411-000476eba25f} commands, the contents of the BCD is:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>bcdedit /store "C:\Users\Public\Documents\Windows_PE\x32-x64\Media\EFI\Microsoft\Boot\BCD"
Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
flightsigning           Yes
default                 {default}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30
Windows Boot Loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot_x32.wim,{default}
path                    \windows\system32\boot\winload.efi
description             Windows Setup
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot_x32.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>bcdedit /store "C:\Users\Public\Documents\Windows_PE\x32-x64\Media\EFI\Microsoft\Boot\BCD" /v
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
flightsigning           Yes
default                 {7619dcc9-fafe-11d9-b411-000476eba25f}
displayorder            {7619dcc9-fafe-11d9-b411-000476eba25f}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30
Windows Boot Loader
-------------------
identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
device                  ramdisk=[boot]\sources\boot_x32.wim,{7619dcc9-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.efi
description             Windows Setup
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                ramdisk=[boot]\sources\boot_x32.wim,{7619dcc9-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>

How do I prevent the {7619dcc9-fafe-11d9-b411-000476eba25f} identifier is replaced by his alias {default} in the device and osdevice elements?




My complete procedure is:

md "<Windows_PE_Path>"
md "<Windows_PE_Path>\x32-x64\Media"
md "<Windows_PE_Path>\ISO"
copype x86 "<Windows_PE_Path>\x32"
copype amd64 "<Windows_PE_Path>\x64"
MakeWinPEMedia /ISO "<Windows_PE_Path>\x32" "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
MakeWinPEMedia /ISO "<Windows_PE_Path>\x64" "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
robocopy "<Windows_PE_Path>\x32\fwfiles" "<Windows_PE_Path>\Boot_files"
rd "<Windows_PE_Path>\x32" /s /q
rd "<Windows_PE_Path>\x64" /s /q
powershell Mount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
powershell Get-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso" ^| Get-Volume
robocopy <Drive_Letter>:\ "<Windows_PE_Path>\x32-x64\Media" /e /a-:R
powershell Dismount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
ren "<Windows_PE_Path>\x32-x64\Media\sources\boot.wim" boot_x32.wim
powershell Mount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
powershell Get-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso" ^| Get-Volume
robocopy "<Drive_Letter>:\sources" "<Windows_PE_Path>\x32-x64\Media\sources" boot.wim
ren "<Windows_PE_Path>\x32-x64\Media\sources\boot.wim" boot_x64.wim
robocopy <Drive_Letter>:\EFI\Boot "<Windows_PE_Path>\x32-x64\Media\EFI\Boot" bootx64.efi
powershell Dismount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {default} description "<Windows_PE_x32_name>"
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /copy {default} /d "Windows_PE_x64_name>"
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /v
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> device ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> osdevice ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> device ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> osdevice ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>
bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {bootmgr} displaybootmenu true
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set {default} description "<Windows_PE_x32_name>"
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /copy {default} /d "Windows_PE_x64_name>"
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /v
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x32_ID> device ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x32_ID> osdevice ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x64_ID> device ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x64_ID> osdevice ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>
bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set {bootmgr} displaybootmenu true
robocopy "<Windows_PE_Path>\Boot_files" "<Windows_PE_Path>\x32-64\fwfile"
MakeWinPEMedia /iso "<Windows_PE_Path>\x32-x64" "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"
isoburn /Q <Drive_Letter>: "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"

Where am I wrong?

Thanks

Bye

#6 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 08 May 2015 - 03:54 PM

Windows Boot Loader
-------------------
identifier {default}
device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}

/set {7619dcc9-fafe-11d9-b411-000476eba25f} device ramdisk=[boot]\sources\boot_x32.wim,{7619dcc9-fafe-11d9-b411-000476eba25f}


What about
/set {default} device ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}

Or use the generic name {ramdiskoptions}
http://diddy.boot-la...#ramdiskoptions

#7 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 12 May 2015 - 05:57 PM

Now, my procedure is as follows:

 

1) md "<Windows_PE_Path>"
2) md "<Windows_PE_Path>\x32-x64\Media"
3) md "<Windows_PE_Path>\ISO"
4) copype x86 "<Windows_PE_Path>\x32"
5) copype amd64 "<Windows_PE_Path>\x64"
6) MakeWinPEMedia /ISO "<Windows_PE_Path>\x32" "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
7) MakeWinPEMedia /ISO "<Windows_PE_Path>\x64" "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
8) robocopy "<Windows_PE_Path>\x32\fwfiles" "<Windows_PE_Path>\Boot_files"
9) rd "<Windows_PE_Path>\x32" /s /q
10) rd "<Windows_PE_Path>\x64" /s /q
11) powershell Mount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
12) powershell Get-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso" ^| Get-Volume
13) robocopy <Drive_Letter>:\ "<Windows_PE_Path>\x32-x64\Media" /e /a-:R
14) powershell Dismount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
15) ren "<Windows_PE_Path>\x32-x64\Media\sources\boot.wim" boot_x32.wim
17) powershell Mount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
18) powershell Get-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso" ^| Get-Volume
19) robocopy <Drive_Letter>:\sources "<Windows_PE_Path>\x32-x64\Media\sources" boot.wim /a-:R
20) ren "<Windows_PE_Path>\x32-x64\Media\sources\boot.wim" boot_x64.wim
21) robocopy <Drive_Letter>:\EFI\Boot "<Windows_PE_Path>\x32-x64\Media\EFI\Boot" bootx64.efi /a-:R
22) powershell Dismount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
23) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" | find "device"
24) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {default} description "<Windows_PE_x32_name>"
25) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /copy {default} /d "Windows_PE_x64_name>"
26) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {default} device "ramdisk=[boot]\sources\boot_x32.wim,<Options_ID>"
27) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {default} osdevice "ramdisk=[boot]\sources\boot_x32.wim,<Options_ID>"
28) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> device "ramdisk=[boot]\sources\boot_x64.wim,<Options_ID>"
29) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> osdevice "ramdisk=[boot]\sources\boot_x64.wim,<Options_ID>"
30) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {bootmgr} displaybootmenu true
31) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD" /set {default} description "<Windows_PE_x32_name>"
32) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD" /copy {default} /d "Windows_PE_x64_name>"
33) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD" /set {default} device "ramdisk=[boot]\sources\boot_x32.wim,<Options_ID>"
34) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD" /set {default} osdevice "ramdisk=[boot]\sources\boot_x32.wim,<Options_ID>"
35) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD" /set <Windows_PE_x64_ID> device "ramdisk=[boot]\sources\boot_x64.wim,<Options_ID>"
36) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD" /set <Windows_PE_x64_ID> osdevice "ramdisk=[boot]\sources\boot_x64.wim,<Options_ID>"
37) bcdedit /store "<Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD" /set {bootmgr} displaybootmenu true
38) robocopy "<Windows_PE_Path>\Boot_files" "<Windows_PE_Path>\x32-64\fwfile"
39) MakeWinPEMedia /iso "<Windows_PE_Path>\x32-x64" "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"
40) isoburn /Q <Drive_Letter>: "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"

 

Windows PE 32/64 bit works properly with computers that have the BIOS; while with those that have the UEFI, the CD does not boot and the screen remains black. Why?

 

Thanks

 

Bye



#8 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 12 May 2015 - 07:05 PM

Windows PE 32/64 bit works properly with computers that have the BIOS; while with those that have the UEFI, the CD does not boot and the screen remains black.

I doubt MakeWinPEMedia at a multi boot dvd.
Use oscdimg to create the iso file https://technet.micr...y/hh824847.aspx

As for testing: use a default Efisys.bin

Next step: create a 2.88mb floppy image, include both bootia32.efi and bootx64.efi. Use this floppy image instead.

#9 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 13 May 2015 - 10:15 AM

After several attempts on different computer, I noticed that the only case in which the computer does not boot from my CD is the one in which this computer is a 64 bit with the UEFI.

So, how do I solve this problem ie how do I make this CD so that it starts even with the 64 bit computers with UEFI?

Thanks

Bye



#10 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1857 posts
  • Location:Nantes - France
  •  
    France

Posted 13 May 2015 - 10:19 AM

Hi,

 

Have you given a try to QuickPE?

I have had good success with booting X64 + UEFI.

 

Regards,

Erwan



#11 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 May 2015 - 02:56 PM

I noticed that the only case in which the computer does not boot from my CD is the one in which this computer is a 64 bit with the UEFI.

The EFI El Torito x64 boot loader file \efi\boot\bootx64.efi is missing.
Include the file <DVD>\efi\boot\bootx64.efi.

EFI El Torito uses a virtual floppy:
the file efisys.bin file at given condition: include \efi\boot\bootx64.efi to the floppy image.
Adjust the file efisys.bin before creating the final ISO image.

#12 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 13 May 2015 - 03:46 PM

The EFI El Torito x64 boot loader file \efi\boot\bootx64.efi is missing.
Include the file <DVD>\efi\boot\bootx64.efi.

EFI El Torito uses a virtual floppy:
the file efisys.bin file at given condition: include \efi\boot\bootx64.efi to the floppy image.
Adjust the file efisys.bin before creating the final ISO image.

 

The contents of the \EFI\Boot directory is:

k36s0p.jpg

 

Where did I go wrong? How come my CD does not start in the 64 bit computers with the UEFI?

 

Thanks

 

Bye



#13 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 May 2015 - 04:21 PM

The contents of the \EFI\Boot directory is:

The \EFI\Boot directory is NOT used at DVD boot.

Create a ISO image yourself
https://technet.micr...y/hh824847.aspx

Oscdimg -bootdata:2#p0,e,bEtfsboot.com#pEF,e,bEfisys.bin -u1 -udfver102 C:\winpe_amd64\media C:\winpe_amd64\winpeamd64.iso

Adjust names to your case.
And edit this referenced Efisys.bin file.

#14 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13330 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 May 2015 - 04:28 PM

Balubeto, you should try understanding and following the given suggestions.

Besides the given reference read ATTENTIVELY here:
http://www.msfn.org/...-of-oscdimgexe/
http://www.msfn.org/...m-bootable-usb/
https://support.micr...kb/947024/en-us

In a nutshell:

  • a BIOS booting CD/DVD uses "No emulation mode" and the no emulation bootsector is etfsboot.com
  • a EFI/UEFI booting CD/DVD uses El-Torito floppy emulation mode and the floppy emulation image is efisys.bin, and the EFI will look inside this image for either \EFI\BOOT\bootia32.efi OR \EFI\BOOT\bootx64.efi

A "normal" Windows DVD (which does not exist in dual mode 32/64) efysis.bin will contain only either  bootia32.efi OR bootx64.efi.

You need to create your own floppy image "efisys.bin" and put in it BOTH bootia32.efi AND bootx64.efi.

 

The standard "efisys.bin" is a 1.44 Mb floppy image, and the \EFI\BOOT\bootia32.efi in it is more than 1 Mb in size so you need a larger image (the suggested 2.88 Mb size is fine) to have enough space for both bootia32.efi AND bootx64.efi.

 

:duff:

Wonko



#15 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 13 May 2015 - 04:58 PM

Perhaps, I discovered the problem:

I noticed that the efisys.bin file of Windows PE 32 bit is different than 64 bit.

So, how do I create a CD of Windows PE 32/64 bit fully working? Or rather, how do I create a efisys.bin single file?

 

Thanks

 

Bye



#16 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13330 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 May 2015 - 05:30 PM

You did not seemingly "discovered" anything, this is what we have tried telling you till now.

 

The efisys.bin is a FLOPPY IMAGE.

 

Try opening it with 7-zip and explore the contents, the efisys.bin from a Windows 32 bit DVD will contain \EFI\BOOT\bootia32.efi whilst the efisys.bin from a Windows 64 bit DVD will contain \EFI\BOOT\bootx64.efi .

 

Do you understand what a floppy image is?

 

Do you know how to create one?

 

http://en.lmgtfy.com...y image 2.88 Mb

 

:duff:

Wonko

 

BTW, I see how you still have the old habits ...

https://social.techn...=w8itproinstall

http://www.windows-n...x-boot-problem/

http://www.eightforu...-problem-3.html



#17 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1857 posts
  • Location:Nantes - France
  •  
    France

Posted 13 May 2015 - 05:36 PM

You did not seemingly "discovered" anything, this is what we have tried telling you till now.

 

The efisys.bin is a FLOPPY IMAGE.

 

Try opening it with 7-zip and explore the contents, the efisys.bin from a Windows 32 bit DVD will contain \EFI\BOOT\bootia32.efi whilst the efisys.bin from a Windows 64 bit DVD will contain \EFI\BOOT\bootx64.efi .

 

Do you understand what a floppy image is?

 

Do you know how to create one?

 

http://en.lmgtfy.com...y image 2.88 Mb

 

:duff:

Wonko

 

BTW, I see how you still have the old habits ...

https://social.techn...=w8itproinstall

http://www.windows-n...x-boot-problem/

http://www.eightforu...-problem-3.html

 

efisys.bin opened with 7-zip

 

81OyF2Y.png

 

When building a winpe from a dvd/iso, I use the below path :

 

wimlib-imagex.exe extract %dest%\iso\sources\boot.wim 1 /Windows/Boot/DVD/EFI/en-US/efisys.bin --dest-dir=%dest%\iso\efi\microsoft\boot --nullglob
and i burn my iso this way :
 
call mkisofs.exe -iso-level 4 -l -R -UDF -D -volid "WINRE" -b boot/etfsboot.com -no-emul-boot -boot-load-size 8 -hide boot.catalog -eltorito-alt-boot -eltorito-platform efi -no-emul-boot -b efi/microsoft/boot/efisys.bin -o %dest%\winre.iso %dest%\iso
may be this can help Balubeto.


#18 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13330 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 May 2015 - 05:52 PM

may be this can help Balubeto.

 

Or maybe it can confuse him some more. :unsure:

 

Particularly because not all mkisofs.exe builds support some of those switches and at a probability level of 97.78% he will have an older one missing some switches (and you should know about this possible issue ;)), in any case (just to keep everything as together as possible):

http://reboot.pro/to...e-2#entry189483

 

 

:duff:

Wonko



#19 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 128 posts
  •  
    Italy

Posted 13 May 2015 - 06:03 PM

Sorry again but what is the proper procedure to create a efisys.bin single file in order to insert it the CD of Windows PE 32/64 bit with the command MakeWinPEMedia?

 

Thanks

 

Bye



#20 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1857 posts
  • Location:Nantes - France
  •  
    France

Posted 13 May 2015 - 06:07 PM

Sorry again but what is the proper procedure to create a efisys.bin single file in order to insert it the CD of Windows PE 32/64 bit with the command MakeWinPEMedia?

 

Thanks

 

Bye

 

You dont create this file.

You obtain it from the iso, dvd or waik/adk.

 

In  your case it is probably in <Windows_PE_Path>\x32\fwfiles and <Windows_PE_Path>\x64\fwfiles.

Or in <Windows_PE_Path>\Boot_files but you seem to copy only the x32 version in there, looking at your batch.

 

Then, since you seem to be using WAIK/ADK, dont use MakeWinPEMedia batch (as we dont know what it does...) but rather go straight for the oscdimg microsoft tool.

That tool has a command line parameters to point at your efisys.bin to make your ise UEFI compliant which is may be what is missing in MakeWinPEMedia .

 

As a whole, the issue might be the batch you are using? it requires knowledge which you may not have acquired yet?

Why not go for a simpler/proven to work tool which you can find out there?



#21 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 May 2015 - 06:36 PM

to create a efisys.bin single file

Remember the request is not supported by manufacturer.
The result may work or fail at real world.

Use ImDisk and create a 4 mb floppy image a:\
Format a: as FAT
copy files <DVD>\efi\boot\boot*.efi to a:\efi\boot\boot*.efi
save a: to a file efisys.bin

Luckily UEFI works at a lot of floppy images in real world.
 

with the command MakeWinPEMedia?

Try copy the file yourself before running efisys.bin

#22 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13330 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 May 2015 - 06:52 PM

Use ImDisk and create a 4 mb floppy image a:\

Wouldn't a 2.88 Mb image, 2949120 bytes in size, with a geometry of 80 Trks 2 Hds 36 Secs 512 B/S

http://www.911cd.net...indpost&p=91870

just like any of the 2.88 Mb ones in here:

http://en.lmgtfy.com...y image 2.88 Mb

i.e. here:

http://www.rmprepusb...orials/winimage

as you originally suggested:

 

 

Next step: create a 2.88mb floppy image, include both bootia32.efi and bootx64.efi. Use this floppy image instead.

 

do "better" (being surely El-Torito compatible?) :dubbio:

 

Or being it a "-eltorito-alt-boot -eltorito-platform efi" the geometry doesn't matter anymore? :unsure:

 

Good ol' BFI should do nicely:

http://www.nu2.nu/bfi/

 

:duff:

Wonko



#23 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 May 2015 - 07:22 PM

Wouldn't a 2.88 Mb image, 2949120 bytes in size, with a geometry of 80 Trks 2 Hds 36 Secs 512 B/S

do "better" (being surely El-Torito compatible?) :dubbio:

Yes, it a more traditional floppy image should work better.

However there is another issue:
floppy image bootx*.efi chainloads <DVD>\bootmgr.efi at DVD.
There are different x86 and x64 \bootmgr.efi, twice the same file names.
Hexediting bootx*.efi breaks secure boot.

floppy image bootx*.efi are different to <DVD>\efi\boot\bootx*.efi files.

Both <DVD>\efi\boot\bootx*.efi are bigger and won't match a 2.88 mb flopppy.

Using <DVD>\efi\boot\bootx*.efi as El Toriro boot is not supported by the manufacturer.
The Operating system manufacturer dosn't distribute multi x86 x64 ISO files.
Works in a lot of hardware cases, but will fail at some cases.

The implicit susggestion was a 2.88 floppy image with a default floppy image bootia86.efi, and a added <DVD>\efi\boot\bootx64.efi.
And a x86 <DVD>\bootmgr.efi file.
The result should work in more cases, bu won't be supportable from the outside.
To many files involved. Hence the other 4mb approach.
Do you like more confusion: a default floppy image x64, added a <DVD>\efi\boot\booti86.efi and a x64 <DVD>\bootmgr.efi file.

#24 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13330 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 13 May 2015 - 07:38 PM

Well, if 2.88 Mb is not enough, I would still go for one of the bigger sizes but still found El-Torito compliant such as a 5.76 Mb one, at least in theory it might have more chances.

Or use one of the available bigger sizes, but still El-Torito "0x03" compatible, list (just for the record) here:

http://www.msfn.org/...oppy-emulation/

http://www.msfn.org/...ation/?p=971170

 

 

:duff:

Wonko



#25 cdob

cdob

    Gold Member

  • Expert
  • 1314 posts

Posted 13 May 2015 - 09:15 PM

I would still go for one of the bigger sizes but still found El-Torito compliant such as a 5.76 Mb one,

This rings another old bell: http://bootcd.narod.ru/images_e.htm
The floppy images are available still.

UEFI 12.3.2.1 ISO-9660 and El Torito

EFI differs from “El Torito” “no emulation” mode in that it does not load the “no emulation” image into memory and jump to it.
EFI interprets the “no emulation” image as an EFI system partition.

There seems to be no restriction: a floppy image, a MBR hard disk image or a GPT hard disk image should work.
Even a fixed size VHD image should work. A powershell ISO aware OS, supports VHD out the box too.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users