Combine x64 & x86 in one ISO? (UEFI & BIOS)

Hi,

Thanks to the Win8.1SE package, I can create separate versions of x86 and x64 WinPE ISOs. Now I'd like to ask how to combine both versions in one ISO? And I hope that this combined ISO can boot to the x86 version on 32-bit UEFI system (Asus T100), x64 version on 64-bit UEFI system (Venue 11)?

Thanks in advance :)

Hi

Combine 32 and 64 for Legacy BIOS boot is quiet easy. You can use the "Multi-Wim" script to automate the combining process. However UEFI is different beast. The boot files of UEFI PEs are dependent on the architecture. For example, "Bootmgr.efi" is diffeent for 64 and 32. I am afraid that combining the two is not possible.

And I hope that this combined ISO can boot to the x86 version on 32-bit UEFI system (Asus T100), x64 version on 64-bit UEFI system (Venue 11)?

There is no optical drive included.
How do you boot a ISO file? Do you write a CD, DVD or other?
Do you use a USB optical drive?

What about a USB storage disk?

create a 2.88 mb floppy image and hexedit files:
\EFI\BOOT\BOOTIA32.EFI: bootmgr.efi to bootmgr.x86
\EFI\BOOT\BOOTX64.EFI:  bootmgr.efi to bootmgr.x64

Use this floppy image as EFI boot image.

Add both versions to \efi\microsoft\boot\bcd and create entries for renamed boot.wim.

\Programs folder name is used at x86 and x64 PE. How to solve this?
Incldue all files to boot.wim?

create a 2.88 mb floppy image and hexedit files:
\EFI\BOOT\BOOTIA32.EFI: bootmgr.efi to bootmgr.x86
\EFI\BOOT\BOOTX64.EFI:  bootmgr.efi to bootmgr.x64

That is not going to work probably without turning off "SecureBoot" on the target machine. I never had a chance to work with a tablet PC but from what i have read, there seems to be tablet PCs which doesn't allow to turn off "SecureBoot" at all. Anyway, Venue11 seems to support disable/enable that.

http://www.dell.com/support/Article/bb/en/bbdhs1/644809/EN

Thanks for your answers, cdob and anshad.

Yes, I use a USB optical drive. I asked about ISO simply because it's the default output of many tools/guides on these WinPE stuffs, so I hope if I stick to the default it'll be easier to understand. ISO/DVD is also write-protected, whereas files on a USB stick might be affected by many factors.

I don't mind about turning off Secure Boot, as both of my hybrid tablets allow that.

For apps in \Programs, could we just use their 32bit versions, as 64bit Win8.1SE project now has support for WoW64?

Now I'm reading posts/articles/guides about these PE stuffs to have better understanding. I've also found one guy who made a Win8.1_AIO ISO and *specifically stated* that[1]:

In MBR Mode, It will boot & install on 32bit and 64bit processors.
 In 32bit UEFI Mode, It will boot & install on 32bit processors. 32bit UEFI Firmware needed for UEFI Boot
 In 64bit UEFI Mode, It will boot & install on 64bit processors. 64bit UEFI Firmware needed for UEFI Boot

I downloaded his ISO and saw that there was only one bootmgr.efi. Do you think he used a different method from cdob's method?

Edit: link to an illegal torrent removed

Hi

As i said earlier, my reply is completely based on what i have read. I wish i could test a 32 and 64 UEFI combo but the lack of hardware is an issue for me. "cdob" knows better than me about booting so i hope he will help you find a way around.

Anyway, you should remove that torrent link you posted. It is strictly against the forum rule to provide download links for downloading pirated Windows. The last thing we wanted here is trouble from Microsoft legal team.

Have you tried the DVD on your tablet machines ?. Is it boot fine on both tablets as expected ?.

Actually, as I don't have a dual-layer (DVD9) optical drive, I don't know how I can test the default ISO method. And I don't have my Asus T100 by me until this weekend. However, after testing on my Venue with the USB created based on his guide, I think he's doing right. So I'll report later after I do a full test.

