html in an elevated CMD or PowerShell session and reviewing the output. I was able to publish the same path to HKLM, which got browser integration working, but this is definitely a hack:Ĭreating a second configuration file at C:\ProgramData\keepassxc\_browser_edge.json for KeepassXC during its installation with a matching registry entry in HKLM seems like a much cleaner solution, perhaps selecting specifically for installations by users with administrative You can verify that this policy is applying on your PC by asking your IT department or (if you have local admin rights) running gpresult /h. User-level native messaging hosts are blocked in the baseline policy, which prevents Edge from searching HKCU for the manifest: Microsoft publishes security baselines for several of their products in the form of group policy objects (which we're applying at my company), and one of the policies therein is causing this problem.
0 Comments
Leave a Reply. |