KeePassXC Extension Not Connecting to the KeePassXC Database (Edge & Windows)

[TESTER-sec]

Cannot connect KeePassXC extension to KeePassXC databse:

Have you searched for an existing issue?

• [x] Yes, I tried searching and reviewed the pinned issues

Brief Summary

This reportable issue is reproducible on multiple Windows 11 systems using the latest Edge browser.

Edition Windows 11 Pro Version 24H2 Installed on ‎8/‎25/‎2025 OS build 26100.5074 Experience Windows Feature Experience Pack 1000.26100.234.0

Edge Browser Version 139.0.3405.125 (Official build) (64-bit)

1. Tried uninstalling and reinstalling KeePassXC (provisioned from the Microsoft Store); and
2. Uninstalling and reinstalling the KeePassXC extension for Microsoft Edge; and
3. Deleting all configuration files, AppData, ProgramData, etc.

This provides no fix.

Expected Versus Actual Behavior

Expected: The KeePassXC browser extension will connect to the KeePassXC database.

Actual: The KeePassXC browser extension does not connect to the KeePassLC database.

Steps to Reproduce

1. Update Windows 11 and Microsoft Edge to: Edition Windows 11 Pro Version 24H2 Installed on ‎8/‎25/‎2025 OS build 26100.5074 Experience Windows Feature Experience Pack 1000.26100.234.0

Edge Browser Version 139.0.3405.125 (Official build) (64-bit)

2. Install the latest available version of KeePassXC via the Microsoft Store: 2.7.10

3. Install the latest KeePassXC from the Microsoft Edge extension website.

4. Configure browser integration and attempt to log into a website with I&A credentials stored within the KeePassXC database.

5. Navigate to website and attempt to login using KeePassXC:

KeePassXC-Browser Debug Information

KeePassXC - unknown (2.7.10)
KeePassXC-Browser - 1.9.9.4
Operating system: Win64
Browser: Microsoft Edge 139.0.0.0

[varjolintu]

Which part of the Troubleshooting Guide fails for you? Have you also enabled the Browser Integration and Edge in KeePassXC side?

[TESTER-sec]

Which part of the Troubleshooting Guide fails for you? Have you also enabled the Browser Integration and Edge in KeePassXC side?

The entire Guide. Followed everything in there possible.

Reporting a valid bug that can be reproduced every single time at-will.

[varjolintu]

The entire guide? So there are no registry entries, no JSON files..? Did you do this? https://keepassxc.org/docs/KeePassXC_GettingStarted#_browser_integration

[TESTER-sec]

The entire guide? So there are no registry entries, no JSON files..? Did you do this? https://keepassxc.org/docs/KeePassXC_GettingStarted#_browser_integration

[varjolintu]

And that JSON file points to a correct keepassxc-proxy.exe, and you can launch it manually (just for testing)?

And you have checked this also? https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide#7-windows-specific-with-chromium-based-browsers-chrome-edge-vivaldi-brave-etc

[TESTER-sec]

This reported issue began after the Windows 11 OS update released by Microsoft today.

This reported issue began after Microsoft's latest update to Edge browser.

Cannot role systems back/downgrade to prior versions. Against security policies.

[varjolintu]

This definitely sounds like a Windows/Edge issue then, or the problem is in your system. We haven't changed anything between. If the methods in the Troubleshooting Guide doesn't help, there's nothing we can do.

EDIT: I tested this with my own Windows 11 installation and no issues.

[droidmonkey]

Are you running a develop snapshot of the extension? Show the screenshot of the extension manager

[varjolintu]

Still an issue?

[gisturbance]

Still an issue?

At least for me, the same issue occurs on Firefox Nightly and portable Ungoogled Chromium using a portable KeePassXC using the latest Windows 11, and that since way before August 30th. The proxy is running, all registry entries are properly set, all config files are pointing to the correct locations.

Key exchange was not successful.

[kuriosity121]

Yes, this is still a issue. I have a freshly installed Windows 10 Education 25H2 with a October 2025 Patchlevel and Microsoft Edge Version 142.0.3595.65 (Official build) (64-bit). I used a fresh Edge Profile for testing. Just install the extension from the link of the official KeepassXC website. Click on "Connect" for connecting the database. And nothing happens. I also followed the full troubleshooting guide. Nothing helped. JSON is in place and points to the correct keeepass-proxy.exe.

The error is: "Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings."

How can I help you debugging this issue?

[varjolintu]

Yes, this is still a issue. I have a freshly installed Windows 10 Education 25H2 with a October 2025 Patchlevel and Microsoft Edge Version 142.0.3595.65 (Official build) (64-bit). I used a fresh Edge Profile for testing. Just install the extension from the link of the official KeepassXC website. Click on "Connect" for connecting the database. And nothing happens. I also followed the full troubleshooting guide. Nothing helped. JSON is in place and points to the correct keeepass-proxy.exe.

The error is: "Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings."

How can I help you debugging this issue?

