Windows PE 5.x boot problem

balubeto · May 7, 2015

I noticed a very curious detail:

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

Code:

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:

Code:

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 avoid that the {7619dcc9-fafe-11d9-b411-000476eba25f} identifier is construed as the {default} alias in the device and osdevice elements?

Thanks

Bye

balubeto · May 12, 2015

Now, my procedure is as follows:

Code:

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

KYHI · May 12, 2015

KYHI said:
Add Quotes " " to the efi command lines..

But I am pretty sure that will modify both the Bootmgr and Bootmgr.efi files..

the only other issue you may need to adjust for is within this folder > EFI\BOOT
View attachment 61227

check the folder listed above - x86 uefi boot is not very common..

balubeto · May 13, 2015

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

KYHI · May 13, 2015

please post a pic of the files in this folder > EFI\BOOT

balubeto · May 13, 2015

KYHI said:
please post a pic of the files in this folder > EFI\BOOT

The contents of the \EFI\Boot directory is:

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

Thanks

Bye

balubeto · May 13, 2015

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

KYHI · May 13, 2015

Since x86 UEFI booting is very uncommon (except for with Atom Processors)

I am unloading the winpe I created to dropbox > https://www.dropbox.com/s/31v8zub83tafanr/WinPE.zip?dl=0
You will notice two Source Folders - x86 and x64 copy your correct "Boot.wim" into each folder
Note: You renamed boot.wim(s) = I renamed Folder(s)

Happy Testing!!
Let me know how you make out

By the way in my sig below - is a customized WinPE - it called Win81SE

balubeto · May 14, 2015

KYHI said:
Since x86 UEFI booting is very uncommon (except for with Atom Processors)

I am unloading the winpe I created to dropbox > https://www.dropbox.com/s/31v8zub83tafanr/WinPE.zip?dl=0
You will notice two Source Folders - x86 and x64 copy your correct "Boot.wim" into each folder
Note: You renamed boot.wim(s) = I renamed Folder(s)

Happy Testing!!
Let me know how you make out

By the way in my sig below - is a customized WinPE - it called Win81SE

I downloaded this WinPE.

Now, using only the Microsoft utilities, how do I create an ISO image and create a bootable USB stick?

By chance, you know the proper procedure to create this WinPE 32/64 bit because I want to know it?

Thanks

Bye

balubeto · May 14, 2015

To create an iso that works in any case, I thought to rename the two Efisys.bin in efisys_x32.bin and efisys_x64.bin and then use the command

Code:

oscdimg -o -u2 -udfver102 -bootdata:3#p0,e,b"<Windows_PE_Path>\Boot_files\etfsboot.com"#pEF,e,b"<Windows_PE_Path>\Boot_files\efisys_x32.bin"#pEF,e,b"<Windows_PE_Path>\Boot_files\efisys_x64.bin" "<Windows_PE_Path>\x32-x64" "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"

to create the ISO.

For you, with this method, I can reach my goal?

Thanks

Bye

KYHI · May 14, 2015

I have no clue what you are asking? all the configuring has been done for you already...

balubeto · May 14, 2015

KYHI said:
I have no clue what you are asking? all the configuring has been done for you already...

I have no more understanding nothing.
Following my procedure, if I create my iso with the command

Code:

oscdimg -o -u2 -udfver102 -bootdata:3#p0,e,b"<Windows_PE_Path>\Boot_files\etfsboot.com"#pEF,e,b"<Windows_PE_Path>\Boot_files\efisys_x32.bin"#pEF,e,b"<Windows_PE_Path>\Boot_files\efisys_x64.bin" "<Windows_PE_Path>\x32-x64" "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"

you can boot it even on the 64 bit computers with the UEFI?

Instead, how did you create your WinPE that you made me download?

Thanks

Bye

KYHI · May 14, 2015

here is the full WinPE.iso > https://www.dropbox.com/s/y1tsi53jqsl44vd/WinPE.iso?dl=0

Using ADK and I edited the BCD
MakeWinPEMedia /ISO C:\WinPE C:\WinPE\WinPE.iso

copype x86 C:\WinPE_x86
MakeWinPEMedia /UFD C:\WinPE_x86 K:
MakeWinPEMedia /ISO C:\WinPE_x86 C:\WinPE_x86\WinPEx86.iso

copype amd64 C:\WinPE_amd64
MakeWinPEMedia /UFD C:\WinPE_amd64 K:
MakeWinPEMedia /ISO C:\winpe_amd64 C:\winpe_amd64\WinPEx64.iso

balubeto · May 14, 2015

KYHI said:
here is the full WinPE.iso > https://www.dropbox.com/s/y1tsi53jqsl44vd/WinPE.iso?dl=0

Your WinPE.iso does not boot on any type of computer. Why?

Thanks

Bye

KYHI · May 14, 2015

Yes, it does.. Both Legacy and UEFI..

What you do with the ISO > burn it to CD or Copy the ISO contents (files) to usb stick?

balubeto · May 14, 2015

KYHI said:
here is the full WinPE.iso > https://www.dropbox.com/s/y1tsi53jqsl44vd/WinPE.iso?dl=0

I recreated your iso with command

Code:

oscdimg -o -u2 -udfver102 -bootdata:3#p0,e,b"<Windows_PE_Path>\Boot_files\etfsboot.com"#pEF,e,b"<Windows_PE_Path>\Boot_files\efisys_x32.bin"#pEF,e,b"<Windows_PE_Path>\Boot_files\efisys_x64.bin" "<Windows_PE_Path>\x32-x64" "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"

to create it.

Now, it does not boot with 32 bit computer with the UEFI. Why?

Thanks

Bye

KYHI · May 14, 2015

Why??? are you doing that..

That command creates an iso with boot files - the boot files are already present - you are just overwriting them..

KYHI · May 14, 2015

Now, it does not boot with 32 bit computer with the UEFI. Why?

32Bit UEFI is not supported, unless it has an ATOM cpu

KYHI · May 14, 2015

Or make two WinPE versions - they use 3 different files - one of them is the bootmgr.efi

balubeto · May 14, 2015

KYHI said:
Yes, it does.. Both Legacy and UEFI..

What you do with the ISO > burn it to CD or Copy the ISO contents (files) to usb stick?

I created an iso CD.

Thanks

Bye

Windows PE 5.x boot problem

Member

My Computer

Member

My Computer

Well-Known Member

My Computer

Member

My Computer

Well-Known Member

My Computer

Member

My Computer

Member

My Computer

Well-Known Member

My Computer

Member

My Computer

Member

My Computer

Well-Known Member

My Computer

Member

My Computer

Well-Known Member

My Computer

Member

My Computer

Well-Known Member

My Computer

Member

My Computer

Well-Known Member

My Computer

Well-Known Member

My Computer

Well-Known Member

My Computer

Member

My Computer