+- Ventoy Forums (https://forums.ventoy.net)
+-- Forum: iVentoy General Use —— iVentoy 使用交流 (https://forums.ventoy.net/forumdisplay.php?fid=7)
+--- Forum: iVentoy Discussion Forum (https://forums.ventoy.net/forumdisplay.php?fid=8)
+--- Thread: Trouble installing Windows 11 (/showthread.php?tid=2847)
Pages:
1
2
Trouble installing Windows 11 - kev043 - 04-14-2024
Hi there, as other people have been posting the same error, I can't seem to find a way around it, I've followed all the advice in other posts with the same issue
First my setup... I have iventoy 1.0.20 on a Linux server, I've forwarded port 26000 in my router, I added a fresh iso of windows 11 from Microsoft, I tested iventoy first in a virtual machine and the install of windows 11 worked fine but when it comes to my 2 other main systems the install fails saying it needs to load a missing driver, I can ping the server and get a reply and see the install pc's network mac address in iventoy
This is my first system
Gigabyte Z590 AORUS PRO AX
Intel Core I5 11600k
Intel i225v LAN
Kingston SNVS250G NVME
My other system is based on an Intel 12th gen cpu and that fails in the same way
I even tested the windows version and that fails in exactly the same way, I've also tried disabling windows firewall and temporarily disabled firewall rules in the unifi router but still do luck.
I really appreciate the help and this is an amazing piece of software thank you.
RE: Trouble installing Windows 11 - sklerder - 04-14-2024
Hi kev043.
I may be wrong, but you probably need the IRST driver to make Windows installer to recognize you NVMe ...
Can you, in your BIOS/EFI settings change the storage driver to AHCI ?
If the issue comes from this setting, it could (and should) work, but in AHCI mode only.
If you can't force to AHCI, the only way I'm aware of is to integrate the IRST driver in an injector.
RE: Trouble installing Windows 11 - kev043 - 04-14-2024
Hi sklerder
Thank you for the info but I'm not sure if it is that because when the install fails I bring up a command prompt run diskpart and list disks I can see my nvme boot drive, I've tried to add the Intel Rapid Storage Technology Driver from a usb but it doesn't accept the driver.
RE: Trouble installing Windows 11 - sklerder - 04-14-2024
If you can see the NVMe drive from cmd console, then, the issue is not with the IRST driver.
Could you check that you see the Y: drive in this case ?
RE: Trouble installing Windows 11 - sklerder - 04-14-2024
This seems to be the issue with the network card starting too slowly (when starting, VTOYPE.BAT doesn't find the NIC and then doesn't initialize drive Y:, thus can't continue on installation).
Are you sure you have the iVentoy 1.0.20 ? (This issue is supposed to be solved in 1.0.20, but was present under 1.0.19).
Can you post the content of your "X:\Windows\System32\ventoy\vtoype.log" ?
For further reading, please consult these links :
- https://www.iventoy.com/en/doc_win_driver.html
- https://forums.ventoy.net/showthread.php?tid=2676
RE: Trouble installing Windows 11 - kev043 - 04-15-2024
Hi sklerder , yes 100% this is my version - Version 1.0.20 Linux 64-bit, When I try to run that log I get this error An attempt was made to reference a token that does not exist
RE: Trouble installing Windows 11 - sklerder - 04-15-2024
Hi kev043.
In "cmd", could you launch the command "type X:\Windows\System32\ventoy\vtoype.log" and then copy/paste the result in this discussion ?
RE: Trouble installing Windows 11 - sklerder - 04-15-2024
Well, just start an iso installation (W11 for example), without any unattended.xml file.
When you obtain the first installation screen (where you can choose between Repair and Install), just press SHIFT+F10 to obtain the command prompt.
And then, launch the "type X:\Windows\System32\ventoy\vtoype.log" and copy/paste all the content of the cmd screen (there may be many lines before those that are displayed, the most important are at the beginning, so please copy ALL the lines).
RE: Trouble installing Windows 11 - kev043 - 04-15-2024
Hi sklerder
here is the log, thank you.
X:\Windows\System32>REM ========== VTOY PE INIT =============
X:\Windows\System32>set Drive=Y
X:\Windows\System32>set URL=http://192.168.1.109:16000/riso/id/1.iso
X:\Windows\System32>set SERVER=192.168.1.109
X:\Windows\System32>set MAC=04-7C-16-DF-A0-BE
X:\Windows\System32>wpeinit
X:\Windows\System32>X:\windows\System32\VTOYPE.EXE WAITNIC 30
Wait for NIC (04-7C-16-DF-A0-BE for 30 seconds
[i=0] NIC NOT found, wait and retry
[i=1] NIC NOT found, wait and retry
[i=2] NIC NOT found, wait and retry
Adapter List:
pIpAdapterInfo->Address 04-7C-16-DF-A0-BE
[i=3] NIC found OK
X:\Windows\System32>netcfg -winpe
Trying to install ms_tcpip6 ...
... done.
Trying to install ms_netbios ...
... done.
Trying to install ms_msclient ...
... done.
Trying to install ms_tcpip ...
... done.
X:\Windows\System32>set Count=0
X:\Windows\System32>set MaxCnt=10
X:\Windows\System32>if 0 EQU 10 goto END_LOOP
X:\Windows\System32>set /a Count=0+1
X:\Windows\System32>echo Try 1 ...
Try 1 ...
X:\Windows\System32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : minint-anhuefc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek® PCI(e) Ethernet Controller
Physical Address. . . . . . . . . : 04-7C-16-DF-A0-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::58:1ec:628a:9bc1%3(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 50625558
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-AE-F2-99-04-7C-16-DF-A0-BE
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
X:\Windows\System32>ping -n 2 -w 2000 192.168.1.109
Pinging 192.168.1.109 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.1.109:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
X:\Windows\System32>if 1 EQU 0 goto NETFINISH
X:\Windows\System32>goto START_LOOP
X:\Windows\System32>if 1 EQU 10 goto END_LOOP
X:\Windows\System32>set /a Count=1+1
X:\Windows\System32>echo Try 2 ...
Try 2 ...
X:\Windows\System32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : minint-anhuefc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek® PCI(e) Ethernet Controller
Physical Address. . . . . . . . . : 04-7C-16-DF-A0-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::58:1ec:628a:9bc1%3(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 50625558
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-AE-F2-99-04-7C-16-DF-A0-BE
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
X:\Windows\System32>ping -n 2 -w 2000 192.168.1.109
Pinging 192.168.1.109 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.1.109:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
X:\Windows\System32>if 1 EQU 0 goto NETFINISH
X:\Windows\System32>goto START_LOOP
X:\Windows\System32>if 2 EQU 10 goto END_LOOP
X:\Windows\System32>set /a Count=2+1
X:\Windows\System32>echo Try 3 ...
Try 3 ...
X:\Windows\System32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : minint-anhuefc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek® PCI(e) Ethernet Controller
Physical Address. . . . . . . . . : 04-7C-16-DF-A0-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::58:1ec:628a:9bc1%3(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 50625558
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-AE-F2-99-04-7C-16-DF-A0-BE
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
X:\Windows\System32>ping -n 2 -w 2000 192.168.1.109
Pinging 192.168.1.109 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.1.109:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
X:\Windows\System32>if 1 EQU 0 goto NETFINISH
X:\Windows\System32>goto START_LOOP
X:\Windows\System32>if 3 EQU 10 goto END_LOOP
X:\Windows\System32>set /a Count=3+1
X:\Windows\System32>echo Try 4 ...
Try 4 ...
X:\Windows\System32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : minint-anhuefc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek® PCI(e) Ethernet Controller
Physical Address. . . . . . . . . : 04-7C-16-DF-A0-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::58:1ec:628a:9bc1%3(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 50625558
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-AE-F2-99-04-7C-16-DF-A0-BE
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
X:\Windows\System32>ping -n 2 -w 2000 192.168.1.109
Pinging 192.168.1.109 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.1.109:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
X:\Windows\System32>if 1 EQU 0 goto NETFINISH
X:\Windows\System32>goto START_LOOP
X:\Windows\System32>if 4 EQU 10 goto END_LOOP
X:\Windows\System32>set /a Count=4+1
X:\Windows\System32>echo Try 5 ...
Try 5 ...
X:\Windows\System32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : minint-anhuefc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek® PCI(e) Ethernet Controller
Physical Address. . . . . . . . . : 04-7C-16-DF-A0-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::58:1ec:628a:9bc1%3(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 50625558
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-AE-F2-99-04-7C-16-DF-A0-BE
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
X:\Windows\System32>ping -n 2 -w 2000 192.168.1.109
Pinging 192.168.1.109 with 32 bytes of data:
PING: transmit failed. General failure.
Reply from 192.168.1.109: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.109:
Packets: Sent = 2, Received = 1, Lost = 1 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
X:\Windows\System32>if 0 EQU 0 goto NETFINISH
X:\Windows\System32>X:\windows\System32\ventoy\httpdisk.exe /mount 0 http://192.168.1.109:16000/riso/id/1.iso /cd Y:
Y:: The system cannot find the path specified.
X:\Windows\System32>if exist Y: (echo httpdisk mount OK ) else (echo httpdisk mount FAILED )
httpdisk mount FAILED
RE: Trouble installing Windows 11 - sklerder - 04-15-2024
Weird ...
The ping to 192.168.1.109 (your PXE server, normally) is long to give the first answer (more than 5 seconds).
And the attempt to mount the ISO fails as if the ISO wasn't present.
Are you sure to not have any other PXE server in this installation ?