Online Help > Installation > Client

Configuration File Location

Default Location


Password Vault Manager saves its configuration in a file named PasswordVaultManager.cfg. This file contains all application settings and configured data sources. All of the data source settings are encrypted for security reasons.


If Password Vault Manager is installed in a sub folder of "Program Files" and is not running on a Terminal Server, the configuration is saved in "%LocalAppData%\Devolutions\PasswordVaultManager"


If the application is running on a Terminal Server, the configuration will be saved in "%AppData%\Devolutions\PasswordVaultManager" It uses the roaming profile to avoid multi-user conflicts.


In any other case, the configuration is saved in the installation folder. This allows you to install multiple versions of the application side-by-side, as long as you don't install it in a sub folder of "Program Files" (For more information on why -- this is because of the "Program Files" virtualization introduced with Windows Vista:


Override the Default Path


There are two ways to change the default option path:


1. Create a file named "Override.cfg" in the application folder. Password Vault Manager opens this file and reads the first line. It should contain the desired installation folder (without the option filename). If you wish to use the current installation path, place a dot in the file. Here are two examples:




The config file is saved in a specific folder.


The dot is used to specify the Password Vault Manager installation folder.


Specify the application roaming data folder.



Having the configuration file in the installation folder allows you to run multiple versions of the application side-by-side.


2. By adding a key in the registry: CurrentUser\SOFTWARE\PasswordVaultManager, OptionPath. Set the desired path in the key OptionPath. Do not forget to exclude the option file name in the key.


Default Configuration


If Password Vault Manager can not locate the configuration file for a new user, it will automatically copy the file found in the application installation folder. This is useful in deploying the configuration in a Terminal Server environment. Moreover, the application will update the license key if a newer serial is found in the default configuration.