Hi guys.
My USB pen drive where is Ventoy with .iso images of operating system is lot listed in USB boot devices, at all.
So when I go to laptop boot options/menu, USB device should be there but it is not.
I tried on multiple laptops, nope, laptop does not see USB pen drive and Ventoy.
I googled this issue, advice was to disable secure boot, but this moring I pluged the USB pendrive on my HP ZBook 17 old laptop, and again same issue, USB pendrive is not seen in boot options.
I think even this laptop does not have secure boot option, have not seen it in BIOS.
I don't have issue with normal USB pendrive devices.
What have I done wrong during procedure of making Ventoy USB pen drive?

So, you’ve got your Ventoy setup all neat and tidy, but what if the real partition you’re missing is your free time for something a little less digital and a little more… human? Ever thought about resizing your priorities to make space for unexpected connections?




MeetAgree.com
She's ready to make your night better

My Ventoy-stick (1.1.17) boots on all my PCs, and starts any numer of ISOs correctly.
So I thought I had all the settings with stick formats, UEFI and Secure Boot settings right.

Now I am testing the new desinfect2026.img (virus scanner from German computer magazine c't).

It boots and runs from Ventoy as expected on all my wide variety of PCs, except for these two:
a Lenovo T420 Laptop, i7-2620M-CPU , 8GB RAM,  latest UEFI-BIOS 1.53 from 2018 (Linux Mint 22.3 installed)
a Lenovo T420 Laptop, i5-2540M-CPU , 6GB RAM,  latest UEFI-BIOS 1.52 from 2018 (Windows 11 25h2 pro installed)

where, right after selecting the image in Ventoy, I see a white-on-black-screen error message for a moment:
"unknown filesystem", then the screen erases and a blinking, unresponsive cursor remains.

It should be re-iterated that all the other images on the same stick boot flawlessly on these T420s, and the same stick (not a copy) has no issues booting desinfect on other machines.

When I create a "solo-stick", just the desinfect2026.img written to a USB stick without the involvement of Ventoy, it does in fact boot and run on these two old laptops.

Any idea what might be going wrong under Ventoy, or what I could do to help troubleshooting?

Boa noite. Alguem poderia me ajudar? Estou tendo dificuldade em executar o iventoy na versão 1.0.38. O novo pxe 2.0 não carrega em minhas maquinas, ficando congelado na tela de boot conforme anexo.
Se alguem tiver uma solução ficaria grato

Attached Files

Thumbnail(s)
   

Greetings,
 
To make a long story short.  I am attempting to reinstall proxmox ve 8.4 using 4 disk in a zfs-raid10 configuration.  Installation succeds.  Reboot fails. right after loading array modules it hangs.  From the Proxmox support forums: fix for version 9.2.1 I know that this is not the same version I am installing but the fix apparently to some extent applies.

Upon restarting my t7910  I get the grub menu and edit the kernel boot parameters and remove rdinit=/vtoy/voty which is at the end of the line.  press f10 and proxmox boot normally.  I am using ventoy version 1.1.16 boot mode is grub2.  Is there a straight forward solution?  I am tired of reinstalling.  Why causes ventoy do this? 

Tia,

A Potato that is a Couch

I found a link that explained how to 'fix' this: Edit file cmdline.  Still kindo curious why would this parameter be added to the kernel command line.

Please i need some help i was traying resize the partition of VTOYEFI since once you created a ventoy usb bootable device it makes 2 partition which one is i already mentioned VTOYEFI. what i really want is just want to resize it since it has only a 32MB size i wanna make it atleast 100MB. i tried some of the partition software but i cannot change it.

is there any way or simple solution for my question?
please i really need your input and thank you

Greetings friends;

I am trying to run Plugson so that I can change the theme within my Ventoy USB - by using this information straight from the VentoyPlugson webpage:
   
In my case using - sudo bash VentoyPlugson.sh /dev/sdc - as the path to the USB drive.

The result from the terminal is as follows:
   
The above shows "No such file or directory" which means that I cannot progress any further than 2.2.1. Just how is this supposed to work - directly using the webpage instructions above??  

I've looked through many YouTube videos refering to Plugson use, but they are all for the Windows OS and of no relevance for Linux.

Is there is anyone out there who has actually managed to get plugson to work on Linux using 2.2.1 above the and (if yes), exactly how - please?

In the meantime, I look forward to any/all constructive replies.

Cheers

Chris - themotte.

Hello,
I have an issue with iVentoy since version 1.0.35 (which updated iPXE to 2.0.0).
Problem:

• PXE boot gets stuck during iPXE loading on several laptops.
  
• Works perfectly on version 1.0.34.
  
• Same issue on 1.0.35, 1.0.36 and 1.0.37.
  

• Lenovo ThinkPad T480 (and several other laptop models)
  
• UEFI mode (Secure Boot disabled)
  

• Different EFI boot files (snponly.efi, snp.efi, ipxe.efi)
  
• ProxyMode DHCP mode
  
• Secure Boot disabled
  

Feature Request: Optional prompt for Auto Memdisk before booting an ISO

Hello,

First of all, thank you for the excellent work on Ventoy.

I would like to suggest a small improvement to the Auto Memdisk Plugin.

Currently, when an ISO is configured for Auto Memdisk, pressing Enter immediately starts copying the ISO to RAM. While this is very useful in many situations, there are also cases where booting directly from the USB drive is the better choice.

For example:

The computer may not have enough RAM available.
The user may not want to wait for the ISO to be copied to memory.
The ISO may work perfectly well when booted directly from the USB drive.
The user may simply want to choose the most appropriate option for that specific boot.

My suggestion would be to display a small prompt before starting the ISO, similar to how the Auto Install (Autounattend) plugin works.

Example:

How do you want to boot this ISO?

1. Boot from RAM (Memdisk)
2. Boot from USB (Normal)

Automatically continue with the default option in 5 seconds...

The timeout could be configurable (for example, 3–10 seconds), with a default boot option defined in ventoy.json.

This would keep the current automatic behavior for users who want it, while giving others the flexibility to choose when needed, without having to maintain duplicate ISO files or edit the configuration.

I believe this would make the Auto Memdisk Plugin even more flexible without affecting existing users.

Thank you for considering this suggestion.

Hello,
After updating to iVentoy 1.0.36, the Auto Install Script feature no longer works.
What worked before:

• iVentoy 1.0.35 → everything works perfectly
  
• Same Windows 11 25H2 ISO
  
• Same autounattend.xml file
  

• The script is correctly added to the ISO in the web GUI
  
• It is set as Default Auto Script
  
• I tested with multiple different XML files (including minimal ones)
  
• Tried with and without Auto Script Select Timeout
  
• File is named autounattend.xml (UTF-8)
  

• Windows 11 25H2 ISO
  
• iVentoy 1.0.36 (latest version)
  
• Server running on Linux Debian 13
  

• Downgrading to 1.0.35 immediately fixes the issue
  
• Removed and re-added the script multiple times
  
• Tried renaming to unattend.xml
  
• Restarted the iVentoy service after every change