api/drivers/rebuild: boot.wim not found

[rgl]

api/drivers/rebuild fails to rebuild the boot.wim:

curl \
        --silent \
        --show-error \
        -X POST \
        http://localhost:8081/api/drivers/rebuild \
        -H "Authorization: Bearer $bootimus_admin_token" \
        --url-query "imageId=$image_id" \
        | jq

{
  "success": true,
  "message": "Boot.wim rebuild started in background. Check logs for progress."
}

The logs show that failed as:

ERROR: Failed to rebuild boot.wim for image 7: boot.wim not found at data/isos/windows-server-2022-amd64/sources/boot.wim

This happens because the path is not correct. The actual boot.wim file path is at:

$ ll data/isos/windows-server-2022-amd64/iso/sources/boot.wim 
-rw-r--r-- 1 root root 414017113 jul 12 16:30 data/isos/windows-server-2022-amd64/iso/sources/boot.wim

There's a missing iso/ path segment.

[rgl]

please note that although #92 fixes the path, the wim rebuild fails as:

2026/07/12 15:42:56 Rebuilding boot.wim for image ID 7...
2026/07/12 15:42:56 Rebuilding boot.wim for windows-server-2022-amd64 with 1 driver pack(s)
2026/07/12 15:42:56 Creating backup of boot.wim at data/isos/windows-server-2022-amd64/iso/sources/boot.wim.backup
2026/07/12 15:42:57 Extracting driver packs...
2026/07/12 15:42:57   - Extracting windows-qemu-drivers.zip
2026/07/12 15:42:57 Listing WIM images...
2026/07/12 15:42:57 Processing 2 WIM image(s)
2026/07/12 15:42:57 Processing WIM image 1...
2026/07/12 15:42:57   Extracting image 1...
2026/07/12 15:43:03   Injecting drivers into image 1...
2026/07/12 15:43:03   Capturing modified image 1...
2026/07/12 15:43:26 Processing WIM image 2...
2026/07/12 15:43:26   Extracting image 2...
2026/07/12 15:43:26 wimextract output: ERROR: "2" is not a valid image in "data/isos/windows-server-2022-amd64/iso/sources/boot.wim"!
       Please specify a 1-based image index or image name.  To list the images
       contained in the WIM archive, run

           wiminfo "data/isos/windows-server-2022-amd64/iso/sources/boot.wim"

ERROR: Exiting with error code 18:
       Tried to select an image that does not exist in the WIM.
2026/07/12 15:43:26 ERROR: Failed to rebuild boot.wim for image 7: failed to extract WIM image 2: exit status 18

I'm using the windows server 2022 evaluation iso from https://software-static.download.prss.microsoft.com/sg/download/888969d5-f34g-4e03-ac9d-1f9786c66749/SERVER_EVAL_x64FRE_en-us.iso as scraped by https://github.com/rgl/windows-evaluation-isos-scraper/tree/main/data

Executing the wiminfo command returned:

$ docker exec -it bootimus bash
# wiminfo "data/isos/windows-server-2022-amd64/iso/sources/boot.wim"
WIM Information:
----------------
Path:           data/isos/windows-server-2022-amd64/iso/sources/boot.wim
GUID:           0x0204993f39da44936a8eebf031c7cb11
Version:        68864
Image Count:    1
Compression:    LZX
Chunk Size:     32768 bytes
Part Number:    1/1
Boot Index:     0
Size:           381361899 bytes
Attributes:     Relative path junction

Available Images:
-----------------
Index:                  1
Name:                   1
Description:            
Display Name:           Windows (TM) 10 Preinstallation Environment
Display Description:    Windows (TM) 10 Preinstallation Environment
Directory Count:        4137
File Count:             16417
Total Bytes:            1879545064
Hard Link Bytes:        871418858
Creation Time:          Sun Jul 12 15:43:03 2026 UTC
Last Modification Time: Sun Jul 12 15:43:04 2026 UTC
Architecture:           x86_64
Product Name:           Windows (TM) 10 Preinstallation Environment
Edition ID:             WindowsPE
Installation Type:      WindowsPE
Product Type:           WinNT
Languages:              en-US 
Default Language:       en-US
System Root:            WINDOWS
Major Version:          10
Minor Version:          0
Build:                  20348
Service Pack Build:     587
Service Pack Level:     0
Flags:                  WindowsPE
WIMBoot compatible:     no

