In fact most of the Chrome Ext install come from restrictions/policies/controls of our organization that manage the OS. (it is rarely show the similar issue with your own PC at home).
I may start with my general setting which might give you and others.
- Make sure that no restriction in the
\Software\Policies\Google\Chrome\NativeMessagingHosts\ExtensionBlacklist. If you found any thing in this session, it means ‘Block’. ‘*’ = block everything.
- In case there is ExtensionBlacklist, then you may allow you extension to be installed. By having the specific extension’s ID added in ‘Software\Policies\Google\Chrome\NativeMessagingHosts\ExtensionInstallWhitelist’.
Step 1) and 2) go together - you won’t need to add the Whitelisting if there is no Blacklisting.
- Once you have installed the Chrome Extension, the extension reference would show up in \Software\Google\Chrome\Extensions… where it shows the ID, version, and .crx file path.
If you don’t have the ‘Extensions’ show up, it doesn’t interfere the functionality that much - you can leave it be.
- 4.2) In the ‘manifest’ file that is referenced, the content has to have :
“name”: <the ‘com.uipath.chromenativemsg’ name from the registry>
“chrome-extension://<Chrome extension ID - version that you installed>”
If those relations are linked properly, the ChromeNativeMessaging should be able to enable and run.
Though I still use Uipath v2018, but the principle of how Chrome works would be similar.
The missing registry can be added manually with admin. Also i use HKEY_Local instead on _Current_User, but the idea of referencing NativeMessage doesn’t change.
Hope it helps