wimlib incorrectly working with Windows 11 24H2

[Zed45]

Hi. Host system ArchLinux+Plasma desktop. Windows 11 Enterpise 24H2 x64 Qemu/KVM (VirtManager) VM. Latest wimlib (1.14.4).
After sysprep/shutdown wimcapture produces install.wim with wrong architecture (x86). Due to this when installing Windows setup stops with error.
In setuperr.log have can not get image architecture, can not get image metadata errors.
All other isos working just fine. Windows 21H2, 23H2. So wimlib working correctly as should, I think problem related to new Windows version (24H2).
Left picture original install wim (W11 Enterprise LTSC 24H2), right picture my captured sysprepped image.
https://i.postimg.cc/x8WHZHPn/Screensho ... 164856.png

[synchronicity]

I just tested one of the images from the install.wim from Win11_24H2_English_x64.iso, and wimlib still sets the architecture property correctly.

I don't know why you're seeing differently.

By the way, wimlib gets the value by checking what architecture Windows/System32/kernel32.dll has.

[Zed45]

Thanks for testing and replying. I will try show explain bit more how i doing it. Due to my english its hard for me. My native tongue is mongolian.
Just downloaded and hash checked latest windows iso (Microsoft Windows 11 [10.0.26100.2894], Version 24H2 (Updated January 2025).
During installation entered Audit mode.
https://i.postimg.cc/zfsWmbKh/Version.png
Generalize Shutdown.
https://i.postimg.cc/HWBxX8nt/Generalize.png
Using qemu-nbd mounted as block device. Captured image still has wrong architecture property.
https://i.postimg.cc/4NgDfWsL/Capture.png
Workaround. Attaching custom PE disk to VM,booting from it. Using GimageX (quite old) capturing same partition.
https://i.postimg.cc/Jn8NDH0L/ImageX.png
Gimagex captured wim has correct architecture property, different product name. Size also smaller.
https://i.postimg.cc/brkdQ3BV/Comparision.png
Wimlib same procedure always worked for me until this 24H2 version came out. Few days ago I sysprepped 2 images (W10 LTSC 2021 wimlib captured, W11 LTSC 2024 GImageX captured). Everything working as should. For now I will be using workaround. I think, you must have much more important things to do.
Thanks for this excellent software.

[Skyblue]

Hi Zed45,

At work, I am imaging Windows 11 2024 H2 systems with wimlib 1.14. All of them are passing the stage Sysprep. No any issues. Do you use any unattend.XML file? Is that file correct?

[Zed45]

Hi. Yes Im using unattend.xml. File working correctly as intended for Windows 10, Windows 11 older versions.
Thanks, now im suspecting problem is related to my specific system. Maybe qemu packages.

[Sergey_Galan]

I also encountered this problem. In MacOS, I created a backup of Windows 11 24H2 x64 using wimlib (1.14.4).
I get the following information:

Code: Select all

----------------
Path:           /Volumes/Content/Общий доступ/Backup folder/WindowsBackup.wim
GUID:           0xeb5831061080325d1592805e20349ee0
Version:        68864
Image Count:    2
Compression:    XPRESS
Chunk Size:     32768 bytes
Part Number:    1/1
Boot Index:     0
Size:           25138059931 bytes
Attributes:     Integrity info, Relative path junction

Available Images:
-----------------
Index:                  1
Name:                   Backup 2025-08-14-00:07
Description:            
Display Name:           Windows 10 Pro
Display Description:    Windows 10 Pro
Directory Count:        56154
File Count:             253385
Total Bytes:            66550662150
Hard Link Bytes:        17844043208
Creation Time:          Wed Aug 13 21:07:33 2025 UTC
Last Modification Time: Wed Aug 13 21:08:08 2025 UTC
Architecture:           x86
Product Name:           Windows 10 Pro
Edition ID:             Professional
Installation Type:      Client
HAL:                    acpiapic
Product Type:           WinNT
Product Suite:          Terminal Server
Languages:              en-US ru-RU uk-UA 
Default Language:       ru-RU
System Root:            WINDOWS
Major Version:          10
Minor Version:          0
Build:                  26100
Service Pack Build:     4946
Service Pack Level:     0
Flags:                  Professional
WIMBoot compatible:     no

Index:                  2
Name:                   Backup 2025-09-07-23:34
Description:            
Display Name:           Windows 10 Pro
Display Description:    Windows 10 Pro
Directory Count:        64031
File Count:             236510
Total Bytes:            60569359340
Hard Link Bytes:        15961103230
Creation Time:          Sun Sep 07 20:36:27 2025 UTC
Last Modification Time: Sun Sep 07 20:37:08 2025 UTC
Architecture:           x86
Product Name:           Windows 10 Pro
Edition ID:             Professional
Installation Type:      Client
HAL:                    acpiapic
Product Type:           WinNT
Product Suite:          Terminal Server
Languages:              en-US ru-RU uk-UA 
Default Language:       ru-RU
System Root:            WINDOWS
Major Version:          10
Minor Version:          0
Build:                  26100
Service Pack Build:     5074
Service Pack Level:     0
Flags:                  Professional
WIMBoot compatible:     no

attached kernel32.dll, maybe this will help.

For the test, I made a clean installation of Windows 11 24H2 x64 and then created a backup, and there were no problems -Architecture: x86_64