wimlib

Please explain your problem more clearly. I don't speak German, I don't know exactly which of the 5 images you are comparing to what, I don't know what software you are using to view the WIM images and what values it's showing you. Can you provide a minimal reproducer using the wimlib-imagex command...

wimlib supports LZX window size up to 2 MiB. You simply need to use the options I suggested. But as I said, WIM uses independently decompressible chunks, which can result in worse compression ratio than CAB at same LZX window size, even though wimlib's LZX compressor (given a high enough compression...

CAB has an advantage in compression ratio because it doesn't divide the data into independently decompressible chunks, whereas WIM does. But if you don't need independently decompressible chunks, you might as well use LZMS compression with its much larger chunks. I don't believe DISM in Windows 7 ev...

Why it is using the weakest LZX:15 compression instead of LZX:21, like in WinCab? Because that's the only LZX setting that's compatible with Microsoft's WIM software (WIMGAPI, DISM, ImageX). If you don't mind your archives being compatible with wimlib only, you can use: wimcapture --solid --solid-c...

The changes are always summarized in the NEWS file that's included in all the downloads. For v1.13.1 there was just a single bug fix: Version 1.13.1: Fixed a crash or incorrect output during LZMS compression with a compression level greater than 50 and a chunk size greater than 64 MiB. This affected...

I don't think I can figure out the remaining problem(s) anytime soon without being able to reproduce it myself. I don't have much to go on, and I have limited time. So for now I went ahead and released v1.13.1 with the fix I mentioned, so at least one bug is fixed. I don't suppose there's any chance...

Indeed, integrity tables (as can be enabled by --check) are mostly pointless because all file data and file metadata in WIM archives is already checksummed. However, the integrity table does cover the WIM's blob lookup table, which says where all the file data and metadata is in the file. That other...

I've found and fixed a bug that may have caused this. It resulted in a crash or incorrect output when LZMS compression was used with both a compression level and a chunk size greater than the defaults. The fix is in wimlib-1.13.1-BETA1. Can you try it from the Downloads page? However, if the informa...

1. Is there a way to open wim file via stdin? Only if the WIM file was created in the "pipable" format, which is only supported by wimlib and is not the default. 2. Is it possible to create a uncompressed wim file? Yes, just use --compress=none. 3. Is it possible to create a new wim file as a split...

FYI I had asked for --threads=1 too. That would reveal whether the problem always occurs at the same place in the data. Anyway, if it works reliably with --solid-compress=LZMS:100 --solid-chunk-size=64M as indicated by your Attempt 7, that's useful to know too; it suggests the problem is exclusive t...