Why does the browser add-on no longer connect after upgrading to version 19?

With version 19, the Password Depot browser extension was redeveloped from the ground up. It communicates with the client exclusively via Native Messaging; the local connection port used by earlier generations is gone. The add-ons for Chrome, Edge, and Firefox are distributed through the browser stores and update there automatically. After the automatic update to the new add-on generation, the add-on can therefore no longer connect to an older client, because each add-on generation only works with the matching major client version. The new extension requires the new client interface, which was introduced with version 19.0.3 and stabilized with 19.0.4 – a client version 19.0.4 or later is therefore required.

To restore the connection:

1. Update the client. Install the current version 19 (at least 19.0.4). Within version 19, use Help → Search for updates; coming from version 18 or older, an upgrade to the new major version is required.

2. Run the setup again and include the add-on components. Install version 19 "over" the existing installation and select the add-on components for your browsers in the setup. The setup re-registers the Native Messaging Host (pdMessagingHost.exe in the installation directory C:\Program Files\AceBIT\Password Depot 19) in the Windows registry.

3. Restart the browser and check the status. Click the add-on symbol in your browser: under About Password Depot Extension you can see the version of the add-on and of the connected client. The Version mismatch status means that add-on and client do not match.

4. Still no connection? Check whether several major versions (e.g. 18 and 19) are installed in parallel – in this case, the registry entries of the Native Messaging Host (de.acebit.passworddepot) may point to the wrong version; run step 2 again. In managed environments, group policies or antivirus software may also block Native Messaging or pdMessagingHost.exe.

Note: If you cannot update the client for the time being (e.g. because you are still using version 18), install the previous add-on generation manually as a temporary measure – it is available for Chrome, Edge, and Firefox on the previous versions page of our website – and then renew the Native Messaging registration via Help → Add-ons in the client. This workaround only applies as long as you are using an older major version; once you switch to version 19, you return to the current add-on from the store.

macOS: The macOS client has its own release cycle and may differ from the server version; add-on and client version must still match, however. As of version 19, you set up the connection once via Help → Add-ons → Save Native Messaging. For details, see the article on the add-on on macOS (see Related topics).

Related topics:

• The new browser extension for Password Depot 19

• How do I prevent the add-on from filling in wrong or unwanted fields?

• What can I do if the add-on does not fill in a login page at all?

• Setting up the browser add-on on macOS (as of version 19)