我有两个U盘，都出现了安装Ventoy后在Windows下面识别极其缓慢的问题，有时候插上去过十几分钟才能识别，偶尔过了十多分钟直接提示信号灯超时，而无法识别的情况。但是U盘一旦识别，则使用完全正常，拷贝文件速度没有任何问题，也可以正常弹出。识别过程中资源管理器处于卡死状态， 磁盘管理器无法打开，任务管理器显示U盘的占用时间为100%，如果一旦拔出U盘，整个系统立刻恢复正常。如果打开事件管理器，会发现报告大量disk相关错误。
如果对U盘直接重新分区抹掉ventoy，则U盘一切正常，插上就可以正常使用，不存在识别难度，但是一旦重新做成ventoyU盘，则立刻复现此问题，即使是刚做完的空白ventoyU盘也是这样，跟里面放置多少iso没关系。
这个现象从win 11 24H2开始出现，一直延续到现在，每个ventoy版本都发现过。在win10上没发现这个问题，同样的U盘在24H2上识别困难，在win10上可以正常的速度识别。
问题跟电脑没有关系，即使是新安装的操作系统没有联网也会这样。经常出现用来安装系统的ventoyU盘在安装过程中一切正常，但是进入系统后，反而因为识别问题需要等好久才能使用。
在网络上见到过不少这个问题的帖子，但是似乎都没有给出明确的答案。

Hiyall,
I am ancient and need all the help I can get! With the help of a friend, I managed to make a Ventoy USB for Linux Mint that works well. I now want to install Tiny10 on a separate Ventoy USB to install on an Oracle VirtualBox. Following the instructions I was given for the Linux Mint-based Ventoy doesn't seem to work.

I would appreciate instructions in the following format: Do 1., then  Do 2, etc.

Hi everyone,
I’ve been using Ventoy for a while and it works great for most ISOs.
But I’m wondering how others organize multiple versions of the same ISO (like Windows/Linux) without filling up the USB too quickly.
Do you rename ISOs, use folders, or something else?
Thanks for any tips!

Good morning, I have a request, if possible.
On my Ventoy USB drive I use a folder structure, for example:

I have a router running the DHCP server and I want to use dnsmasq as a DHCP proxy for iVentoy.
The router has the address 192.168.1.1 and gives addresses in the range 192.168.1.x

The dnsmasq server runs on Ubuntu and the iVentoy server runs on Windows address 192.168.1.102

The following config does not work:
port=0
log-dhcp

dhcp-range=192.168.1.0,proxy

pxe-service=x86PC,"Test",iventoy_loader_16000,192.168.1.102

dhcp-no-override

Post (English – faithful translation)
Hello,
I am trying to boot a Ventoy USB drive in UEFI mode using QEMU with OVMF, but QEMU always drops into the EFI Shell instead of automatically booting Ventoy.
What works

• The Ventoy USB boots correctly on real hardware in UEFI mode
  
• The Ventoy USB boots correctly in QEMU using Legacy/BIOS mode
  
• From the EFI Shell, manual boot works:
  
  fsX:cd EFI\BOOTBOOTX64.EFI
  
• After running this, Ventoy starts normally.
  

• Automatic UEFI boot when using QEMU
  
• Even when using:
  • startup.nsh
    
  • placed in the root of the USB
    
  • Clean or regenerated OVMF VARS files
    
  • Passing the USB drive directly as a raw block device
    QEMU still always boots into the EFI Shell.
    

• Host OS: Linux
  
• QEMU:
  qemu-system-x86_64
  
• UEFI firmware:
  OVMF_CODE_4M.fd
  
• +
  OVMF_VARS_4M.fd
  
• USB drive passed as a raw block device
  
• Standard Ventoy layout (GPT with EFI partition)
  

• QEMU + OVMF
  
• and Ventoy UEFI boot from a USB device?
  

• recommended QEMU settings for Ventoy UEFI boot?
  
• known workarounds (other than manual EFI Shell boot)?
  
• an explanation of why OVMF does not automatically detect
  BOOTX64.EFI
  
• on the Ventoy USB?
  

w我在使用ventoy安装操作系统的时候，通常都是用无人值守的配置文件进行硬盘的重新分区。在不同电脑上硬盘会有不同的配置，尤其是有时候有些电脑会同时具有机械和固态。经过大量测试，我发现使用这个VT_WINDOWS_DISK_CLOSEST_400参数一般都可以准确选择到固态硬盘.但是这个参数有个潜在的风险，他不会避开ventoy所在的U盘。我遇到过不止一次，使用自动安装配置文件后，ventoy自身被删除了。比较常见的原因是主板开启了vmd等需要额外安装驱动的情况。这个时候就比较无语，因为这意味着我需要重新制作一个ventoy的U盘，实际使用中还是要浪费不少时间的。
有没有办法能按照磁盘大小选择磁盘，同时还能避开ventoy自身呢？实际上就是想达到VT_WINDOWS_DISK_1ST_NONVTOY 和  VT_WINDOWS_DISK_CLOSEST_400两个参数配合的效果。

I am currently working on loading and booting Ventoy from an ISO file or CD/DVD media instead of traditional USB/HDD/SSD. Is anyone interested in collaborating with me on this?"

Hi, LongPanda !
Is it possible to use the Ventoy Injection Plugin with compressed files stored on a drive other than the Ventoy drive?

Hi Every one,

I want to remove this secation please guide