You are new to this thread. Did you check: https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide#7-windows-specific-with-chromium-based-browsers-chrome-edge-vivaldi-brave-etc ?

[gisturbance]

Yes, this is still a issue. I have a freshly installed Windows 10 Education 25H2 with a October 2025 Patchlevel and Microsoft Edge Version 142.0.3595.65 (Official build) (64-bit). I used a fresh Edge Profile for testing. Just install the extension from the link of the official KeepassXC website. Click on "Connect" for connecting the database. And nothing happens. I also followed the full troubleshooting guide. Nothing helped. JSON is in place and points to the correct keeepass-proxy.exe. The error is: "Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings." How can I help you debugging this issue?

You are new to this thread. Did you check: https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide#7-windows-specific-with-chromium-based-browsers-chrome-edge-vivaldi-brave-etc ?

As their message states "I also followed the full troubleshooting guide". It's time to break out of the neverending loop of going through the troubleshooting guide without any progress. Maybe there is some kind of secret conspiracy trying to keep this issue unresolved.

[varjolintu]

Yes, this is still a issue. I have a freshly installed Windows 10 Education 25H2 with a October 2025 Patchlevel and Microsoft Edge Version 142.0.3595.65 (Official build) (64-bit). I used a fresh Edge Profile for testing. Just install the extension from the link of the official KeepassXC website. Click on "Connect" for connecting the database. And nothing happens. I also followed the full troubleshooting guide. Nothing helped. JSON is in place and points to the correct keeepass-proxy.exe. The error is: "Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings." How can I help you debugging this issue?

You are new to this thread. Did you check: https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide#7-windows-specific-with-chromium-based-browsers-chrome-edge-vivaldi-brave-etc ?

As their message states "I also followed the full troubleshooting guide". It's time to break out of the neverending loop of going through the troubleshooting guide without any progress. Maybe there is some kind of secret conspiracy trying to keep this issue unresolved.

Yes.. But the person didn't say anything about the policies concerning Edge. I ask the same questions every time if the person doesn't give the information right away.

If there's a conspiracy somewhere, it's surely related how Edge works and integrates with Windows :) Just kidding of course, but most of the reports are exactly with this combination. And every system is a bit different. This is why the information provided using the Troubleshooting Guide is important for me. If I cannot reproduce exactly the same issue on my unique system, it's difficult to find the actual solution.

[kuriosity121]

Thank you very much for pointing that out! And my apologies for apparently overlooking that point. Perhaps a screenshot showing the relevant group policies would also be useful. You can use this one, if you like:

Previously, the message queue was indeed disabled. (The block list is only important if you really want to enhance the security by controlling these extensions.)

[gisturbance]

I've just noticed that opening KeepassXC sometimes changes the value of the registry entry Computer\HKEY_CURRENT_USER\Software\Mozilla\NativeMessagingHosts\org.keepassxc.keepassxc_browser from .../org.keepassxc.keepassxc_browser_firefox.json to .../org.keepassxc.keepassxc_browser_tor-browser.json. Manually adjusting the value and then restarting Firefox doesn't help. Tor Browser is not on the system.

Windows 11 24H2 (26100.7019) Firefox Nightly 147.0a1 (2025-11-10) KeepassXC portable 2.7.10

Works flawlessly on Chromium portable 142.0.7444.134

[varjolintu]

I've just noticed that opening KeepassXC sometimes changes the value of the registry entry Computer\HKEY_CURRENT_USER\Software\Mozilla\NativeMessagingHosts\org.keepassxc.keepassxc_browser from .../org.keepassxc.keepassxc_browser_firefox.json to .../org.keepassxc.keepassxc_browser_tor-browser.json. Manually adjusting the value and then restarting Firefox doesn't help. Tor Browser is not on the system.

Windows 11 24H2 (26100.7019) Firefox Nightly 147.0a1 (2025-11-10) KeepassXC portable 2.7.10

Works flawlessly on Chromium portable 142.0.7444.134

There might be a bug somewhere if the browser name is set incorrectly for the file. But actually here the filename doesn't matter. The content does, and it should point to the correct executable.

[gisturbance]

There might be a bug somewhere if the browser name is set incorrectly for the file. But actually here the filename doesn't matter. The content does, and it should point to the correct executable.

Sadly everything is pointed correctly, still resulting in an unsuccessful keyexchange, as initially stated.

[gurkey6-design]

