I am a newcomer to Ventoy and like the idea of being able to select among multiple ISOs to boot. However, after preparing a 32GB USB stick with Ventoy 1.0.90 under Linux and putting multiple ISOs on the stick, Ventoy is not able to see the ISOs on either of the two computers I tried.

Ventoy boots fine but there are no ISOs visible, nor can I find them when I use F2 to move around on the stick. Mounting the stick on another computer I see the ISOs in the Ventoy partition as expected.

What could I be doing wrong? Is there a step I have missed to make them visible in the Ventoy menu?

Is there a way to prevent VTOYEFI from auto-mounting from the MBR formatted Ventoy USB drive on another PC or after using mountvol /r?  When I unplug the USB drive and then run mountvol /r then plug the drive back in it auto-mounts both the Ventoy and the VTOYEFI partitions? MBR uses type EF for the VTOYEFI partition which means EFI System Partition but is not hidden. GPT uses GPT attributes 0xC0000001 for the VTOYEFI partition which is both hidden and no auto-mount.

Hi all,
for practical and performance reasons I am trying to copy from my USB driver .ISO and casper-rw files on the target (temporary) computer first partition (ext3)
I manage to boot successfully by F2 browsing the disk, but not giving persistency.
I tried to manually add "persistence" to the boot command line, but it does not work (it is not a FAT partition)
then I tried to configure ventoy.conf file adding (hd1,1) to the path, but as you see it is parsed as 'invalid'
Any further ideas ?
cheers
"persistence":[
        {
            "image": "/YUMI/Linux-ISOs/linuxmint-21.1-mate-64bit.iso",
            "backend":[
                "/YUMI/Linux-ISOs/persistence.dat"
            ]
        },
{
            "image": "(hd1,1)/boot/boot-isos/linuxmint-21.1-mate-64bitHDD.iso",
            "backend":[
                "(hd1,1)/casper-rw"
            ]
        },
        {
            "image": "/YUMI/Linux-ISOs/linuxmint-21.1-xfce-64bit.iso",
            "backend":[
                "/YUMI/Linux-ISOs/casper-rw"
            ]
        }
    ]

以前i没注意过这个问题今天用此软件写U盘直接启动PE的ISO文件发现C盘被U盘占用。例原C在PE中显示为E，有没有什么解决 方案。

• 2023/03/26 --- 1.0.90 release
  

1. Fix the issue that VTOY_LINUX_REMOUNT option can not work for (Kernel 5.18+) + (Intel Gen11+ CPU).
   
   
2. Support LibreELEC 11.0+. (#2281)
   
3. Fix the issue that Fedora Rawhide install media not detected. (#2283)
   
4. Add support for chimera linux. (#2309)
   
5. Optimization for Fedora boot process.
   
6. languages.json update.
   
7. New iso support. (Total 1100+)
   

Hi,

Maybe a bit of a niche question, but I've started using Ventoy at work to easily switch between diagnostic and various OS ISOs for client hardware, and one thing that's been floating in the back of my mind is,

"If a Windows ISO can boot fine, and an Ubuntu ISO can boot fine, how come I need to register Ventoy's certificate?"

I really don't know too much when it comes to exactly how secure boot works. I figured maybe it's a Microsoft thing where OEMs ship with private keys that only handshake with Windows, but my Ubuntu USBs will boot on these systems with no Mokmanager prompt as well.

In that case, is it possible to take the certificate from Ubuntu or Windows and "transplant" it onto my VTOYEFI partition? Or perhaps there's a tool I can use to enroll my Ventoy .cer with the private keys the UEFIs expect, or something?

Like I said, I'm not too sure how secure boot works on anything beyond a basic conceptual level, but if anyone could help me make it so I can boot my Ventoy USBs on new machines without enrolling the key or disabling secure boot every time, I'd be very appreciative

I have Ventoy Installed on a USB3 Portable SSD 500gb.
There is Plenty of Space left , only 50% occupied.
This drive has Ventoy installed as GPT and Formatted to NTFS with a \Ventoy Partition.
I have all my ISO's in \Ventoy.
Everything Works just Fine from here.
I have Created a Linux Persistence File here ( WindowsFx ) and it Works, and Saves between Restart.
However shortly after a restart of WindowsFx a message Popped Up Saying I have Run out of Space on The Drive.
At that point I have Hardly Installed much at all.
Any help would be appreciated.

1. 设备：

• 佳翼I9GTR硬盘盒+梵想固态硬盘
  

• ventoy：安装到移动硬盘，并放入VHD的img插件，支持VHD启动
  
• wtg：win创建VHD，WTGA安装，ventoy进wtg成功
  
• ltg：VirtualBox创建虚拟机(固定+efi)，加载Ubuntu-22.04.2-full.iso安装完成，安装vtoyboot插件，改名为vdi.vtoy
  

• ThinkPad T480: 启动进ubuntu系统, ok
  
• 拯救者R9000x: 启动失败，错误提示后黑屏, fail
  
• 后来测了CentOS7和8，问题一样，报错都差不多 
  

• T480s：独立NVIDIA MX150，内存40G，硬盘m.2 pcie3 三星固态 500G
  
• R9000x：集显+独立NVIDIA gtx1650ti(混合模式)，内存40G，硬盘梵想S500pro 2TB+三星980 1TB
  

Attached Files

Thumbnail(s)
       

这个工具很好，经常推荐给完全小白的人使用，但是也很频繁会碰到他们用的U盘是虚标容量的情况，启动后只能进入grub命令行界面，然后就要手把手教他们怎么在 U盘手动建目录然后复制压缩包内的 ventoy.disk.img.xz，非常麻烦，个别人甚至直接就放弃了。所以，能否在 UI 上加个单选框之类的，在制作启动盘时候直接就采用将压缩包放在可见区方案？

I created a Ventoy USB stick, worked great, I needed more room on the VENTOY 1st partition for more ISO files, so I used MiniTool Partition Wizard to shrink a 3rd partition I had after the EFI partition, move the VTOYEFI and increase the size of the VENTOY partition.

Attempting to boot to it threw an error that is was not a standard Ventoy installation and it failed. It was a simple enough fix, I simply deleted the VTOYEFI partition (I used MiniTool again) and then did a Non Destructive Install using the Ventoy2Disk.exe. After this it worked again. 

Why is Ventoy so picky about moving the EFI partition? I've moved around an EFI partition for other boot tools, like AGFM / Easy3Boot without issue.  I also notice that you can't increase the size of the EFI partition either.

Curious as to why this is like this.