-The following features are currently unsupported:
-.IP \[bu] 2
-File permissions and security descriptors are ignored. The information
-contained in them in an existing WIM will be lost when wimlib writes a WIM file.
-This does not seem to matter for Windows PE, but this means that you should not
-use this program to image a drive containing Windows Vista/7/8 and expect it to
-be applied with the correct file permissions.
-.IP \[bu] 2
-Split WIMs are not fully supported. These can be used to split up a WIM to fit
-on multiple CDs, if you can't use a DVD for some reason. You can use
-\fBimagex join\fR to combine split WIMs, but you cannot yet create split WIMs.
-.IP \[bu] 2
-The \fB--verify\fR option, for all commands that use it. Without this option,
-there theoretically could be a SHA1 hash collision between two files, although
-it's very unlikely.
-.IP \[bu] 2
-The \fB--config\fR option, for all commands that use it.
-.IP \[bu] 2
-Alternate stream entries
-.IP \[bu] 2
-Different versions of the WIM file format (if different versions even exist)
-
-Also see the Doxygen documentation for Wimlib.
+
+As of version 1.0.0, wimlib supports capturing and applying WIMs directly from
+NTFS and has much improved support for hard links and symbolic links. In
+addition, you may now apply split WIMs and mount them read-only. I don't think
+there are many other features that would be worth it to implement. Besides
+porting the library to Windows (which I'm not really interested in), the main
+thing that could use improvement (in my opinion) is that the LZX compression
+ratio still isn't quite as good as Microsoft's version. Furthermore, if
+Microsoft updates the WIM format, I'd need to support it, but it looks like the
+format for Windows 8 is the same as that of Windows 7.