No Auto Installation menu choice, what am I not doing or doing wrong?
Any help would be appreciated 

Volume in drive G is Ventoy
Volume Serial Number is 4E21-0000

Directory of G:\

08/03/2020  06:35 PM    <DIR>          ISO
08/03/2020  06:36 PM    <DIR>          ventoy

Directory of G:\ISO

08/03/2020  06:35 PM    <DIR>          .
08/03/2020  06:35 PM    <DIR>          ..
07/24/2020  09:04 AM    4,197,056,512 Windows_10_64.iso
              1 File(s)  4,197,056,512 bytes

Directory of G:\ventoy

08/03/2020  06:36 PM    <DIR>          .
08/03/2020  06:36 PM    <DIR>          ..
07/26/2020  07:34 PM              188 ventoy.json
08/03/2020  06:36 PM    <DIR>          script
              1 File(s)            188 bytes

Directory of G:\ventoy\script

08/03/2020  06:36 PM    <DIR>          .
08/03/2020  06:36 PM    <DIR>          ..
05/11/2020  06:10 AM            7,618 autounattendmbr.xml
07/26/2020  10:46 AM            7,009 autounattendUEFI.xml
              2 File(s)        14,627 bytes

my ventoy.json file that passed F5-debug and passes Json Parser Online

{ "auto_install" : [
        {
            "image": "/ISO/windows_10_64.iso",
            "template": [
"/ventoy/script/autounattendmbr.xml",
"/ventoy/script/autounattendUEFI.xml"]}]}


Thanks in advance
Robert

老大   DELL C6100  无法从工具盘启动   可以解决下不？

Attached Files

Thumbnail(s)
   

Hello
I just downloaded the latest 64 bit version of windows10 from May from the microsoft download site.

I check the checksum. Its good.

No problem to put in the EXFAT partition.
I boot perfectly with a computer in Legacy mode. The start of the boot is going well. But it is totally impossible to install windows because a driver is missing ...
See this picture https://filestore.community.support.micr...a6cc5dbe75 in an old discussion https://answers.microsoft.com/en-us/wind...90a1604855
I did with the French iso then the international iso in English.

I suspect the missing driver is either the one that accesses the EXFAT partition or the FAT16 partition because when I use another build tool, the installation can be done in a completely normal fashion.

I'm going to give it a try by turning the fat16 partition into fat32.

Do you know this problem?

I tested live ALT Linux Workstation 9.1 x86_64 (2020-08-05) with ventoy-1.0.18.
ISO: alt-workstation-9.1-x86_64.iso (4.7GB)
DistroWatch info: info
Download: download
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
           

I tested live linux BEE free 20.04 2020-08-01 (based on Ubuntu) with ventoy-1.0.18.
ISO: BEE-free-20.04-2020-08-01.iso (3.4 GB)
Download: download
DistroWatch info: info
Site: site
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

Hi,

I love ventoy.
But there's a problem I have.

I made an Multiboot-USB Stick. With ventoy so easy.
But if I edit an ISO the error: "No bootfile found for UEFI! Maybe the image does not support X64 UEFI!" occured.

In this case it's Acronis 2019.
Inside iso is a file for Mac: AcronisTrueImage2019-17000.dmg
I delete this one to safe space. Now I bood end get the error.

Kaspersky rescue disc the same.

But I did the same thing with Acronis 2017 ago... this worked fine.

I use PowerISO or UltraIso to edit the isos.

Can someone help me with this?

Best regards

I've installed Ventoy onto two different USB drives and both fail to boot on an i386.  I get "GR" in the upper left corner, then an error message about an invalid file system, and then it dumps me into a GRUB recovery command prompt.  The USB drives were 16 GB and 2 GB.  Both written successfully with the Windows version of the installer.

I was able to get the drives to boot on a newer x64 system and everything appeared to work properly there.  I was building the USB drive to stick some utilities on, like Clonezilla and DBAN, so it's not super-critical for it to work on "antique" hardware.  It didn't work and I'm trying to understand why.  I read the documentation pretty carefully and didn't see anything that indicated it wouldn't work on x32.

Thanks for any clarification...

I tested live Linux Kodachi 7.2 (2020-08-03) with ventoy-1.0.17/1.0.18.
ISO: kodachi-7.2-64.iso  (2.9GB)
Download: Download
Info site: info
Distrowatch info: info
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
       

I tested live BunsenLabs Linux 6 Lithium amd64 (2020-08-02) with ventoy-1.0.17/1.0.18.
ISO: lithium-1-amd.hybrid.iso  (1.2GB)
Download: 
Distrowatch info: info
Boot:
- Legacy (MBR)
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

I've tested pmagic_2020_05_20.iso and noticed a strange behavior with CloneZilla under a particular condition.  If you use the first option to launch (running from RAM), remove the flash drive after the timezone screen comes up, run Clone Disk (Clonezilla), then just after the "Shutting down the Logical Volume Manager" message, a series of these appear:

/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...
/dev/dm-0: read failed after 0 of 512 at...

This seems to happen only if I remove the flash drive after Parted Magic launches.

This does not happen in Memdisk mode, but of course takes much longer to load.  Tested with both Ventoy 1.0.17 and 1.0.18.

I've tested also with Rufus and YUMI and something similar doesn't happen with either of those.