Hi =)

i have 2 servers:
1. PXE server using iVentoy
2. testing server
i've taken two backups of the second server using REAR (Relax and Recover) and CloneZilla - both are in ISO format, with standalone unattended restore capability

now here's my problem:
when i mount the ISO (either one) directly through IPMI the ISO works fine and the system is restored (unattended)
when i boot the testing server using PXE to iVentoy environment and choose the ISO (either one) from the iVentoy list - the ISO initially loads but fails to run, system reports it can't find the restore files as if the ISO is not mounted at all

in clonezilla case - it fails in the part where it's trying to load squashfs
in rear case - it fails to find the restore data

should it technically work? or am i missing something?
let me know if you require any more info,
thanks,

I had a working version of Ventoy which I was very happy with, but it no longer boots.

I created an additional partition on my Ventoy disk and installed Linux (OpenSuse) on it. That installed it's own grub and now when I boot, the system starts OpenSuse.

How do I recover Ventoy's grub loader?

Add Device Drivers to Windows During Windows Setup | Microsoft Learn

Looking to create a Windows answer file (unattend.xml) to go with a Windows 10 install.

How do I get device drivers be available during the windowsPE stage?  I am trying to avoid modifying the Windows 10 .iso and placing the files inside there.

I understand iVentoy provides a HTTP server to serve files which I can get to work when sending PowerShell scripts during the Windows auditUser and auditSystem phases.

The problem I am facing here is that prior to configuring the drive and partitions, there needs to be specific Intel drivers to be installed before formatting and partitioning of the drives can be performed during the Windows install. I figure I am able to use the auto-injection feature of iVentoy to get the files into the X:\ boot drive however how am I able to automatically get these drivers to be installed?

Thanks

iventoy管理界面为啥不设置一个用户和密码呢

Hello, I think that might be impossible, but I'm curious.

Thanks!

I have an Intel NUC that refuses to boot iVentoy unless the boot menu resolution is set to 800x600. However, if I set the resolution that low, then every WinPE .iso I boot has a garbled display after the Windows boot logo, so I still can't get it to work. When I try higher resolutions I get errors like attached. Any ideas?

Attached Files

Thumbnail(s)
   

ventoy文件注入插件和ventoy.dat文件是否有冲突？
在使用ventoy启动PE时，若PE的ISO根目录中有ventoy.dat文件时，文件注入插件会失败；若删除根目录下的ventoy.dat文件，文件注入成功，但是这样PE启动时，会加载ISO驱动器，不能直接弹出USB（等同于ISO文件如何标记自己是 Ventoy Compatible 的功能失效。详www.ventoy.net/cn/doc_compatible_mark.html）。目前测试了多个PE都存在这种现象，不知道这个是否是一个bug，或者是我在使用文件注入插件时操作错误。希望能解决我的困惑，谢谢！

Will it be possible in future versions of iVentoy to boot BIN or IMG images like what can be done with Ventoy?

I used the guide on how to install this using windows and all methods in "When Ventoy2Disk.exe Failed To Install" worked except the VM which just stagnated on the loading screen. However when I installed the program to install ventoy gpt or mbr it always failed to install to my 1tb usb 3 generic flash drive gpt or mbr

I think this is a problem with Windows 10 ISOs.
httpdrive cant mount iso to drive y: - because of the problem with the ip configuration.

The problem does not exist on Windows 11 isos.

The iVentoy system can be reached via ping and the manual mounting of the ISO works in the recovery console of Windows Setup. I also can access drive y:
X:\windows\System32\ventoy\httpdisk.exe /mount 0 http://192.168.50.2:16000/riso/id/13.iso /cd Y:

I it possible to change your script for this configuration to wait some more time for configuration?
I already tried it with WinInjection but without solution.

IPv4-Adresse . . . . . . . . . . : 192.168.50.82(Vorläufig) or IPv4-address . . . . . . . . . . : 192.168.50.82(Tentative)
Says that a conflict check is currently being running and that probably takes too long for your script (no wait times)
(see last entrys in the log)

Here is the log file (its a german system)
==========================
[...]
Try 18 ...
X:\windows\system32>ipconfig /all

Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : minint-svhds23
Prim res DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein

