Overview

What Is the Windows Helper App?

The Windows Helper app is a small Windows desktop application that extends Password Boss beyond the browser. While the browser extension autofills passwords on websites, the Windows Helper autofills credentials in native desktop applications—things like VPN clients, remote desktop tools, and other software that isn't running in a browser tab.

It runs quietly in the system tray, watches for the active application window, and offers to fill saved credentials when it recognizes a supported login screen (for example, Cisco AnyConnect, OpenVPN, FortiClient, ConnectWise, Zoom, Microsoft Teams, or Slack's desktop login).

Prerequisites

• Windows only (not available on macOS or Linux)
• Administrator/elevated rights on the machine to install
• An active Password Boss account, signed in through the web app (app.passwordboss.com)

Installation / Deployment

The desktop app ships in three Windows formats:

• MSI (.msi) — Recommended for enterprise deployment (SCCM, Intune, GPO)
• NSIS (.exe) — Scripted/manual silent installs where MSI tooling isn't available
• Portable (.exe) — Standalone, no install; no silent mode exists for this target, not recommended for managed rollouts

MSI (recommended for enterprise)

Install, silent and machine-wide:

msiexec /i "C:\path\to\PasswordBossDesktopAppSetup-<version>.msi" MSIINSTALLPERUSER="" /qn /norestart /l*v "C:\path\to\install.log"

Uninstall, silent:

msiexec /x "C:\path\to\PasswordBossDesktopAppSetup-<version>.msi" /qn

Notes:

• MSIINSTALLPERUSER="" is required for a true machine-wide install. Without it, the installer silently defaults to a per-user install even when run elevated.
• Always quote both the MSI path and the log path, and use absolute paths for both — a relative log path can drop the log somewhere unexpected.
• /qn shows no UI, /norestart suppresses an automatic reboot, /l*v <log> writes a verbose log — capture this before escalating any failed unattended install.
• If a machine-wide install silently fails, check the log for MSI error 1925 or 1603 — both point to the install running without proper elevation.
• Installing a newer MSI over an existing install upgrades it in place — no duplicate entry in Apps & Features.

PowerShell scripting tip: msiexec doesn't block when launched directly from PowerShell, so $LASTEXITCODE won't reflect the real result. Use Start-Process -Wait -PassThru instead:

$p = Start-Process msiexec -ArgumentList '/i', '"C:\path\to\PasswordBossDesktopAppSetup-<version>.msi"', 'MSIINSTALLPERUSER=""', '/qn', '/norestart', '/l*v', '"C:\path\to\install.log"' -Wait -PassThru
$p.ExitCode   # 0 = success, 3010 = success, reboot required

NSIS (.exe)

Install, silent, default location (from an elevated prompt):

PasswordBossDesktopAppSetup-<version>.exe /S

Install, silent, custom directory:

PasswordBossDesktopAppSetup-<version>.exe /S /D=C:\Program Files\PasswordBossDesktopApp

Uninstall, silent: run the generated uninstaller from the app's install directory with /S — this also requires an elevated prompt.

Portable (.exe)

Not an installer — runs standalone without installing anything on the machine. This target has no silent-install or silent-uninstall mode, so it isn't suited to RMM/managed deployment.

Verify It Worked

• The Password Boss icon appears in the Windows system tray.
• Opening the tray icon shows the app signed in (or prompts you to sign in on first launch).
• On a known-supported app (e.g., Cisco AnyConnect or the ConnectWise desktop client), opening its login screen should trigger an autofill prompt within a couple of seconds.

Common Issues

A specific desktop app isn't being auto-detected, even though it's on the list.

The Windows Helper relies on how an application exposes its login fields to Windows. Some apps use non-standard interfaces the Helper can't automatically recognize. If the app appears in the Helper's app list but doesn't trigger autofill, try selecting it manually from the list instead of waiting for auto-detection.

Autofill works reliably on some apps but not others.

This is expected — compatibility varies based on how the target application is built. Common VPN clients, RDP, and communication apps (Cisco AnyConnect, ConnectWise, Zoom, Teams, Slack) are well-supported. Apps with custom-drawn or unusual interfaces may fill inconsistently or not at all. If autofill fails, you can always copy the credential from the web app and paste it manually as a fallback.

Autofill doesn't work in a window running "Run as Administrator."

Windows security policy prevents standard applications from sending input into elevated (admin) windows. This is a Windows-level restriction, not a bug — the workaround is to copy the password from the web app and paste it manually into the elevated window.

Autofill doesn't reach an app running inside a Remote Desktop (RDP) or remote-support session.

The Windows Helper runs on the local machine and can't reach into a separate remote session. Use copy/paste from the web app instead — if the RDP session has clipboard redirection enabled, copying locally and pasting into the remote session will work.

The Helper's tray icon is missing after installation.

Confirm the install actually completed (check Apps & Features, or the MSI install log if deployed via RMM). If it's installed but the tray icon isn't showing, sign out and back in, or restart the app from the Start menu.

Still Having Issues?

If a client has followed the steps above and the Helper still isn't detecting or filling a specific application, escalate with:

• The exact application name and version
• Windows version
• Whether the app appears in the Helper's manual app-selection list
• Whether the same credential fills correctly through the web app or browser extension