wimlib

Yes, it was easier to handle this case on capture rather than on apply, and then the resulting WIM image can be applied with other versions of wimlib or with other software without any problems. Can you try it again, creating new WIM images?

As it turns out, Windows treats Data Deduplication reparse points specially and actually provides the "dereferenced" file contents even when an application explicitly asks not to dereference the reparse point. However it doesn't hide the reparse point itself. This explains the behavior you...

I haven't used Windows' deduplication support before, but it sounds like it replaces files with reparse points, the data is actually stored in chunk files in System Volume Information, and it's not transparent to applications that backup/restore reparse points directly. So if that's the case, a WIM ...

Fix is included in wimlib-1.11.0-BETA1, and wimlib.h is now included in the Windows binary release files too.

I've made all the changes I mentioned --- updates to wimlib.h and the example programs for MSVC compatibility, and including the import library (libwim.lib) and header (wimlib.h) in the Windows binary releases, in the "devel" directory. If you have time, please try wimlib-1.11.0-BETA1 from...

When statically linking to libraries it's the norm to have to explicitly link to all the dependencies.

Also note that if the application is proprietary, wimlib cannot be statically linked to it because that would violate the LGPL, which requires end users to be able to update the LGPL library.

Glad to hear you got it working! I think you're one of the first people to actually try to compile this stuff with Visual Studio. Most previous Windows users have used the DLL though LoadLibrary(), or the equivalent for whatever programming language they happen to be using. I should be able to addre...

Well, I still don't understand why the directory is named that way. Either way, I think this should be fixed, so I wrote an NTFS-3G patch to allow setting short (DOS) names on files whose long names end in a space or dot. I sent it to the NTFS-3G mailing list but I do not know when it might make it ...

The problem is that NTFS-3G doesn't allow setting short names on files whose long name ends in a space or period. This differs from the Windows behavior which is to allow short names on such files. I'll try to figure out if NTFS-3G should be changed to allow this case. I would however wonder whether...

If you cannot provide the WIM file, the output of could also be useful (replace $WIMFILE with the WIM file path).