I got the same problem on 2 different systems (mine and my wife's) using OS Windows 11 Pro 25H2 and Windows 11 Home 25H2. Both systems are using the most current version of their OS. No entry can be found in the corresponding Edge entries within the registries. No native messaging going on.

[KIMWW]

Same problem for me too on Linux. Enable Browser Integration is ticked for Brave browser in the KeePassXC application settings, but the KeePassXC browser extension cannot connect to KeePassXC. It carry on saying “Check that browser integration is enabled in KeePassXC settings.” I tried from Flathub and AppImage packages but same negative results.

[varjolintu]

Same problem for me too on Linux. Enable Browser Integration is ticked for Brave browser in the KeePassXC application settings, but the KeePassXC browser extension cannot connect to KeePassXC. It carry on saying “Check that browser integration is enabled in KeePassXC settings.” I tried from Flathub and AppImage packages but same negative results.

There are multiple issues about Brave, and how they might use Chrome's configuration paths. Try enabling support that too. If it doesn't help, try to find the actual configuration path and use Custom Browser feature in KeePassXC for it to provide the correct path for nativemessaginghosts.

[l-raider]

I can confirm this issue on Linux (Nixos 25.11 Stable) with Brave as well: Brave 1.84.135 (Official Build) (64-bit) (Chromium: 142.0.7444.135) KeepassXC browser extension version 1.9.10 KeepassXC version 2.7.10

(Worked fine earlier, my guess is a Brave update broke it.)

[varjolintu]

(Worked fine earlier, my guess is a Brave update broke it.)

It wouldn't be the first time.

[l-raider]

I found a fix, the path to "keepassxc-proxy" had changed on my system, updating it to the correct path in ~/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json solved it for me with Brave.

This is likely a Nixos only solution, since the path changed from "/nix/store/jbjwd08qch0x5rgd0n9awkf7id6dpi31-keepassxc-2.7.10/bin/keepassxc-proxy" to "/nix/store/vapzwpw5nspik2za4abi31wqa5lx5q2g-keepassxc-2.7.10/bin/keepassxc-proxy".

home-manager workaround for this:

  home.file."/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json".text =
    builtins.toJSON {
      allowed_origins = [
        "chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/"
        "chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
      ];
      description = "KeePassXC integration with native messaging support";
      name = "org.keepassxc.keepassxc_browser";
      path = "${lib.getBin pkgs.keepassxc}/bin/keepassxc-proxy";
      type = "stdio";
    };

[stan-threatmate]

I had a similar issue on Mac OS. Turned out the installed KeePassXC app had the binary but something was up with its signature:

/Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy
Killed: 9                  /Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy

Reinstalling the keepassxc app with homebrew fixed it.

[varjolintu]

I had a similar issue on Mac OS. Turned out the installed KeePassXC app had the binary but something was up with its signature:

/Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy
Killed: 9                  /Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy

Reinstalling the keepassxc app with homebrew fixed it.

This is not related to the issue at all.

[stan-threatmate]

@varjolintu not sure what you mean but I had the same symptoms of "Key exchange was not successful" no matter what I tried to do. Finally it came down to the executable from the keypass app being "corrupted".

[varjolintu]

@varjolintu not sure what you mean but I had the same symptoms of "Key exchange was not successful" no matter what I tried to do. Finally it came down to the executable from the keypass app being "corrupted".

Yes, but this thread is with a specific issue concerning Windows and Edge.

[GeorgiKarapetrov]

Same issue:

I tried:

1. removing the connected database from the extension.
2. disconnecting all browsers from the database
3. refreshing the root group id of the database
4. disabling and reenabling the browser integration of the KeepassXC app

System info:

KeePassXC - 2.7.11
KeePassXC-Browser - 1.9.11
Operating system: MacIntel
Browser: Chrome/Chromium 142.0.0.0 (Brave Browser)

Content of ~/Library/Application\ Support/BraveSoftware/Brave-Browser/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json

{
    "allowed_origins": [
        "chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/",
        "chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
    ],
    "description": "KeePassXC integration with native messaging support",
    "name": "org.keepassxc.keepassxc_browser",
    "path": "/Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy",
    "type": "stdio"
}

otool -L /Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy yealds

/Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy:
	@loader_path/../Frameworks/libQt5Network.5.15.18.dylib (compatibility version 5.15.0, current version 5.15.18)
	@loader_path/../Frameworks/libbotan-3.7.7.1.dylib (compatibility version 3007.7.0, current version 3007.7.1)
	@loader_path/../Frameworks/libQt5Core.5.15.18.dylib (compatibility version 5.15.0, current version 5.15.18)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 2000.63.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1356.0.0)

When I click Connect, in the extension settings, the browser console message is:

[Error keepass.js:313] KeePassXC-Browser - 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings.

sudo opensnoop -n "Brave Browser" gives me some nonsense:

dtrace: system integrity protection is on, some features will not be available

dtrace: invalid probe specifier 
 /*
  * Etc, etc, REDACTED
  */
: probe description syscall::open:entry does not match any probes. System Integrity Protection is on

To be honest I hate this MacOS but I don't have any say in the matter. It seems to (brake something/change configs) with every update though I can't definitely know that a system update broke the browser integration. Please, let me know if I need to give permissions somewhere? Should I open a new bug with this info?

[varjolintu]

People PLEASE! This thread is about Edge in Windows. I'll add that to the title. Every other browser and OS is OUT OF SCOPE of this thread. Please add new messages to issue threads that are actually related. This is the last time I say this. After this I'll just start deleting the messages because those are just noise.

Thank you.