Windows - Software - Uninstall DBeaver

What the DBeaver uninstaller does

This Automox Worklet™ uninstalls DBeaver database management software from Windows endpoints. The Worklet scans the system registry for DBeaver installations in both 32-bit and 64-bit program directories, detects whether the software is present, and removes all system-wide installations.

DBeaver is a popular open-source database management tool that provides SQL editing, data visualization, and connection management across multiple database platforms. Organizations may need to uninstall this software to enforce standardized tooling, reduce software sprawl, or comply with security policies.

The Worklet targets system-wide installations registered in the Windows Uninstall registry hive at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for 64-bit systems and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall for 32-bit applications on 64-bit systems.

Why remove DBeaver from your endpoints

Unauthorized database tools create data security risks and compliance violations. When users install DBeaver without approval, they gain extensive database access capabilities that bypass normal access controls. This situation creates potential vectors for unauthorized database queries, data exfiltration, or unintended data modification that your security team cannot monitor.

Uninstalling unauthorized or unnecessary database tools reduces your security surface area by eliminating potential vectors for unauthorized database access or data exfiltration. This Worklet streamlines the removal process by automatically detecting installed versions and performing silent uninstallation with appropriate permissions.

Using automated removal also saves time compared to manual uninstallation across dozens or hundreds of endpoints. The Worklet handles both 32-bit and 64-bit versions in a single execution, reducing administrative overhead.

How DBeaver removal works

1. Evaluation phase: The Worklet queries the Windows registry to detect whether DBeaver is installed as a system-wide application. On 64-bit systems, it checks both the native 64-bit registry path and the 32-bit application compatibility path (Wow6432Node). If DBeaver is found in either location, the Worklet flags the endpoint for remediation.

2. Remediation phase: If DBeaver is detected, the Worklet executes the uninstall executable located in the program installation directory. For 64-bit installations, it runs C:\Program Files\DBeaver\Uninstall.exe with silent uninstall arguments (/S /allusers). For 32-bit installations on 64-bit systems, it runs C:\Program Files (x86)\DBeaver\uninstall.exe with the same arguments. The Worklet waits for the uninstallation process to complete before reporting success or failure.

DBeaver removal requirements

• Windows 10, Windows 11, or Windows Server 2016 and later

• System-wide DBeaver installation (not user profile-specific installations)

• Administrative privileges required to execute the uninstall process

• DBeaver must be installed via the standard Windows installer (detectable in registry)

Expected state after DBeaver removal

After successful remediation, DBeaver will be completely removed from the endpoint with all application files deleted from Program Files or Program Files (x86) directories. The uninstall process cleans up associated registry entries in the Windows Uninstall registry hive and removes Start menu shortcuts. You can verify removal by checking that DBeaver no longer appears in Programs and Features or by querying the registry paths that the Worklet evaluates. Subsequent evaluations will find no DBeaver entries, confirming complete removal.

Subsequent evaluations will find no DBeaver entries in the registry, confirming that the software is no longer installed on the system. Users will no longer be able to launch DBeaver from the Start menu or any installed shortcut. The Worklet can be run repeatedly without error on endpoints where DBeaver is already uninstalled.

How to validate uninstall dbeaver changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for uninstall dbeaver.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as Start-Process, Out-Null, Write-Output, then rerun evaluation for compliance.