PS this is now fixed at #92 too. bootimus now correctly detects the number of images:

2026/07/12 16:00:52 Rebuilding boot.wim for image ID 7...
2026/07/12 16:00:52 Rebuilding boot.wim for windows-server-2022-amd64 with 1 driver pack(s)
2026/07/12 16:00:52 Extracting driver packs...
2026/07/12 16:00:52   - Extracting windows-qemu-drivers.zip
2026/07/12 16:00:52 Listing WIM images...
2026/07/12 16:00:52 Processing 1 WIM image(s)
2026/07/12 16:00:52 Processing WIM image 1...
2026/07/12 16:00:52   Extracting image 1...
2026/07/12 16:00:58   Injecting drivers into image 1...
2026/07/12 16:00:58   Capturing modified image 1...
2026/07/12 16:01:20 Successfully rebuilt boot.wim for windows-server-2022-amd64
2026/07/12 16:01:20 Successfully rebuilt boot.wim for image 7

PPS oh. actually, that last fix is not enough... it seems when it inline updates the image using wimcapture... the boot.wim image is reset to having a single wim image count, so something else is missing.

humm, the existing code is always using wimcapture, but shouldn't that only be used to create the first image? then wimappend should be used to append the other ones?

also, this should not inline modify the final boot.wim, as when there are errors, it will be corrupted? instead, this should wimcapture/wimappend to a temporary file, and only when everything goes ok, override the original boot.wim?

also, this should never loose the original boot.wim file, correct? each time we do a bootimus api/drivers/rebuild, it should always start with the original boot.wim. otherwise, if we delete some drivers from bootimus, they will remain in the boot.wim, because that file was overriden the previous time it was rebuilt.

PPPS instead of using wimextract/wimcapture (which have caveats when executed on non-windows hosts; like loss of ntfs permissions), why not use wimupdate instead?

PPPPS I've updated #92 to inject the drivers using wimcapture and it now works as expected. the bootimus logs show:

2026/07/12 19:06:02 Rebuilding boot.wim for image ID 9...
2026/07/12 19:06:02 Rebuilding boot.wim for windows-server-2022-amd64 with 1 driver pack(s)
2026/07/12 19:06:02 Creating backup of boot.wim at data/isos/windows-server-2022-amd64/iso/sources/boot.wim.backup
2026/07/12 19:06:04 Extracting driver packs...
2026/07/12 19:06:04   - Extracting windows-qemu-drivers.zip
2026/07/12 19:06:04 Listing WIM images...
2026/07/12 19:06:04 Processing 2 WIM image(s)
2026/07/12 19:06:04 Processing WIM image 1...
2026/07/12 19:06:04   Updating image 1...
2026/07/12 19:06:05 Processing WIM image 2...
2026/07/12 19:06:05   Updating image 2...
2026/07/12 19:06:06 Successfully rebuilt boot.wim for windows-server-2022-amd64
2026/07/12 19:06:06 Successfully rebuilt boot.wim for image 9

And I can see the drivers as:

$ docker exec -it bootimus bash

# wimdir data/isos/windows-server-2022-amd64/iso/sources/boot.wim 1 | grep kvm
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvm.cat
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvm.inf
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvm.sys
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvmco.exe
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvmp.exe

# wimdir data/isos/windows-server-2022-amd64/iso/sources/boot.wim 2 | grep kvm
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvm.cat
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvm.inf
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvm.sys
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvmco.exe
/Windows/System32/DriverStore/FileRepository/NetKVM/2k22/amd64/netkvmp.exe

[rgl]

but, with a qemu kvm virtual machine, although it shows the boot menu, and the wimboot menu, the screen stays black, and nothing shows up. any idea how to troubleshoot that part?