How to uninstall KeePassXC on Windows

Your passwords are in the .kdbx database you saved, wherever you put it, and uninstalling KeePassXC never touches that file. Back up the database and its key file, if you use one, and make sure you can open the backup before you continue; a database without its key file may be unusable. KeePassXC's own folders hold only its settings. This guide covers KeePassXC installed machine-wide from the KeePassXCTeam.KeePassXC winget package, a Windows Installer package. KeePassXC documentation

Quit KeePassXC first

Save and lock your database, then quit KeePassXC from its tray icon or the Database menu; closing the window may only minimize it to the tray. KeePassXC can start at sign-in through its own "Automatically launch KeePassXC at system startup" option, which shows in Settings › Apps › Startup. Check Task Manager (Ctrl+Shift+Esc) for any KeePassXC.exe still listed before you uninstall.

Remove the app with its own uninstaller

Go to Settings › Apps › Installed apps, find KeePassXC, and choose Uninstall, or run:

winget uninstall --id KeePassXCTeam.KeePassXC

It is a machine-wide Windows Installer package, so Windows asks for administrator access. The uninstaller removes the program folder, the Start Menu folder, the .kdbx file type registration and the startup entry.

Where the data lives

Check the result

Run these read-only commands after the uninstall finishes:

Get-Process KeePassXC -ErrorAction SilentlyContinue
winget list --id KeePassXCTeam.KeePassXC
Test-Path "$env:ProgramFiles\KeePassXC"
Test-Path "$env:APPDATA\KeePassXC"
Test-Path "$env:LOCALAPPDATA\KeePassXC"

• No output from Get-Process only means this query observed no matching process; a suppressed error leaves the running state unknown.
• A completed winget list query with no match means the package record is gone; a matching row means the uninstall did not finish.
• The first Test-Path returning False means the program folder is gone.
• Test-Path "$env:APPDATA\KeePassXC" returning True means your settings are still there, which is expected unless you removed them yourself.
• Test-Path "$env:LOCALAPPDATA\KeePassXC" returning True means the small state file is still there; remove it yourself if you want a clean start.

None of these check your database. Open it with a KeePass-compatible app you kept, or on another device, to confirm you still have access.

If you installed it with winget

winget uninstall runs the same Windows Installer removal Settings › Apps uses and removes the same program files; it does not touch %APPDATA%\KeePassXC, %LOCALAPPDATA%\KeePassXC or your database.

What Mole lists

For KeePassXC installed machine-wide from winget:

• The program folder goes with the app row. The Start Menu folder and a row grouping Windows' own records of when you opened the program are selected by default.
• A KeePassXC startup entry that still points at the removed program is selected by default and backed up to a .reg file before removal; in this test the uninstaller had already removed it.
• %APPDATA%\KeePassXC and HKCU\SOFTWARE\KeePassXC are listed but not selected, since they hold your settings.
• %APPDATA%\KeePass was listed too, not selected. It belongs to KeePass Password Safe, not KeePassXC, so leave it unticked unless you also removed KeePass.
• %LOCALAPPDATA%\KeePassXC was written after the review list was built, so Mole shows it in the result in its own section, not selected, with its own Move to Recycle Bin link.
• Your .kdbx database is never listed.

What this test covered

Tested on September 28, 2026 with KeePassXC 2.7.12 installed through winget, machine scope, and removed with its Windows Installer uninstaller. The app was opened once and the startup update check was declined. No database was created or opened, and browser integration was not turned on, so its connection entries in browsers were not checked.