Ventoy Forums
Portal

Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  

Search Forums

(Advanced Search)

Forum Statistics
» Members: 13,798
» Latest member: thfox
» Forum threads: 1,679
» Forum posts: 6,737

Full Statistics

Online Users
There are currently 481 online users.
» 0 Member(s) | 476 Guest(s)
Applebot, Baidu, Bing, Google, Yandex

Latest Threads
Lost ISO partition
Forum: Ventoy Discussion Forum
Last Post: Rootman
4 hours ago
» Replies: 2
» Views: 1,591
Default to BIOS boot
Forum: iVentoy Discussion Forum
Last Post: eilmrein
12-13-2025, 01:41 PM
» Replies: 2
» Views: 5,855
Remove Secation from Them...
Forum: Ventoy Plugin Forum
Last Post: Somii
12-13-2025, 12:30 PM
» Replies: 0
» Views: 80
About the low activity
Forum: Ventoy Discussion Forum
Last Post: Susan028
12-13-2025, 11:22 AM
» Replies: 5
» Views: 9,694
VHD don't work
Forum: Ventoy Plugin Forum
Last Post: Susan028
12-08-2025, 09:37 AM
» Replies: 2
» Views: 6,535
How can i recover control...
Forum: Ventoy Discussion Forum
Last Post: elreydelaswasas1
11-26-2025, 04:05 PM
» Replies: 0
» Views: 473
ventoy运行windows系统镜像问题
Forum: Ventoy Discussion Forum
Last Post: leo
11-21-2025, 12:29 PM
» Replies: 0
» Views: 865
Boot 32 bit Windows
Forum: Ventoy Plugin Forum
Last Post: Steve2926
11-07-2025, 11:03 AM
» Replies: 3
» Views: 8,376
Live ISO Building ?
Forum: Ventoy Discussion Forum
Last Post: Eliott
10-31-2025, 02:02 AM
» Replies: 1
» Views: 1,453
Menu Spacing
Forum: Ventoy Discussion Forum
Last Post: fan_boy
10-30-2025, 03:49 AM
» Replies: 0
» Views: 655

 
  EFI not work with external DHCP on other subnet
Posted by: itgao - 07-19-2023, 06:32 AM - Forum: iVentoy Discussion Forum - Replies (6)

Hello,


On the same network iventoy works fine (bios & uefi), but on other subnet bios work but not uefi.
I tried with latest release (1.0.14)


thanks for your work Smile



Attached Files Thumbnail(s)
   
Print this item

  隐藏EFI盘符 Hidden EFI volume
Posted by: 塞北的雪 - 07-18-2023, 04:28 PM - Forum: Ventoy Discussion Forum - Replies (1)

每次看到EFI盘符很不爽，想着隐藏掉，以下保存为批处理.bat格式，右键，管理员身份运行
save to .bat and run as admin

Code:
@echo off
setlocal enabledelayedexpansion
if exist %temp%\ventoy_vol.txt (
    del %temp%\ventoy_vol.txt
)
if exist %temp%\ventoy_diskpart_cmd.txt (
    del %temp%\ventoy_diskpart_cmd.txt
)
echo list volume >%temp%\ventoy_diskpart_cmd.txt
diskpart /s %temp%\ventoy_diskpart_cmd.txt |findstr /i VTOYEFI >%temp%\ventoy_vol.txt
echo Find Volume：
type %temp%\ventoy_vol.txt
for /f "tokens=1,2,3" %%a in (%temp%/ventoy_vol.txt) do (
    set "volumeNumber=%%b"
    set "volumeLetter=%%c"
    echo volumeNumber： !volumeNumber!
    echo volumeLetter： !volumeLetter!
)
if "!volumeNumber!" EQU "" (
    echo 未找到目标卷标编号，即将退出 volumeNumber not found
    ping -n 5 127.0.0.1>nul
    exit
)
if "!volumeLetter!" EQU "" (
    echo 未找到目标驱动器号，即将退出 volumeLetter not found
    ping -n 5 127.0.0.1 >nul
    exit
)
rem echo select volume !volumeNumber!
rem echo remove letter=!volumeLetter!
echo select volume !volumeNumber! >%temp%\ventoy_diskpart_cmd.txt
echo remove letter=!volumeLetter! >>%temp%\ventoy_diskpart_cmd.txt
diskpart /s %temp%\ventoy_diskpart_cmd.txt
echo 隐藏完毕 Done.
del %temp%\ventoy_diskpart_cmd.txt
del %temp%\ventoy_vol.txt

save to delete_volume_with_label.bat or what you like.

Print this item

  求助arm架构下报错，见正文
Posted by: loooong - 07-18-2023, 07:55 AM - Forum: Ventoy Discussion Forum - Replies (1)

纯小白一枚；求助各位大佬；电脑平台：麒麟990/9006c  arm结构 属华为PC；系统镜像：UOSV20(1050)/KOS(2203)，系统镜像使用ultalso刻录至U盘正常进入系统；ventoy制作好后 在X86架构 win系统镜像能正常进入引导并成功安装系统；但是在arm架构990/9006cCPU下面 进入后提示报错见附件；烦请有什么好的 解决方法
  
报错内容：Synchronous Exception at 0*0000000075dd22b0

Print this item

  iVentoy 启动映射网络驱动器的问题
Posted by: Solin - 07-18-2023, 05:58 AM - Forum: iVentoy Discussion Forum - Replies (32)

