wimlib

Thanks for doing these tests. I've included the file list in wimlib-1.8.3-BETA2, and it now knows to force XPRESS4K compression on all files in the list. Therefore, it should now be possible to apply a full Windows image in "compact mode" using XPRESS8K, XPRESS16K, or LZX compression, with...

I've implemented the above-mentioned solution in wimlib v1.8.3-BETA2. Feel free to test it if you have a chance.

Hi, With the files you provided I was able to identify the problem. wimlib v1.8.1 and later pass a slightly different parameter to a certain libntfs-3g function, and it violated some assumptions made by libntfs-3g internally. Unfortunately this usually didn't cause things to completely break, so I n...

Two things: 1. WOF is a filesystem filter driver which must be attached to a volume to actually be usable. You can use 'fltmc' to determine whether it is attached or not, and if not attach it. It might be the case that I need to add code in wimlib to do this automatically for compact-mode extraction...

Is wofadk.sys loaded and attached to the volume to which you are applying the WIM image? A compact-mode application depends on the running operating system having wofadk.sys or wof.sys available, in addition to the target operating system.

The WOF driver does not support any LZX chunk sizes other than the default (32768 bytes).

wimlib does allow you to set a higher compression level while retaining the same chunk size (e.g. using --compress=lzx:100), but this typically improves the compression ratio by less than 1%.

Yes, that is possible. You'll need to capture a new WIM file containing the main partition; then reformat the main partition and apply the image from the WIM file with the --wimboot flag.

For improved space savings, you could use LZX compression (capture with --compress=lzx).

Thanks for testing with wimlib v1.8.2. Yes, uploading the ntfscloned image might be a way forward. An alternative might be to upload a WIM image instead. This is based on your observation that when the same WIM image was applied with wimlib v1.8.0 and wimlib v1.8.2-BETA, the problem only occurred in...

Can you provide any more information about the WIM file? What is its compression type and chunk size (check with 'wiminfo')? Do you still get the file list if you run 'wimdir'? If file data is actually corrupted for some reason (and it sounds like it is), then you cannot apply the full image with wi...

Thanks for the report. I'm not 100% what's happening but it looks like there is a native error code (NTSTATUS) being returned, probably by wofadk, which isn't mapped to a Win32 error code on Windows 7. I'm guessing this is the "Compressing this object would not save space." error code, whi...