Universal Dual Boot BIOS/UEFI for Windows 7 / 8.1 / 10 AIOs

ChrisR, I decided to open a new thread since you allow me to do it and not to spoil the other thread. So quoting your last message in the other thread, I want to ask if this is good for my needs:

Mr.X,

In addition...
For your AIO Windows 8.1 or 10 
I guess that the simplest way is to use the Media Creation Tool by choosing both architectures.
Thus you have the base for starting windows in 32-bit or 64-bit, in Bios or UEFI.
then replace:
x86\sources\install.esd by your AIO install.wim with 32-bit home, Pro, enterprise,... images
x64\sources\install.esd by your AIO install.wim with 64-bit home, Pro, enterprise,... images
Not tested but it should be enough 

Oherwise, here is an example to change both bcd:

Code: [Select]

:: Change PATH
:: MBR bcd
Bcdedit.exe /store PATH\boot\bcd /create {3de3efd5-a380-11e5-9c17-000000005aad} /d "Windows 10 Setup (32-bit)" /application osloader
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} osdevice ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} device ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} path \windows\system32\boot\winload.exe
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} systemroot \Windows
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} locale en-US
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} inherit {bootloadersettings}
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} bootmenupolicy legacy
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} detecthal Yes
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} winpe Yes
Bcdedit.exe /store PATH\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} EMS No
:: displayorder
Bcdedit.exe /store PATH\boot\bcd /displayorder {default} {3de3efd5-a380-11e5-9c17-000000005aad}
::
:: EFI bcd
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /create {3de3efd5-a380-11e5-9c17-000000005aad} /d "Windows 10 Setup (32-bit)" /application osloader
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} osdevice ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} device ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} path \windows\system32\boot\winload.efi
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} systemroot \Windows
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} locale en-US
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} inherit {bootloadersettings}
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} isolatedcontext Yes
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} bootmenupolicy legacy
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} detecthal Yes
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} winpe Yes
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /set {3de3efd5-a380-11e5-9c17-000000005aad} EMS No
:: displayorder
Bcdedit.exe /store PATH\efi\microsoft\boot\bcd /displayorder {default} {3de3efd5-a380-11e5-9c17-000000005aad}

Just an example 
You can also use Visual BCD Editor or EasyBCD

I actually know how to make AIOs. Whether they are single architecture or double architecture (using x86 iso files), Windows 7/8/8.1/10.
For MBR disks there's no problem with any combination whatsoever. To overcome the UEFI - GPT boot I've always made x64 AIOs though. When I saw the other topic I thought I found an opportunity to learn or resolve the problem about Universal Dual Boot on a single install.esd x86/x64 Windows 8.1 multi-index iso file.

That said, I need to have my AIO as an iso file and capable of being deployed on a USB stick to boot as well. I use to run Rufus program to make USB sticks for UEFI/GPT boot and for legacy BIOS/UEFI-MBR boot, so I don't really know if Rufus could handle this non-standard boot files then if not, what other program can I use for USB sticks. Moreover, is this even possible?

So the above bcd edit is enough for my needs?

Thanks in advance.

Here is a Legacy Boot BCD Store..
It displays the boot options for WinPE x86, WinPE x64, Windows 8.1 Setup x86, Windows 8.1 Setup x64, Windows 10 Setup x86 and Windows 10 Setup x64

They all use the same boot file - they all just point to a different RAMDISK "Sources" folder

BOOTICE is your friend..  select the entry for say WinPE x86 > right-click select Duplicate
Edit the Ramdisk locations and description

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}
                        {abb7e776-8af0-11e5-83a1-0c8bfd4c841a}
                        {b549f9c0-2d28-4f35-b5b2-cc130fb6923c}
                        {934f4b5b-405f-4077-9478-00eab73caeef}
                        {c070b244-810c-408f-bf01-44a0bbb4ff32}
                        {092484ef-9a69-4ad1-a9e7-c5222348fd31}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30
displaybootmenu         Yes

