wimlib

While I'm interested in better support for recovering from errors, it would be a big change, and I don't work very much on this project anymore. I would also expect any "vibe-coded" patch to have a human who has reviewed the patch, fully understands it, has improved it further where applicable, and ...

wimlib uses NtQueryInformationFile with FileStreamInformation to list each file's named data streams. Would you be able to confirm that Windows is indeed listing WofCompressedData as one of the named streams, despite the file not being WOF compressed (as you say)?

A hard link doesn't "point" to another file name, but rather directly to the file itself. So this question doesn't make a lot of sense. There's no "outside folder" that the links point into.

Does anyone know what could typically cause this?

Does anything appear in the error log, if you enable error logging?

On Windows, does wimlib_global_init() automatically enable privileges like SeBackupPrivilege / SeRestorePrivilege?

Yes, it enables those by default.

I've released wimlib 1.14.5:


Fixed excessive progress messages from `wimlib-imagex`. It now prints the progress updates at a more reasonable rate, improving performance.

Fixed build error with the latest version of Mingw-w64.

Fixed build error in `mount_image.c` on some old Linux distros ...

I've fixed this in commit 3b9fa443e90d382e53133d165ae79e45d7c98178. Please pull down the latest "master" branch, and it should work now.

Well, written permission from the copyright holder (me) still counts even if it's not pushed out to the repo. But sure, I understand it would be clearer if the repo itself was updated. I've pushed out a commit which updates the library license from LGPLv3+ to LGPLv2.1+.

Is this wimlib v1.14.4? And are you following the instructions from "Building from source" in the README.WINDOWS.md file?

If no programs have the files open, it should be fine since the modification times should be up-to-date.

Adding some assertions might be a good idea.

But again, the required alignment is no more than the natural alignment, i.e. __alignof__(struct avl_tree_node). That's either 4 or 8. So even if the code didn't use the bottom two bits of parent_balance for other information, it would still have ...