Failed To Start Native Messaging Host on 64 bit Machines

36 views
Skip to first unread message

Vishal Jaiswal

unread,
Dec 19, 2024, 2:59:59 AM (5 days ago) Dec 19
to Chromium Extensions
Hi Chromium Team,

We are facing one issue related to our extension (Trellix EndPoint Security Web Control).
This extension is running as expected on 32 bit machines, but on 64 bit machines where 64 bit chrome application is present it throws an error that "Unchecked runtime.lastError: Failed to start native messaging host".

Note -: If 32 bit chrome is installed then also the extension runs as expected without any error.

The native messaging host that this extension talks to is 32 bit. And we have set the registry for native messaging host under -: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\siteadvisor.mcafee.chrome.extension

When I checked the documentation, I found that it doesn't matter whether the nativemessaginghosts registry is defined under WOW6432 or in 64 bit as extension first checks wow6432 and if nativehost is not found then it will query 64 bit registry.

We need help to resolve this issue, we are not sure why nativemessaging host is getting failed to start with 64 bit chrome.

hrg...@gmail.com

unread,
Dec 19, 2024, 3:56:59 AM (5 days ago) Dec 19
to Chromium Extensions, Vishal Jaiswal
WOW6432 is for 32-bit programs running in a 64-bit Windows. Therefore a 64-bit Chrome will not even look at the key your are using.
Instead, use this:
HKEY_LOCAL_MACHINE\Software\Google\Chrome\NativeMessagingHosts\...
Reply all
Reply to author
Forward
0 new messages