starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-26 07:35:57 +03:00

[GH-ISSUE #108] Windows Installers prompt for a Driver #1584

New issue

Closed

opened 2026-03-01 18:34:38 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 18:34:38 +03:00

Owner

Originally created by @cpressland on GitHub (Aug 17, 2016).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/108

After extracting both a Windows 7 and Windows 10 ISO onto a CentOS 7.2 Server running Nginx 1.6.3 Netboot successfully boots the ISO, however, the installation cannot run due to some missing driver. My expectation is that this is fundamentally a Windows issue. See attached screenshots.

After the wimboot process starts, I can see the following logging in the Nginx access log:

10.166.16.205 - - [17/Aug/2016:15:17:49 +0100] "GET /x64/bootmgr HTTP/1.1" 200 400228 "-" "iPXE/1.0.0+ (f6e8)" "-"
10.166.16.205 - - [17/Aug/2016:15:17:49 +0100] "GET /x64/boot/bcd HTTP/1.1" 200 16384 "-" "iPXE/1.0.0+ (f6e8)" "-"
10.166.16.205 - - [17/Aug/2016:15:17:50 +0100] "GET /x64/boot/boot.sdi HTTP/1.1" 200 3170304 "-" "iPXE/1.0.0+ (f6e8)" "-"
10.166.16.205 - - [17/Aug/2016:15:17:57 +0100] "GET /x64/sources/boot.wim HTTP/1.1" 200 257783122 "-" "iPXE/1.0.0+ (f6e8)" "-"

But I'm not seeing any further requests following this, so it would seem like windows is able to boot, but the installer is missing and not loaded from HTTP.

Originally created by @cpressland on GitHub (Aug 17, 2016). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/108 After extracting both a Windows 7 and Windows 10 ISO onto a CentOS 7.2 Server running Nginx 1.6.3 Netboot successfully boots the ISO, however, the installation cannot run due to some missing driver. My expectation is that this is fundamentally a Windows issue. See attached screenshots. ![screen shot 2016-08-17 at 13 23 38](https://cloud.githubusercontent.com/assets/6557665/17736610/a8cebb46-6480-11e6-874f-5b47a6b3be45.png) ![screen shot 2016-08-17 at 13 40 15](https://cloud.githubusercontent.com/assets/6557665/17736611/ac523b94-6480-11e6-9b5d-cc8d128a53e8.png) After the wimboot process starts, I can see the following logging in the Nginx access log: ``` 10.166.16.205 - - [17/Aug/2016:15:17:49 +0100] "GET /x64/bootmgr HTTP/1.1" 200 400228 "-" "iPXE/1.0.0+ (f6e8)" "-" 10.166.16.205 - - [17/Aug/2016:15:17:49 +0100] "GET /x64/boot/bcd HTTP/1.1" 200 16384 "-" "iPXE/1.0.0+ (f6e8)" "-" 10.166.16.205 - - [17/Aug/2016:15:17:50 +0100] "GET /x64/boot/boot.sdi HTTP/1.1" 200 3170304 "-" "iPXE/1.0.0+ (f6e8)" "-" 10.166.16.205 - - [17/Aug/2016:15:17:57 +0100] "GET /x64/sources/boot.wim HTTP/1.1" 200 257783122 "-" "iPXE/1.0.0+ (f6e8)" "-" ``` But I'm not seeing any further requests following this, so it would seem like windows is able to boot, but the installer is missing and not loaded from HTTP.

kerem closed this issue

2026-03-01 18:34:38 +03:00

kerem commented

2026-03-01 18:34:38 +03:00

Author

Owner

@antonym commented on GitHub (Aug 17, 2016):

See these posts for more info:

http://forum.ipxe.org/showthread.php?tid=7059
http://ipxe.org/howto/winpe

I haven't had time to play around with this myself, but I believe you'll need to kick off the installer from a network share once you're up and running. Loading the installer itself can't see the media.

@antonym commented on GitHub (Aug 17, 2016): See these posts for more info: http://forum.ipxe.org/showthread.php?tid=7059 http://ipxe.org/howto/winpe I haven't had time to play around with this myself, but I believe you'll need to kick off the installer from a network share once you're up and running. Loading the installer itself can't see the media.

kerem commented

2026-03-01 18:34:39 +03:00

Author

Owner

@cpressland commented on GitHub (Aug 17, 2016):

Awesome, thanks! Sorry for not researching this in a little more detail. Converted the netboot target to a WinPE image and all was fine.

@cpressland commented on GitHub (Aug 17, 2016): Awesome, thanks! Sorry for not researching this in a little more detail. Converted the netboot target to a WinPE image and all was fine.

kerem referenced this issue

2026-03-01 18:38:13 +03:00

[GH-ISSUE #1584] Proxmox advanced options not visible #2059

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#1584

No description provided.

Rows
Columns