Sorry for the torrent link. If anybody's interested, you can google for "kickass BigReds".

Oh, it turns out my USB optical drive has a logo of "DVD+RW DL"  Well, I think I just need to buy a DVD9 disc.

Hi ChrisR

Thanks for the valuable input and VMWare testing  . I think the whole process can be automated if following the below steps ( not tested - just an idea ). If successful, the resulting ISO/USB can be used with either 32 or 64 bit UEFI firmwares.

1. Create x86 version of Win8PE as usual and rename the WIM to "Bootx86.wim".

2. Before building the x64 version, change "Boot Manager" to "Auto" in "Main Configuration".

3.In "Multi-Wim" script ( Other OS --> Multi-Wim ), choose the renamed "Bootx86.wim" to be added to the boot selection menu ( "Enable 2 Wim file" option ). Also make sure to put a tick mark on "EFI Compatible" optional check box.


4. Extract "Bootia32.efi" file from "EFI\Boot" folder of x86 ISO. Now go to "Finals --> Create ISO" script and select the option "Include files in ISO Root CD". Then press "Put files for Root CD Here" button to open the "Workbench--> Common--> RootCD" folder.  Create a folder named "EFI" there and then create a subfolder named "Boot" inside it. Copy the "Bootia32.efi" file to the sub folder "Boot" which we created earlier.

5. Deselect the option "Add bootfix.bin" on the "Create ISO" script and build the PE.

If i assumed correctly, the resulting ISO will contain entries to select either x86 or x64 version of Win8PE on both "Boot\BCD" ( for MBR ) and "EFI\Microsoft\Boot\BCD" ( for UEFI ). "Bootia32.efi" file will be used as the boot loader for x86 UEFI and "Bootx64.efi" for x64 firmware.

 

Hi anshad,

Yep, it should be good like that, for both "create ISO" and "Copy To USB device"

Some addition:
for ISO creation, we need to create a boot image file with bootia32.efi and bootx64.efi Inside in efi\boot folder.
The image can be created with the great imdisk 



It seems that we can rename the created image .img in efisys.bin or efisys_noprompt.bin (following the selected choice "Press any key...") for the ISO creation with oscdimg or mkisofs,
the created efisys*.bin can be added also in RootCD in efi\microsoft\boot folder (step 4). Thus no need to change "Create ISO" plugin which use efisys*.bin boot image by default.
I tried like that and it starts well in both 32/64 bit UEFI Virtual Machine.

To see, how to do this automatically with a batch, probably.

loveleeyoungae, If these steps are OK for you, It would be good to get feedback on real computers with secure boot ON  .

#
In step 2, It is also possible to use Grub4Dos or SysLinux for the MBR boot, if wished, the BCD bootmgr is shown after the menu choice.
For efi, we need to choose the WinPE 32 or 64 bit BCD enrty which must be the same architecture as the computer.

To automate, the addition of bootia32.efi and the creation of efisys*.bin (if bootia32 and bootx64 exist) could be added In Multi-Wim plugin.
In postconfig, I changed the BCD description "Windows setup" => %ProjectName% x86 or x64 (+UEFI for efi bcd)

Amazing, ChrisR! I was starting to figure out the method, and your post already showed EXACT things we need to do.

I confirm that the combined WinPE ISO created by using your guide can perform universal boot on REAL 32&64bit BIOS&UEFI systems (Secure Boot ON too)!   

If you search around the web without looking at the posts/articles dates, you will believe that we can't combine 32&64bit UEFI boot files because there is no unified bootmgr.efi, or there is no 32bit UEFI, or you can't boot 32bit OS on UEFI systems, etc... (Especially when some posts were written by well-known guys). But obviously, things have improved :)
And I can say that, after the past weeks searching around, ChrisR was the first person to post all necessary info for this kind of universal boot. I just needed to read another tutorial originally for BIOS boot from Deploymentresearch, and I could perform all necessary commands to create a universal WinPE successfully.

