Changing the Location of KeePass Configuration Files

Depending on your KeePass package (installer or portable), the default settings location may resolve to the installation directory or the user profile. This article explains how to locate the configuration file and shows how to move it to any directory of your choice.

The KeePass Config File

KeePass stores all settings in the file KeePass.config.xml. The location of this config file depends on your setup.

Locating the KeePass Config File

Short Answer

If you installed KeePass from the installer package, your config file is located in %APPDATA%\KeePass. If you installed KeePass from the portable ZIP package, your config file is located in the same directory as KeePass.exe.

Long Answer

The config file is searched in the directory of the KeePass.exe executable first. Only if a global file is present and contains the setting <PreferUserConfiguration>true</PreferUserConfiguration> does KeePass process per-user (local) configuration files. The KeePass installer package sets <PreferUserConfiguration> to true. The portable package does not contain a configuration file, so <PreferUserConfiguration> defaults to false. Per-user configuration files are stored in %APPDATA%\KeePass.

Changing the Location of the KeePass Config File

To specify an alternative location for the config file start KeePass from a shortcut with the -cfg-local command-line parameter. Example:

D:\Tools\KeePass\KeePass.exe -cfg-local:"d:\Data\Programconfig\KeePass\Machine1\KeePass.config.xml"

References

ConfigurationKeePass

Comments

Related Posts

Fixing VS Code UI Unresponsiveness Caused by GitHub Copilot Extension

Fixing VS Code UI Unresponsiveness Caused by GitHub Copilot Extension
This article shows a simple solution to a problem that doesn’t seem to be adequately documented: VS Code UI lags, freezes, and delays caused by the GitHub Copilot extension. Problem: VS Code UI Becoming Slow Having worked on a Python project for a while, I noticed that VS Code’s UI was frequently freezing for seconds at a time. This was happening in various places of the UI: the editor itself but also in the GitHub Copilot Chat window. Copilot also seemed to be taking more and more time getting ready to answer, and the extension-host process would fully saturate one CPU core for long periods of time.
Applications

Latest Posts

Fast & Silent 5 Watt PC: Minimizing Idle Power Usage

Fast & Silent 5 Watt PC: Minimizing Idle Power Usage
This micro-series explains how to turn the Lenovo ThinkCentre M90t Gen 6 into a smart workstation that consumes only 5 Watts when idle but reaches top Cinebench scores while staying almost imperceptibly silent. In the first post, I showed how to silence the machine by replacing and adding to Lenovo’s CPU cooler. In this second post, I’m listing the exact configuration that achieves the lofty goal of combining minimal idle power consumption with top Cinebench scores.
Hardware

Fast & Silent 5 Watt PC: Lenovo ThinkCentre M90t Modding

Fast & Silent 5 Watt PC: Lenovo ThinkCentre M90t Modding
This micro-series explains how to turn the Lenovo ThinkCentre M90t Gen 6 into a smart workstation that consumes only 5 Watts when idle but reaches top Cinebench scores while staying almost imperceptibly silent. In this first post, I’m showing how to silence the machine by replacing and adding to Lenovo’s CPU cooler. In a second post, I’m listing the exact configuration that achieves the lofty goal of combining minimal idle power consumption with top Cinebench scores.
Hardware