DBeaver is an Eclipse RCP application. Nearly all configuration is stored in the workspace, not the registry.
The default workspace is at %USERPROFILE%\AppData\Roaming\DBeaverData\workspace6\ — this contains connection profiles (encrypted), SQL scripts, ER diagrams, and Eclipse platform settings.
Connection passwords are encrypted using a workspace-specific key stored in %USERPROFILE%\AppData\Roaming\DBeaverData\.secret.
The only registry presence is the uninstall entry; DBeaver itself reads no values from the registry at runtime.
Admin vs per-user install: Admin installs write to HKLM, per-user installs write the identical structure to HKCU.
DBeaver supports 80+ database engines via JDBC drivers; drivers are downloaded on demand to %USERPROFILE%\.dbeaver-drivers\.
🗑️ Cleanup
# System install (run as Administrator)Get-ChildItem"HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall"|Where-Object{$_.GetValue("DisplayName")-like"DBeaver*"}|ForEach-Object{Remove-Item$_.PSPath-Recurse-Force}# Per-user installGet-ChildItem"HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall"|Where-Object{$_.GetValue("DisplayName")-like"DBeaver*"}|ForEach-Object{Remove-Item$_.PSPath-Recurse-Force}