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
  

When I used the automated deployment script from iventoy for installation, I encountered two issues. One was that several versions of CentOS 7 could not detect /dev/sr0, preventing me from proceeding with the installation process, as shown in Figures 1 and 2. The other issue was that several versions of CentOS 8 prompted me with a network unreachable error, preventing me from proceeding with the installation process. However, after entering emergency mode, I was able to ping normally, as shown in Figure 3;

By the way, I tried to use the kickstart7.cfg file in the example/ directory for CentOS 7.0 installation, but it also failed to install properly.

When I don't use the ks script for installation, it loads normally. Could it be that there's a problem with the ks script I wrote? Or is there some other reason? Could you please help me out.

   
   
   

Attached Files

  T4-C70-BIOS-82.33.cfg.txt (Size: 2.24 KB / Downloads: 0)

When I try to change Secure Boot string to Bypass Secure Boot (means 0) Plugson just removes whole string and if you select follow UEFI Secure boot check then it will return but with option 1 and also with Secure boot disabled I cannot boot entirely. Also VTOY_WIN_UEFI_RES_LOCK resets when entering Plugson. Why developer not testing it before release??

Attached Files

Thumbnail(s)
       

• 2026/06/25 --- 1.1.15 release
  

1. Fix the boot issue when Secure Boot is disabled in the UEFI firmware. (#3650)
   Attention: Ventoy use a new UEFI secure boot CA since v1.1.14, so you need to enroll the new key for the first boot time. Please refer Notes
   

• 2026/06/24 --- 1.1.14  release
  

1. Update secure boot shim file to solve the UEFI CA 2023 issue.
   
   
2. VentoyPlugson update synchronously.
   
   
3. Global control plugin add a  VTOY_SECURE_BOOT_POLICY option. Notes
   

Will Ventoy need to be updated to rely ONLY on 2023 Secure Boot certificates when MS revokes the 2011 certificates?

I have now inventoy 1.0.34 running only it does not work anymore (also the 1.0.26 does not work).

I think this is because the IP address given by the third party (the router) is a.b.c.20 for example while iVentoy only respond to ip address a.b.c.201 till a.b.c.221.
(I saw in WireShark the IP address given to the PXE Interface).

The DHCP server is in the same subnet (a.b.c.1/24) , On this DHCP server I configured option 66 and 67 (bootfile and next server).
I see that the PXE interface gets it's IP address but not within the configured range, even if I bind the PXE mac address to an IP address within the range it still doesn't work.

Looks like the iVentoy server does not respond at all? In the firewall I permit all traffic to and from the program 'iVentoy_64.exe'
The iVentoy is running on a Windows Server 2016.


Waiting at your input.

Kind regards,
 Johan