pgAdmin

For managed pgAdmin 4 updates, treat both the machine-wide EXE package and the per-user/User x64 package as needing conflicting-process handling. Package testing flags pgAdmin 4 installs where an installer popup can block the installation from continuing, so Intune, ConfigMgr, or PSADT deployments should prompt for closure or pre-close running pgAdmin processes before launching the installer.

Use the official pgAdmin Windows download page as the source of installer content, and keep EXE/User package detection separate in your deployment rules so a blocked per-user install is not mistaken for a successful machine-wide update.

For managed pgAdmin 4 Windows updates, close pgAdmin before running the installer. The machine and per-user x64 packages can return Exit Code 1 when pgAdmin is open during update; pre-close it or use a user-deferral step, then rerun detection. Source: official pgAdmin 4 source.