Win10 httpdisk not mounted / network script to fast

[AngelKing]

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

[sklerder]

../
I already tried it with WinInjection but without solution.
/...

Hi all.

I met the same issue, and solved it with WinInjection :
- Copied the VTOYPE.BAT script in the injector tree
- Modified the copy for ping : replaced "-n 1" by "-n 2" (with ping -n 1, there's no timeout, and as the -w timeout is 2000ms, with -n 2, we'll wait at least 2  seconds)
- Modified the Autorun script to copy the modified VTOYPE.BAT over the standard one (be sure to use absolute path in the copy ...)
- Created the Wininjection file and attached it to the Windows 10 iso.

I verified after execution, the Y: drive is present and it takes only one iteration to make the network OK (the second ping of the first iteration is OK).

As a short term solution, WinInjection works, for long term, it should be better to change "ping -n 1" by "ping -n 2" in the original VTOYPE.BAT script

[longpanda]

I will change "ping -n 1" by "ping -n 2" in the next release.

[sklerder]

Thanks longpanda.

On my side, after about 10 Windows installations, it works very well on a Dell 3020 since I made this modification (never worked before, but, maybe, different NICs could work correctly without modification).
The second thing with this issue is that I have learnt how to deal with Windows injection