Ethernet-Adapter Ethernet:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physische Adresse . . . . . . . . : 08-60-6E-68-E0-8E
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::fdf4:355d:8d00:7441%3(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.50.82(Tentative)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.50.1
DHCPv6-IAID . . . . . . . . . . . : 50880622
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2C-9A-08-78-08-60-6E-68-E0-8E
NetBIOS ber TCP/IP . . . . . . . : Aktiviert

X:\windows\system32>ping -n 1 -w 2000 192.168.50.2
Pinging 192.168.50.2 with 32 bytes of data:
PING: Error during transmission. General error.

Ping-Statistik f r 192.168.50.2:
Pakete: Gesendet = 1, Empfangen = 0, Verloren = 1
(100% Verlust),

X:\windows\system32>if 1 EQU 0 goto NETFINISH
X:\windows\system32>goto START_LOOP
X:\windows\system32>if 18 EQU 18 goto END_LOOP
X:\windows\system32>if 18 EQU 20 goto NETFINISH
X:\windows\system32>X:\windows\System32\VTOYPE.EXE SETIP
Set static IP ...
Adapter List:
pIpAdapterInfo->Address 08-60-6E-68-E0-8E
Run command <cmd /c wmic path win32_networkadapter where index=3 call enable>Run command <cmd /c netsh interface ip set address name=3 source=static addr=192.168.50.82 mask=255.255.255.0 gateway=192.168.50.1>Run command <cmd /c netsh interface ipv4 add dnsserver "3" addr=1.1.1.1 index=1>
X:\windows\system32>set /a MaxCnt=18+2
X:\windows\system32>goto START_LOOP
X:\windows\system32>if 18 EQU 20 goto END_LOOP
X:\windows\system32>set /a Count=18+1
X:\windows\system32>echo Try 19 ...
Try 19 ...
X:\windows\system32>ipconfig /all

Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : minint-svhds23
Prim res DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein

Ethernet-Adapter Ethernet:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physische Adresse . . . . . . . . : 08-60-6E-68-E0-8E
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::fdf4:355d:8d00:7441%3(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.50.82(Tentative)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.50.1
DHCPv6-IAID . . . . . . . . . . . : 50880622
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2C-9A-08-78-08-60-6E-68-E0-8E
NetBIOS ber TCP/IP . . . . . . . : Aktiviert

X:\windows\system32>ping -n 1 -w 2000 192.168.50.2
Pinging 192.168.50.2 with 32 bytes of data:
PING: Error during transmission. General error.

Ping-Statistik f r 192.168.50.2:
Pakete: Gesendet = 1, Empfangen = 0, Verloren = 1
(100% Verlust),

X:\windows\system32>if 1 EQU 0 goto NETFINISH
X:\windows\system32>goto START_LOOP
X:\windows\system32>if 19 EQU 20 goto END_LOOP
X:\windows\system32>set /a Count=19+1
X:\windows\system32>echo Try 20 ...
Try 20 ...

X:\windows\system32>ipconfig /all

Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : minint-svhds23
Prim res DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein

Ethernet-Adapter Ethernet:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physische Adresse . . . . . . . . : 08-60-6E-68-E0-8E
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::fdf4:355d:8d00:7441%3(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.50.82(Tentative)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.50.1
DHCPv6-IAID . . . . . . . . . . . : 50880622
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2C-9A-08-78-08-60-6E-68-E0-8E
NetBIOS ber TCP/IP . . . . . . . : Aktiviert

X:\windows\system32>ping -n 1 -w 2000 192.168.50.2

Pinging 192.168.50.2 with 32 bytes of data:
PING: Error during transmission. General error.

Ping-Statistik f r 192.168.50.2:
Pakete: Gesendet = 1, Empfangen = 0, Verloren = 1
(100% Verlust),

X:\windows\system32>if 1 EQU 0 goto NETFINISH
X:\windows\system32>goto START_LOOP
X:\windows\system32>if 20 EQU 20 goto END_LOOP
X:\windows\system32>if 20 EQU 20 goto NETFINISH
X:\windows\system32>X:\windows\System32\ventoy\httpdisk.exe /mount 0 http://192.168.50.2:16000/riso/id/13.iso /cd Y:
HttpDisk: The network address is not reachable. For more information about troubleshooting network problems, see Windows Help.

X:\windows\system32>if exist Y: (echo httpdisk mount OK ) else (echo httpdisk mount FAILED )
httpdisk mount FAILED