iventoy 版本：1.0.14
启动 Windows 10 安装程序提示找不到介质，根据说明用 Shift+F10 打开命令行，发现网卡正常识别，查看日志发现日志里网卡未获取到IP地址，手工重新执行挂载命令能正常挂载 iso 到 Y：，测试环境的 DHCP 服务获取 IP 地址的时间比较长，怀疑是驱动加载后还未获取到IP地址即开始挂载 ISO 导致挂载失败，测试银河麒麟安装盘也有类似情况，不知是否能增加等待 DHCP 获取地址时间或者能自定义 IP 地址获取等待时间来规避这个问题。

Print this item

Heart iVentoy-1.0.14 release
Posted by: longpanda - 07-18-2023, 04:28 AM - Forum: iVentoy Discussion Forum - Replies (1)

  • 2023/07/18 --- 1.0.14 release
  1. Fix a bug when booting some Linux ISO.

  2. Document: About Windows Driver Missing Error

  3. Bugfix, comments and suggestions are welcome.
Print this item

  iVentoy 1.0.13 release, BitDefender detects as virus
Posted by: dimitrirodis - 07-18-2023, 04:08 AM - Forum: iVentoy Discussion Forum - No Replies

BitDefender is blocking access to the iVentoy downloads, and is also deleting the iVentoy_64.exe as malicious. Please see the attached screenshot.

Can you please check the release, possibly digitally sign the executables, and submit the false positive report to BitDefender?



Attached Files Thumbnail(s)
   
Print this item

Exclamation PCs and thinclient mentioned below are not compatible with IVentoy
Posted by: aboamir@gmail.com - 07-17-2023, 12:51 PM - Forum: iVentoy Discussion Forum - Replies (4)

Today, I tested the following hardware items With Iventoy, but unfortunately, none of them are functioning properly. 

I conducted tests with both legacy and UEFI modes.

Hp Thin client 520
Hp Thin client 530
Hp Thin client 540

Hp Rp 5800
Hp Rp 5810

the pc come to point =(((Dhcp / then exit))

Print this item

Heart iVentoy-1.0.13 release
Posted by: longpanda - 07-17-2023, 09:56 AM - Forum: iVentoy Discussion Forum - Replies (2)

  • 2023/07/17 --- 1.0.13 release
  1. Fix the driver missing issue when booting some Windows ISO files.

  2. Fix the HTTP reconnect issue when downloading files from iVentoy.

  3. Bugfix, comments and suggestions are welcome.
Print this item

Heart iVentoy-1.0.12 release
Posted by: longpanda - 07-17-2023, 03:47 AM - Forum: iVentoy Discussion Forum - No Replies

  • 2023/07/17 --- 1.0.12 release
  1. Fix the driver missing issue when booting some Windows ISO files.

  2. Bugfix, comments and suggestions are welcome.
Print this item

  Experiencing red screen of death on boot
Posted by: bootsie123 - 07-16-2023, 08:21 PM - Forum: iVentoy Discussion Forum - Replies (5)

Hi!

I'm trying to PXE boot into iVentoy from an HPE DL360 G6 and I keep on getting the red screen of death. As far as I can tell, everything is working correctly (meaning the server is getting an IP through DHCP from iVentoy and is able to communicate with it) until iVentoy serves the boot file which shows the list of bootable ISOs.

I'm not really sure where to begin debugging this so if anyone has any suggestions that would be great! Thanks!

iVentoy Logs:

Code:
2023/07/16 01:22:39.721 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:39.721 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:39.721 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:39.722 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:39.722 [DHCP] DHCP boot file is <ipxe.bios.0>
2023/07/16 01:22:44.774 [DHCP] Proc DHCP REQUEST pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:44.775 [DHCP] Recv DHCP Offer Request from 1cc1-de6f-fa68, response DHCP ACK
2023/07/16 01:22:44.775 [TFTP] Parse tftp option(tsize,0)
2023/07/16 01:22:44.775 [TFTP] TFTP RRQ client 192.168.3.200:2070 download <ipxe.bios.0> start ...
2023/07/16 01:22:44.775 [TFTP] Start send file ipxe.bios.0 to 192.168.3.200:2070 with blksize 512, has oack 1
2023/07/16 01:22:44.776 [TFTP] Recv an ERROR opcode pkt from client 192.168.3.200:2070.
2023/07/16 01:22:44.776 [TFTP] Parse tftp option(blksize,1456)
2023/07/16 01:22:44.776 [TFTP] TFTP RRQ client 192.168.3.200:2071 download <ipxe.bios.0> start ...
2023/07/16 01:22:44.776 [TFTP] Start send file ipxe.bios.0 to 192.168.3.200:2071 with blksize 1456, has oack 1
2023/07/16 01:22:44.802 [TFTP] Finished send file to 192.168.3.200:2071 with blksize 1456 blks 92
2023/07/16 01:22:53.009 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:53.009 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:53.009 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:53.009 [PXE]  Client 1c-c1-de-6f-fa-68 start PXE install in Legacy BIOS mode.
2023/07/16 01:22:53.009 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:53.009 [DHCP] DHCP boot file is <http://192.168.3.15:16000/ipxe/01-1c-c1-de-6f-fa-68>
2023/07/16 01:22:54.002 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:54.002 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:54.002 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:54.002 [PXE]  Client 1c-c1-de-6f-fa-68 start PXE install in Legacy BIOS mode.
2023/07/16 01:22:54.002 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:54.002 [DHCP] DHCP boot file is <http://192.168.3.15:16000/ipxe/01-1c-c1-de-6f-fa-68>
2023/07/16 01:22:56.034 [DHCP] Proc DHCP REQUEST pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:56.034 [DHCP] Recv DHCP Offer Request from 1cc1-de6f-fa68, response DHCP ACK
2023/07/16 01:23:56.165 [HTTP] Client 192.168.3.200:34504 (51) timeout

RSOD:
   

Print this item