Writable Volume Exclusions

You can specify certain locations of Writable Volumes to exclude them from being persisted across sessions or getting overwritten.

As an administrator, you might want to prevent automatic updates of some applications and prefer to update the AppStacks that contain these applications manually.

When applications are automatically updated, multiple copies of the files might get created since the applications are also stored on the Writable Volumes. The existing applications then either do not behave as desired or stop working completely. To prevent this behavior, you can apply Writable Volumes exclusions to specific locations and registry paths.

You might also want to specify exclusions for the following reasons:

• Prevent certain folders such as temporary download folders, from accumulating huge, unwanted files.
• Exclude certain applications or paths. You can do this by including paths within the users' profile directories.

Important: The Writable Volumes exclusions feature is for advanced IT administrators or users who are aware of application behavior with App Volumes and want to tweak the way applications are managed or how Writable Volumes are used along with AppStacks.