That said, I've just found out my 32bit UEFI Asus T100 actually has a 64bit Atom CPU! Now I understand a UEFI firmware is not related to the system architecture: 32bit UEFI does not only run on 32bit system, and actually it shouldn't[1]! Is that the reason why the bootmgr.efi & bootmgr from a Win8.1x64 can be the universal boot loader? 
I don't know. But if what BigReds says in his torrent description is true, his ISO can boot on his Acer W510P which is a 32bit UEFI on a 32bit Atom CPU! 
However, due to [1] blog post, maybe we wouldn't have new "32bit UEFI on 32bit CPU" systems from now. So, I think we can consider the issue solved :)

I haven't had the chance to try anshad's method and I don't really understand about the Grub4Dos part. I think I still have to learn more. Now I'm starting to think of combining this universal Win8.1SEPE with a Win8.1 AIO... 

Btw, what's your preferred/best methods to put this universal Win8.1SEPE on a USB? I tried a guide which uses BootIce to create and switch 2 partitions, but it takes much disk space because it needs to duplicate the WIM images on both partitions!

PS: For a side note, the Win8.1SEPE boots perfectly on my Dell Venue. I was very surprised that it has sounds and touch enabled! But it's strange that some apps (Opera, Serviwin, Explorer++...) don't respond to touch. I can touch to focus those apps, but that's all. And touch is not enabled on my Asus T100. But well, maybe I will have to post these issues in another thread 

[1]: http://mjg59.dreamwidth.org/26734.html

Hi 'loveleeyoungae'

Nice to see you here...

Can you please provide a Step by Step procedure of creating 'Win8.1PESE_x86_x64' ?

Congratulations for your success......

Thanks & Regards...

Amazing, ChrisR! I was starting to figure out the method, and your post already showed EXACT things we need to do.

I confirm that the combined WinPE ISO created by using your guide can perform universal boot on REAL 32&64bit BIOS&UEFI systems (Secure Boot ON too)!   

Great  Thanks for your return on REAL computers with Secure Boot ON   

I think the whole process can be automated if following the below steps

Multi-WIM can do it now in a way more or less automated 

1. Create the x86 version of Win8PE (Win8.1PE) with yours configurations, plugins.

2. Choose now your Windows 8/8.1 source 64 bit and before building go to the Multi-Wim plugin (OtherOS folder), select it.
    ps: You can choose the boot manager Auto for the standard startup or choose Grub4DOS, Isolinux for a Multi Boot MBR menu.
   
3. In Multi-Wim plugin, enable "2 WIM-File", "EFI compatible", enable also "add bootia32.efi..." and clic on the openDir button to Open %GlobalTemplates%\MultiWim directory (eg: D:\Win8.1SE\Workbench\Common\MultiWim)
   
4. From the previous building:
   - Copy Boot.wim from "sources" folder in %GlobalTemplates%\MultiWim and rename it in bootx86.wim
   - Copy bootia32.efi from efi\boot in this same folder %GlobalTemplates%\MultiWim
   - Also copy memtest.efi 32 bit from efi\microsoft\boot in %GlobalTemplates%\MultiWim and rename it in memtestx86.efi
   
In %GlobalTemplates%\MultiWim folder, you must have Bootx86.wim, Bootia32.dll and memtestx86.efi.


 
5. Now build the Win8PE x64
    It will use the previous 3 files, write the propre Boot Configuration Data (BCD) and create efisys.img image for the ISO creation.

You have now a "Universal" Win8PE ISO available for 32/64 bit BIOS and 32/64 bit UEFI systems 
And with "Copy To USB-Device" plugin, a USB Stick/disk (FAT32 required) compatible with 32&64bit BIOS&UEFI based computers 


Note: On a 32 or 64 bit UEFI computers, you must choose the BCD entry with the SAME architecture.
          A 32 bit Win8PE does not work on a 64 bit UEFI PC and vice versa.


