<![CDATA[Ventoy Forums - All Forums]]> https://forums.ventoy.net/ Sat, 26 Sep 2026 00:47:15 +0000 MyBB <![CDATA[Ventoy USB pendrive is not listed in boot devices]]> https://forums.ventoy.net/showthread.php?tid=3280 Sat, 05 Sep 2026 07:44:13 +0000 pcpartpicker]]> https://forums.ventoy.net/showthread.php?tid=3280 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?]]> 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?]]> <![CDATA[Can a perfectly partitioned drive still leave room for spontaneity?".]]> https://forums.ventoy.net/showthread.php?tid=3254 Thu, 27 Aug 2026 02:28:13 +0000 FireswordDEA08]]> https://forums.ventoy.net/showthread.php?tid=3254



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



MeetAgree.com
She's ready to make your night better ]]> <![CDATA[error "unknown filesystem" on two old Laptops , desinfect2026.img]]> https://forums.ventoy.net/showthread.php?tid=3250 Mon, 24 Aug 2026 08:05:00 +0000 kreuter]]> https://forums.ventoy.net/showthread.php?tid=3250 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?]]> 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?]]> <![CDATA[Erro iPXE 2.0.0 na versão 1.0.38 do Iventoy]]> https://forums.ventoy.net/showthread.php?tid=3242 Thu, 30 Jul 2026 00:04:31 +0000 jackson]]> https://forums.ventoy.net/showthread.php?tid=3242 Se alguem tiver uma solução ficaria grato

.jpeg   WhatsApp Image 2026-07-29 at 20.55.15.jpeg (Size: 142.03 KB / Downloads: 11) ]]> Se alguem tiver uma solução ficaria grato

.jpeg   WhatsApp Image 2026-07-29 at 20.55.15.jpeg (Size: 142.03 KB / Downloads: 11) ]]> <![CDATA[Proxmox 8.4.x rdinit=vtoy/vtoy SOLVED]]> https://forums.ventoy.net/showthread.php?tid=3231 Wed, 22 Jul 2026 23:15:47 +0000 Couch_Potato]]> https://forums.ventoy.net/showthread.php?tid=3231  
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 Smile

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.]]>  
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 Smile

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.]]> <![CDATA[VENTOY Resize Partition]]> https://forums.ventoy.net/showthread.php?tid=3230 Wed, 22 Jul 2026 04:33:48 +0000 zaldhie]]> https://forums.ventoy.net/showthread.php?tid=3230
is there any way or simple solution for my question?
please i really need your input and thank you Smile]]>
is there any way or simple solution for my question?
please i really need your input and thank you Smile]]> <![CDATA[Plugson installation - not working.]]> https://forums.ventoy.net/showthread.php?tid=3225 Sun, 05 Jul 2026 16:58:55 +0000 Themotte]]> https://forums.ventoy.net/showthread.php?tid=3225
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:

.png   How to start..png (Size: 26.55 KB / Downloads: 9)
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:

.png   Plugson terminal.png (Size: 14.4 KB / Downloads: 11)
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?? Confused  Huh

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.]]>
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:

.png   How to start..png (Size: 26.55 KB / Downloads: 9)
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:

.png   Plugson terminal.png (Size: 14.4 KB / Downloads: 11)
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?? Confused  Huh

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.]]> <![CDATA[[iPXE 2.0.0 regression] PXE boot fails on Lenovo T480 and other laptops since 1.0.35]]> https://forums.ventoy.net/showthread.php?tid=3222 Fri, 03 Jul 2026 09:49:03 +0000 matmus06]]> https://forums.ventoy.net/showthread.php?tid=3222 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.
Affected hardware:
  • Lenovo ThinkPad T480 (and several other laptop models)
  • UEFI mode (Secure Boot disabled)
What I already tried:
  • Different EFI boot files (snponly.efi, snp.efi, ipxe.efi)
  • ProxyMode DHCP mode
  • Secure Boot disabled
Result:
Only version 1.0.34 works reliably. Versions 1.0.35+ fail at the iPXE initialization stage.
Note: On 1.0.36 the .XML auto-install scripts also stopped working.
Could you please check the iPXE 2.0.0 integration for compatibility with Intel NICs on ThinkPad laptops?
Thank you!]]> 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.
Affected hardware:
  • Lenovo ThinkPad T480 (and several other laptop models)
  • UEFI mode (Secure Boot disabled)
