[Bug Report] wimlib-imagex split XML error

[dks918]

Been having a persistent issue across Mac OS and Debian 12. Error occurs when calling "wimlib-imagex split". I'm replicating this issue by trying to create a bootable windows 11 usb drive. I move all materials from the ISO over as usual, but the "/sources/install.wim" is too large for the FAT32 file system of the target. So I call the following:

wimlib-imagex split /path/to/mounted/iso/sources/install.wim /path/to/usb/sources/install.swm 3800

The following error comes back:

encoding error : input conversion failed due to input error, bytes 0x31 0xDB 0xFB 0x4C
encoding error : input conversion failed due to input error, bytes 0x31 0xDB 0xFB 0x4C
Entity: line 1: parser error : Start tag expected, '<' not found
[ERROR] Unable to parse the WIM file's XML document!
ERROR: Exiting with error code 73:
The XML data of the WIM is invalid.

Notes: wimlib-imagex 1.13.5 (using wimlib 1.13.5)

[synchronicity]

Is this reproducible on the latest version (v1.14.3)?

[dks918]

Hey there, I have confirmed that this is happening on 1.14.3 on Mac OS.

[synchronicity]

What is the error message on v1.14.3?

Is there a way I can reproduce this?

[dks918]

Hi there,

It is the same exact error message. My original post has all the information needed to reproduce.

[synchronicity]

It is the same exact error message.

That's not possible. The second half might be the same, but the first three lines are from libxml2 which wimlib v1.14.0 and later does not use:

Code: Select all

encoding error : input conversion failed due to input error, bytes 0x31 0xDB 0xFB 0x4C
encoding error : input conversion failed due to input error, bytes 0x31 0xDB 0xFB 0x4C
Entity: line 1: parser error : Start tag expected, '<' not found

It's really helpful if bugs are reported on the latest version, not an earlier version, because things can always have changed. In this case, the XML parsing code did change significantly.

My original post has all the information needed to reproduce.

It does not mention where to get a file on which the problem reproduces. I can try the latest Windows 11 ISO from Microsoft, but I was hoping for something more specific, for example a minimal example file.

[synchronicity]

No issue seen with Win11_22H2_English_x64v2.iso.