download zMultiWim.7z
Edit: typo in Depend def, thank you Starla for seeing (reply #15 below).
The latest version of Multi-WIM plugin is on server

Thanks to ChrisR and others for this additional script.

I felt free to mention this thread in the forum of the German 'c't Notfall-Windows 2014'.
As I'm not (yet) allowed to post external links here, regard my post from 12/02/2014 02:00 h after following 'Forum' under Links on ct.de/yej2
There You will find additional CMDs

• #1_BUILD.cmd (in order to ensure that Win82SE82_Builder is started with administrator privileges)
  #2_PREPMULTI.cmd (in order to suppoert copying of three filles according to step 4).
  

The only trouble I had sometimes was when I tried to activate zMultiWin.script at the beginning of step 5. An error message appeard that a procedure/script 'n' could not be found and after that the build process stopped. Nothing was documented in the error log.
Same error happened when I tried to build an AiO with your november 2014 version modified by zMultiWim.script out of this thread.

Workaround:
When I changed 'Selected=False' under [Main] by an external editor (PsPad.exe) to 'Selected=True' before beginning step 5, no error occured and an AiO-ISO was created correctly. While editting the script I increased the value in %tmout%=10.

My OS: Win811-x64 ProWMC (fully patched)
Sources: Win811 ProWMC (x86 & x64)
Win81SE82_Builder.exe in both variants with identical hashes.

If further details are necessary don't hesitate to aks me.

Regards, Nemo

The only trouble I had sometimes was when I tried to activate zMultiWin.script at the beginning of step 5. An error message appeard that a procedure/script 'n' could not be found and after that the build process stopped. Nothing was documented in the error log.
Same error happened when I tried to build an AiO with your november 2014 version modified by zMultiWim.script out of this thread.

I think it is caused by line 15

Code: [Select]

Depend=                                       n

Assignation for "Depend" is empty in the version of zMultiWim.script in the current project index. Actually you can use the one in the current project index, because the script version that ChrisR posted in this thread just enables (sets to "True", "ticks" in the GUI)

- To use Other OS --> Multi-Wim script by default for the build (should be enabled *after* creating the x86 build, if following the anshad/ChrisR procedure)
- (In Multi-Wim script) Enable 2. WIM-File
- (In Multi-Wim script) Add bootia32.efi in x64 build or bootx64.efi in x86 build FOR dual boot 32/64 bit UEFI

so, by default, the script GUI setup looks like the pic attached by ChrisR.

Cheers.

Thank you Nemo for writing on Ct's forum, your batchs and the process to get a 32, 64 bits WinPESE compatible with BIOS and UEFI computers 
Their forum is mainly for worries, problems, all this is normal following the release to the general public.
It is good to also have constructive messages or those that appreciate the project 

I think it is caused by line 15

Yes, indeed, well seen Starla 
I removed the download above to avoid any confusion.
The latest version is on SE server and I just added a small fix for the "Open Dir" buttons.

@ChrisR:
Thanks for the new script. I had no time to test it til now. (MS' Patchday; do I have to say more?)
I posted a link to this thread and the corrected script in c't Magazine's forum and aksed Peter Siering, the author, to pin it.

Regards, Nemo

Thanks @ChrisR and everybody else who contributed!
I can confirm the steps above work for me to create a working 32/64 UEFI/BIOS Image. I tested on a 32 Bit UEFI Atom Tablet with Baytrail(Dell Venue 8 Pro) and a 64 Bit UEFI (Lenovo Thinkpad, Surface Pro 3, Dell 8600 Tower), all devices had Secure Boot enabled and worked great. These images were built using PE in RAM and Windows 8.1 with Update source ISO from MSDN.

I am still working on adding drivers for autorotation and touchscreen for the atom tablets, but that is a different issue. I also tested both 32 and 64 bit Legacy Boot and had no issues with 2 laptops and 4 desktops. Thank you for the detailed step by step instructions, it was very helpful and makes it easy to add to my multi-boot USB drive.

\efi\microsoft\boot\bcd

Code: [Select]

Gestionnaire de démarrage Windows
---------------------------------
identificateur          {bootmgr}
description             Windows Boot Manager
locale                  fr-FR
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {2e488718-de32-11dd-8808-005056a95ed2}
                        {2e488718-de32-11dd-8808-005056a95ef0}
                        {2e488718-de32-11dd-8808-005056a95ee0}
toolsdisplayorder       {memdiag}
timeout                 10
displaybootmenu         Yes

Chargeur de démarrage Windows
-----------------------------
identificateur          {default}
device                  ramdisk=[boot]\sources\bootx64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \Windows\system32\boot\winload.efi
description             Win8.1SE UEFI x64 (for 64bit UEFI PC only)
locale                  fr-FR
loadoptions             DISABLE_INTEGRITY_CHECKS
inherit                 {bootloadersettings}
nointegritychecks       Yes
osdevice                ramdisk=[boot]\sources\bootx64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \Windows
custom:250000c2         0
detecthal               Yes
winpe                   Yes
ems                     No

Chargeur de démarrage Windows
-----------------------------
identificateur          {2e488718-de32-11dd-8808-005056a95ed2}
device                  ramdisk=[boot]\sources\bootx86.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.efi
description             Win8.1SE UEFI x86 (for 32bit UEFI PC only)
locale                  fr-FR
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\bootx86.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
custom:250000c2         0
detecthal               Yes
winpe                   Yes
ems                     No

Chargeur de démarrage Windows
-----------------------------
identificateur          {2e488718-de32-11dd-8808-005056a95ef0}
device                  boot
path                    \efi\microsoft\boot\memtestx86.efi
description             Windows Memory Diagnostic (32bit UEFI)
locale                  fr-FR
inherit                 {7619dcc8-fafe-11d9-b411-000476eba25f}
osdevice                boot
systemroot              \Windows

Chargeur de démarrage Windows
-----------------------------
identificateur          {2e488718-de32-11dd-8808-005056a95ee0}
device                  boot
path                    \efi\microsoft\boot\memtestx64.efi
description             Windows Memory Diagnostic (64bit UEFI)
locale                  fr-FR
inherit                 {7619dcc8-fafe-11d9-b411-000476eba25f}
osdevice                boot
systemroot              \Windows

\Boot\bcd

Code: [Select]

Gestionnaire de démarrage Windows
---------------------------------
identificateur          {bootmgr}
description             Windows MBR Boot Manager
locale                  fr-FR
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {2e488718-de32-11dd-8808-005056a95ed2}
toolsdisplayorder       {memdiag}
timeout                 10
displaybootmenu         Yes

Chargeur de démarrage Windows
-----------------------------
identificateur          {default}
device                  ramdisk=[boot]\sources\bootx64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Win8.1SE x64
locale                  fr-FR
loadoptions             DISABLE_INTEGRITY_CHECKS
inherit                 {bootloadersettings}
nointegritychecks       Yes
osdevice                ramdisk=[boot]\sources\bootx64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
custom:250000c2         0
detecthal               Yes
winpe                   Yes
ems                     No

Chargeur de démarrage Windows
-----------------------------
identificateur          {2e488718-de32-11dd-8808-005056a95ed2}
device                  ramdisk=[boot]\sources\bootx86.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Win8.1SE x86
locale                  fr-FR
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\bootx86.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
custom:250000c2         0
detecthal               Yes
winpe                   Yes
ems                     No

ps:

Code: [Select]

loadoptions             DISABLE_INTEGRITY_CHECKS
nointegritychecks       Yes

are required for Win8.1SE x64 build

How to edit those bcd files? I assume your same values have to be copied to my bcd files, right?

These are my bcd files:

\efi\microsoft\boot\bcd

Code: [Select]

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
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

\Boot\bcd

Code: [Select]

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
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.exe
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