What I already tried:
  • Different EFI boot files (snponly.efi, snp.efi, ipxe.efi)
  • ProxyMode DHCP mode
  • Secure Boot disabled
Result:
Only version 1.0.34 works reliably. Versions 1.0.35+ fail at the iPXE initialization stage.
Note: On 1.0.36 the .XML auto-install scripts also stopped working.
Could you please check the iPXE 2.0.0 integration for compatibility with Intel NICs on ThinkPad laptops?
Thank you!]]> <![CDATA[Auto Memdisk Plugin]]> https://forums.ventoy.net/showthread.php?tid=3221 Wed, 01 Jul 2026 11:01:27 +0000 jlsupremo]]> https://forums.ventoy.net/showthread.php?tid=3221
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,

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.]]> <![CDATA[[SOLVED] iVentoy 1.0.36 - Auto Install Script (autounattend.xml) stopped working]]> https://forums.ventoy.net/showthread.php?tid=3216 Mon, 29 Jun 2026 07:38:09 +0000 matmus06]]> https://forums.ventoy.net/showthread.php?tid=3216 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
Problem with 1.0.36:
  • 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)
Despite all that, Windows Setup ignores the unattended file and runs in normal (manual) mode.
Environment:
  • Windows 11 25H2 ISO
  • iVentoy 1.0.36 (latest version)
  • Server running on Linux Debian 13
Tests done:
  • 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
Is anyone else experiencing this issue with version 1.0.36?
Is this a known regression or an intended change?
Thank you in advance!]]> 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
Problem with 1.0.36:
  • 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)
Despite all that, Windows Setup ignores the unattended file and runs in normal (manual) mode.
Environment:
  • Windows 11 25H2 ISO
  • iVentoy 1.0.36 (latest version)
  • Server running on Linux Debian 13
Tests done:
  • 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
Is anyone else experiencing this issue with version 1.0.36?
Is this a known regression or an intended change?
Thank you in advance!]]> <![CDATA[Using ks script issues]]> https://forums.ventoy.net/showthread.php?tid=3215 Mon, 29 Jun 2026 07:08:31 +0000 Niesitelin]]> https://forums.ventoy.net/showthread.php?tid=3215
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.


.png   i1.png (Size: 191.18 KB / Downloads: 7)

.png   i2.png (Size: 393.68 KB / Downloads: 3)

.png   i3.png (Size: 379.71 KB / Downloads: 2)

.txt   T4-C70-BIOS-82.33.cfg.txt (Size: 2.24 KB / Downloads: 0) ]]>
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.


.png   i1.png (Size: 191.18 KB / Downloads: 7)

.png   i2.png (Size: 393.68 KB / Downloads: 3)

.png   i3.png (Size: 379.71 KB / Downloads: 2)

.txt   T4-C70-BIOS-82.33.cfg.txt (Size: 2.24 KB / Downloads: 0) ]]> <![CDATA[Ventoy Plugson bug]]> https://forums.ventoy.net/showthread.php?tid=3214 Thu, 25 Jun 2026 03:07:41 +0000 VadimChoi]]> https://forums.ventoy.net/showthread.php?tid=3214
.png   IMG_20260625_120514_952.png (Size: 119.24 KB / Downloads: 7)

.png   IMG_20260625_120259_112.png (Size: 146.87 KB / Downloads: 2) ]]>
.png   IMG_20260625_120514_952.png (Size: 119.24 KB / Downloads: 7)

.png   IMG_20260625_120259_112.png (Size: 146.87 KB / Downloads: 2) ]]> <![CDATA[Ventoy-1.1.15 release]]> https://forums.ventoy.net/showthread.php?tid=3213 Thu, 25 Jun 2026 01:27:28 +0000 longpanda]]> https://forums.ventoy.net/showthread.php?tid=3213
  • 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/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
    ]]>         <![CDATA[Ventoy-1.1.14 release]]> https://forums.ventoy.net/showthread.php?tid=3212 Wed, 24 Jun 2026 11:29:50 +0000 longpanda]]> https://forums.ventoy.net/showthread.php?tid=3212
  • 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
    ]]>
  • 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
    ]]>         <![CDATA[Update needed for 2023 certificates ??]]> https://forums.ventoy.net/showthread.php?tid=3211 Sun, 21 Jun 2026 23:59:31 +0000 Epictetus77]]> https://forums.ventoy.net/showthread.php?tid=3211