-.TH WIMLIB-IMAGEX "1" "November 2015" "wimlib 1.8.3" "User Commands"
+.TH WIMLIB-IMAGEX "1" "January 2016" "wimlib 1.9.0" "User Commands"
.SH NAME
wimlib-imagex-capture, wimlib-imagex-append \- Create or append a WIM image
.SH SYNOPSIS
.IP \[bu]
All names of all files, including names in the Win32 namespace, DOS namespace,
Win32+DOS namespace, and POSIX namespace. This includes hard links.
+.IP \[bu]
+Object IDs.
.PP
However, the main limitations of this NTFS volume capture mode are:
.IP \[bu] 4
considered an error condition.
.IP \[bu]
Hard links, if supported by the source filesystem.
+.IP \[bu]
+Object IDs, if supported by the source filesystem.
.PP
-There is no support for storing NTFS extended attributes and object IDs.
+There is no support for storing NTFS extended attributes.
.PP
The capture process is reversible, since when \fBwimlib-imagex apply\fR (on
Windows) extracts the captured WIM image, it will extract all of the above
See the documentation for this option in \fBwimlib-imagex-optimize\fR (1).
.TP
\fB--snapshot\fR
-EXPERIMENTAL: create a temporary filesystem snapshot of the source directory and
-capture the files from it. Currently, this option is only supported on Windows,
-where it uses the Volume Shadow Copy Service (VSS). Using this option, you can
-create a consistent backup of the system volume of a running Windows system
-without running into problems with locked files. For the VSS snapshot to be
+Create a temporary filesystem snapshot of the source directory and capture the
+files from it. Currently, this option is only supported on Windows, where it
+uses the Volume Shadow Copy Service (VSS). Using this option, you can create a
+consistent backup of the system volume of a running Windows system without
+running into problems with locked files. For the VSS snapshot to be
successfully created, \fBwimlib-imagex\fR must be run as an Administrator, and
it cannot be run in WoW64 mode (i.e. if Windows is 64-bit, then
\fBwimlib-imagex\fR must be 64-bit as well).