How to uninstall DBeaver on Windows

Everything you set up in DBeaver, saved connections, credentials, SQL scripts and projects, lives in one folder separate from the app. Removing DBeaver does not remove it, and deleting it removes all of that at once. Your databases themselves are not on this PC unless you run them here, and uninstalling DBeaver does nothing to them. This guide covers DBeaver Community installed per-user from the DBeaver.DBeaver.Community winget package.

Export your connections and scripts first

In DBeaver, choose File › Export, then DBeaver › Projects, to write your projects, including their connections and scripts, to an archive you can import later with File › Import (DBeaver projects documentation). Saved passwords are the easiest thing to lose: after you import on another machine, open one connection and check that it still logs in before you delete anything.

Quit DBeaver first

Quit DBeaver from its window. It runs as a Java process, so check Task Manager (Ctrl+Shift+Esc) for a lingering dbeaver process if the app seems slow to close.

Remove the app with its own uninstaller

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

winget uninstall --id DBeaver.DBeaver.Community

Where the data lives

Location	What it holds	What to do
`%APPDATA%\DBeaverData`	Your workspace: projects, connections, encrypted credentials, SQL scripts and downloaded drivers (workspace location)	Export first; keep it if you also use DBeaver Lite, which shares the same folder
`%LOCALAPPDATA%\DBeaver`	The program's own install folder	Removed by the uninstaller
`HKCU\SOFTWARE\DBeaver`	A small registry key DBeaver writes	Safe to remove

Check the result

Run these read-only commands after the uninstall finishes:

Get-Process -Name "dbeaver*" -ErrorAction SilentlyContinue
winget list --id DBeaver.DBeaver.Community
Test-Path "$env:LOCALAPPDATA\DBeaver"
Test-Path "$env:APPDATA\DBeaverData"

No output from Get-Process only means this query observed no matching process; a suppressed error leaves the running state unknown. A listed process means it is still running.
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; True means files remain there.
Test-Path "$env:APPDATA\DBeaverData" returning True means your workspace is still there, which is expected unless you removed it yourself.

If you installed it with winget

winget uninstall runs the same uninstaller Settings › Apps uses and removes the same program files; it does not touch %APPDATA%\DBeaverData on its own.

Account

DBeaver itself needs no account to run locally. Any database server credentials you saved stay only in your workspace or with the server's own account system, and removing DBeaver changes nothing on the server side.

What Mole lists

For DBeaver Community installed per-user from winget:

The program folder (%LOCALAPPDATA%\DBeaver) and the Start Menu shortcut are selected by default.
%APPDATA%\DBeaverData, where your connections and scripts live, is listed but not selected.
HKCU\SOFTWARE\DBeaver is listed but not selected.

What this test covered

Tested with DBeaver Community 26.2.0 installed through winget, per-user scope. Every listed row was ticked and removed in this test. Not verified: exporting and reimporting a project, DBeaver Lite installed alongside it, and the official installer.