Windows Boot Loader
-------------------
identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
device                  ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             WinPE (64-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice               ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Windows Boot Loader
-------------------
identifier              {abb7e776-8af0-11e5-83a1-0c8bfd4c841a}
device                 ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             WinPE (32-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice               ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Windows Boot Loader
-------------------
identifier              {b549f9c0-2d28-4f35-b5b2-cc130fb6923c}
device                  ramdisk=[boot]\Win10\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows 10 Setup (64-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice               ramdisk=[boot]\Win10\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Windows Boot Loader
-------------------
identifier              {934f4b5b-405f-4077-9478-00eab73caeef}
device                ramdisk=[boot]\Win10\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows 10 Setup (32-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice              ramdisk=[boot]\Win10\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Windows Boot Loader
-------------------
identifier              {c070b244-810c-408f-bf01-44a0bbb4ff32}
device                 ramdisk=[boot]\Win81\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows 8.1 Setup (64-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice               ramdisk=[boot]\Win81\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Windows Boot Loader
-------------------
identifier              {092484ef-9a69-4ad1-a9e7-c5222348fd31}
device                  ramdisk=[boot]\Win81\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows 8.1 Setup (32-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice               ramdisk=[boot]\Win81\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

I think it should be OK to prepare your USB sticks with Rufus, it must be FAT32 for UEFI.
You can also use Bootice -> Part Manage -> Format This Part -> FAT32
and check with "process MBR" button that windows NT 6.x MBR is installed.
Then, copy all the files and folders

Code: [Select]

There are a total of 18 entries listed in the bootloader.
Path: C:\Users\Dell\Desktop\DualBootBCD\boot\bcd

Default: Windows 10 PESE (64-bit)
Timeout: 30 seconds
EasyBCD Boot Device: C:\

Entry #1
Name: Windows 10 Multi Setup (32-bit)
BCD ID: {abb7e776-8af0-11e5-83a1-0c8bfd4c841a}
Device: [boot]\x86\Win10Multi\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #2
Name: Windows 10 Enterprise Setup (32-bit)
BCD ID: {a533d773-396e-440a-a617-faa6a9b2a280}
Device: [boot]\x86\Win10Enterprise\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #3
Name: Windows 10 Pro Setup (32-bit)
BCD ID: {cf9dc980-d29c-4b4d-87d3-370c5292a65b}
Device: [boot]\x86\Win10Pro\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #4
Name: Windows 10 Home Setup (32-bit)
BCD ID: {f2289bab-5e83-4461-a1a4-a1952594588f}
Device: [boot]\x86\Win10Home\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #5
Name: Windows 10 PESE (32-bit)
BCD ID: {32dfc0c7-0b5f-4929-bf6f-25245e65a473}
Device: [boot]\x86\Win10PESE\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #6
Name: Windows 10 Multi Setup (64-bit)
BCD ID: {7619dcc9-fafe-11d9-b411-000476eba25f}
Device: [boot]\x64\Win10Multi\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #7
Name: Windows 10 Enterprise Setup (64-bit)
BCD ID: {80533800-2fcb-4b87-840e-6ce0091e919d}
Device: [boot]\x64\Win10Enterprise\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #8
Name: Windows 10 Pro Setup (64-bit)
BCD ID: {1e6b01ad-e477-4524-83a4-d0c544f2bb18}
Device: [boot]\x64\Win10Pro\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #9
Name: Windows 10 Home Setup (64-bit)
BCD ID: {9550ab7f-14a8-40ed-82c8-b9d09b06f6ba}
Device: [boot]\x64\Win10Home\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #10
Name: Windows 10 PESE (64-bit)
BCD ID: {default}
Device: [boot]\x64\Win10PESE\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #11
Name: Windows 8.1 Enterprise Setup (32-bit)
BCD ID: {8f0c7bf6-c350-4ecb-857a-24fb722d2d29}
Device: [boot]\x86\Win8.1Enterprise\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #12
Name: Windows 8.1 Pro Setup (32-bit)
BCD ID: {ad4fc20b-1428-4023-9353-a7f22ee12985}
Device: [boot]\x86\Win8.1Pro\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #13
Name: Windows 8.1 Home Setup (32-bit)
BCD ID: {420992e4-3b84-4dac-9a68-72ff63331e49}
Device: [boot]\x86\Win8.1Home\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #14
Name: Windows 8.1 PESE (32-bit)
BCD ID: {a0a84c41-2320-4f32-a57d-d339630d9c75}
Device: [boot]\x86\Win8.1PESE\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #15
Name: Windows 8.1 Enterprise Setup (64-bit)
BCD ID: {37711056-b643-40cb-a4fc-881dca2114f2}
Device: [boot]\x64\Win8.1Enterprise\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #16
Name: Windows 8.1 Pro Setup (64-bit)
BCD ID: {b50ce744-e583-4664-a276-889e259b88b1}
Device: [boot]\x64\Win8.1Pro\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #17
Name: Windows 8.1 Home Setup (64-bit)
BCD ID: {999889e3-c7c9-47a8-97c6-b653f81860d2}
Device: [boot]\x64\Win8.1Home\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

Entry #18
Name: Windows 8.1 PESE (64-bit)
BCD ID: {7968af58-32b0-4878-8ff4-86fdc466afeb}
Device: [boot]\x64\Win8.1PESE\sources\boot.wim
Bootloader Path: \windows\system32\boot\winload.exe

I think it should be OK to prepare your USB sticks with Rufus, it must be FAT32 for UEFI.

Not just FAT32 anymore. After nagging to Akeo he finally implemented proper drivers for Rufus to format as NTFS for UEFI. Some people including me requested to Akeo that feature due some Windows AIOs have install.wim or install.esd files larger than 4GB. 

I didn't know, what is the config to do for partition scheme and File System ?
I just updated Rufus to version 2.5.799.0

I didn't know, what is the config to do for partition scheme and File System ?
I just updated Rufus to version 2.5.799.0

Just select GPT partition scheme for UEFI and NTFS 

Thanks 
I just look at the Faq, it seems that Rufus does not provide any option for dual UEFI+BIOS boot.
https://github.com/pbatard/rufus/wiki/FAQ#Why_doesnt_Rufus_create_a_Windows_installation_USB_that_can_be_booted_in_both_BIOS_and_UEFI_mode

So, I do not know how it must be done, for the dual UEFI+BIOS option (Fat32) with install.wim larger than 4GB (Windows AIOs).
Probably with a second partition NTFS and with an USB disk, not to switch between Hide/Unhide partition. 

Thanks 
I just look at the Faq, it seems that Rufus does not provide any option for dual UEFI+BIOS boot.
https://github.com/pbatard/rufus/wiki/FAQ#Why_doesnt_Rufus_create_a_Windows_installation_USB_that_can_be_booted_in_both_BIOS_and_UEFI_mode

Yes, it's a shame.

So, I do not know how it must be done, for the dual UEFI+BIOS option (Fat32) with install.wim larger than 4GB (Windows AIOs).
Probably with a second partition NTFS and with an USB disk, not to switch between Hide/Unhide partition.

But you are talking about Rufus only right? Perhaps you already have another program or solution other than Rufus.

I do not have solution, others probably 
I am not a PC Tech and I have not played with Windows AIO even is I know how. Home and Pro is enough for my needs with both install.wim x86/x64.
I use BootIce here to format in Fat32 and all my msdn ISO and install.wim (for WinNTSetup) are on a second NTFS partition on my USB hdd.

It all can be easily done - by NOT creating an AIO Install.wim over 4 GB
To create an AIO USB - use separate Folders..
You can then capture the setup as an ISO file..
As stated many times... Follow MS's Lead - it works..

It all can be easily done - by NOT creating an AIO Install.wim over 4 GB
To create an AIO USB - use separate Folders..
You can then capture the setup as an ISO file..
As stated many times... Follow MS's Lead - it works..

Thanks. But I am lost now lol sorry don't know what you mean by MS's Lead...
You know, I consider myself an amateur for Windows AIOs not an expert. 

Hey man. Maybe I can help you. I did some AIOs in the past

But I didn't undertand very well what you're trying to do.

If you have problems with the size of install.wim (over 4GB) you must split it.
https://technet.microsoft.com/en-us/library/hh825096.aspx

You can not Install a split wim (.swm)
You have to Apply the .swm files

Lets see if I can explain this all real easy... When you boot Windows Setup Media - you are actually booting into the boot.wim inside the sources folder..
That boot.wim is WinPE that launches the Windows Setup...  We already have a much more user friendly WinPE boot.wim (WinPESE)

We build WinPESE to a USB Stick and it is able to boot Legacy or UEFI - via the F12 boot menu option - on supported PC hardware..

So that part is already taken care of = We already have a bootable WinPESE..

Now to create Windows Setup...
After creating your WinPESE USB - create a few other Folders on the USB drive...
Create "Edition" Folders (Enterprise, Professional, Home) on the USB
Inside each of the "Edition" folders create "x86" and "x64" sub-folders
Copy the contents of the Setup Media ISO into the correct corresponding folders...

You do not need to copy from the Setup Media, Because they are not needed and will save you drive space
AUTORUN.INF
BOOTMGR
BOOTMGR.EFI
BOOT - FOLDER
EFI - FOLDER

Boot the WinPESE USB drive - and from File Manager - browse to the USB Drive - select the Windows Version you want to install - run Setup.exe
That's it.. You have now started windows setup from within WinPE (but instead of using MS WinPE - we used WinPESE)

@all
Thank you guys, all of you. I want to gather all info provided in your previous posts then get my hands dirty for a while on the next few days to test. Just saying because you won't hear of me (my feedback) soon 

Xmas holidays are around the corner. So if I don't see/you don't see me around here I wish you happy holidays. Thanks a lot. 

So that part is already taken care of = We already have a bootable WinPESE..

First off I want to thank you, a lot for this detailed tutorial. Amazing.

Now perhaps I didn't explained myself since the beginning and actually I changed topic's title so I apologize for that. I want to make Universal Dual Boot BIOS/UEFI for Windows 7 / 8.1 / 10 AIOs installation media (DVD and USB) but with original untouched M$ isos, not WinPESE's. Is this possible? I learned so far how to edit bcd files, yet I still need more to make them to work.

yes it is possible.......

with the dual boot setup (x64) (x86)

right now the BCD points to the version in the respective folders

you would have to edit the BCD to point to every version folder within the x64 x86 sub-folders

(x64) windows 10, windows 8.1, windows 8.1 pro, windows 7
(x86) windows 10, windows 8.1, windows 8.1 pro, windows 7

if you notice the RAMDISK= options in the codeboxes I posted above - you will see that they all point to a different sub-folder

yes it is possible.......

with the dual boot setup (x64) (x86)

right now the BCD points to the version in the respective folders

you would have to edit the BCD to point to every version folder within the x64 x86 sub-folders

(x64) windows 10, windows 8.1, windows 8.1 pro, windows 7
(x86) windows 10, windows 8.1, windows 8.1 pro, windows 7

if you notice the RAMDISK= options in the codeboxes I posted above - you will see that they all point to a different sub-folder

Good to know it's possible. Thank you.
However I forgot to mention I want the AIOs separated by version, not all versions in one.

Now I've started off with Windows 7. These are my bcd files:

\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}
                        {dbfc69fe-d277-4e4e-ab92-e85ecdde0ede}
timeout                 30

Windows Boot Loader
-------------------
identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
device                  ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows 7 BIOS/UEFI-CSM & DISCO MBR (64-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Windows Boot Loader
-------------------
identifier              {dbfc69fe-d277-4e4e-ab92-e85ecdde0ede}
device                  ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows 7 BIOS/UEFI-CSM & DISCO MBR (32-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                ramdisk=[boot]\x86\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

\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}
                        {43e1117b-4777-4c41-89cf-1122b86a75ba}
timeout                 30

Windows Boot Loader
-------------------
identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
device                  ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.efi
description             Windows 7 UEFI & DISCO GPT (64-bit)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
isolatedcontext         Yes
osdevice                ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Windows Boot Loader
-------------------
identifier              {43e1117b-4777-4c41-89cf-1122b86a75ba}
device                  ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.efi
description             Windows 7 UEFI para 32-bit no existe selecciona 64-bit
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
isolatedcontext         Yes
osdevice                ramdisk=[boot]\x64\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Legacy
detecthal               Yes
winpe                   Yes
ems                     No

Folder/file structure

However I forgot to mention I want the AIOs separated by version, not all versions in one.

All In One what ??

USB or WIM ??

I am talking USB - formatted FAT32 to support UEFI Booting