wimlib

I don't think it's realistic to expect wimlib to process incorrect XML documents. wimlib uses a standards compliant XML parser. You should find out why these characters were inserted in the first place, so you can solve the problem at its source. For its part, wimlib should always create well-formed...

Sounds like the WIM file's XML document contains characters that are forbidden by the XML standard. Where did this file come from?

Good to see you found the code useful. However, there are a few reasons why I am a little hesitant to merge it into the master branch. * The proposed code would live alongside the "generic" UNIX capture/apply code, but really would be specific not only to Linux but to a specific filesystem...

Creating archives from directory trees which are being concurrently modified is not supported. There are many race conditions which can occur in such scenarios.

Yes it should just work from Linux. It's just Windows 8.1 and later that has special handling of this new ACE type.

I don't know. It might be necessary to test different types of apps, including paid apps, as you've suggested. It certainly would be quite hostile to users, on Microsoft's part, if your apps would inevitably break after a simple backup and restore. Regardless, I'm not planning to update wimlib to au...

I believe this will be harder to work around than I initially thought. The real problem is extracting data to nondirectory files. Obviously, to extract any data at all to a nondirectory file, wimlib needs write access to it. Normally, if there is an existing nondirectory file at a location at which ...

Thanks. I am not sure why a network filesystem on Windows would be unreliable as such, but it makes sense that data would need to be paged from the DLL at the very end of the process, when the output shows "100% done". Before then it is running the same code over and over again, for severa...

I'm very suspicious of the error codes you are seeing: C0000006 = STATUS_IN_PAGE_ERROR C00000C4 = STATUS_UNEXPECTED_NETWORK_ERROR Is either the source WIM file or wimlib-imagex located on a network filesystem, or any sort of device which might be producing I/O errors? You should also try running the...

Thanks. Unfortunately I don't have much chance of tracking down this problem if you can't provide a smaller example that reproduces it. The crash isn't even in wimlib but rather in ntdll, so it could be memory corruption or pretty much anything else that occurred prior to the point of the crash... a...