multiboot

Hi, has anyone managed to get xpe booting on a multiboot usb drive? i've tried with aio boot and ventoy. Same result, failed to launch. is there some script to change or file i should had to the build?

corrction: aio boot does n't even copy the iso when building. "error"

On Create Iso script, you should check this checkbox as shown in the picture, for aioboot compability.

Thanks for replying, but it does not work for aioboot nor ventoy.

In ventoy there are 3 ways to boot.

1. Add the iso and see if it works.
2. Add the iso and create a folder called ventoy on the root of your USB and create a ventoy. json file there to include -
"
    "auto_memdisk": [
        "/ISO/Win10XPE.iso"
    ]
}
save it and it will boot through memdisk, takes a bit longer though especially for large isos.
3. You can extract the boot.wim from the iso then rename it,  need the ventoy_wimboot.img from the ventoy site for that, just drop it in a folder called ventoy on the root of you USB.

In ventoy there are 3 ways to boot.

1. Add the iso and see if it works.
2. Add the iso and create a folder called ventoy on the root of your USB and create a ventoy. json file there to include -
"
    "auto_memdisk": [
        "/ISO/Win10XPE.iso"
    ]
}
save it and it will boot through memdisk, takes a bit longer though especially for large isos.
3. You can extract the boot.wim from the iso then rename it,  need the ventoy_wimboot.img from the ventoy site for that, just drop it in a folder called ventoy on the root of you USB.

Couldn't edit my post but the first " in the second method shouldn't be there it's just -


    "auto_memdisk": [
        "/ISO/Win10XPE.iso"
    ]
}

thanks for replying,
as for the options:
1 - does not work
2 - after 11 minutes of "loading iso file to memory", i got a blinkin underscore for a long time ( 20 minutes ), so i gave up
3 - i'm not sure how to do that, so i extract the boot.wim, rename it to "what?", download the ventoy_wimboot.img and drop it in a folder called ventoy. the boot.wim that i extract, where do i place it?

for curiosity, what is the difference between normal iso files like windows 10 media ou any other "normal" media from custom pe, that causes this booting issue? i mean there is got to be some sort of file missing or incomplete, or configuration of some kind that does not let it boot.
if i make a bootable usb with rufus it works great, if i had it to a usb virtual drive like a zalman it also works great. so why does it not run in multiboot? 

In my experiments it seems to be certain scripts that cause it, for me it was initially the C++ framework that was causing issues.

Try creating a totally default iso and booting it with method 1.

for method 3 you can place the 'what?.wim' anywhere on the usb, ventoy scans for it automatically.

As for memdisk, it will take quite a while to load for a large iso so its not really an option for anything over around 1gb and even then it will take 5 minutes or more.

so i tried the basic build, dragged and dropped the iso on ventoy and it booted perfectly . so i guess for ventoy it's safe to say it's some app or script that causes the problem. 
i do not have a lot of additions to my project, but it is still a considerable number of modifications. how does one even start to debug without removing all apps? is there some scripts that are know for causing some issus in booting?

with aioboot - it simply won't load the iso on building the drive -  "error please contact the author for support".  is it a aioboot problem, that does not recognize the iso as legit or reliable, or is it a lack of something on the iso?

i know it works fine with rufus, so i thought i could try to cut my losses and thought of making 2 partitions on a usb drive (one for the pe and one for other apps and tools i need - as some of them are too big to get on pe), and that would work fine for me. silly me, rufus wont do just one partition, as to do the whole drive, so.... back to square one

As an update to my last post it seems to that the .net integration is actually the one that breaks it, haven't really experimented with anything else except the C++ framework (which works with Ventoy) but a majority of my apps I run portably from outside the iso (autoload PStart from F:\ on boot) so that I can add/update or remove apps without having to rebuild the ISO and also so that any settings I alter are saved.

I currently have zero experience with AIOBoot but it looks interesting so I'm off to experiment.

i will try removing the .net. for now, i've made things simple by using rufus, then shrinked the partition, and added a new partition for the other apps i need.
that will work for the time being until someone finds the problem.
i really would like to just drag and drop the iso and it's done.
aioboot it's a great tool. i've been using it for multiboot, and it's just very good, and customizable. you should try it