64 bit Chrome not loading extensions configured to load from registry

[VR]

As per the documentation at https://developer.chrome.com/extensions/external_extensions , on 64 bit machines, extensions can be fetched from chrome store by creating a registry entry under HKEY_LOCAL_MACHINE\Software\Wow6432Node\Google\Chrome\Extensions

This works fine on 32 bit Chrome browser but the new 64 bit chrome browser is not respecting this registry area.

I guess the 64 bit Chrome is looking in the 64 bit registry area but I think at some point existing 32 bit browsers will be forcibly upgraded to 64 bit version and so for backward compatibility reasons, Chrome should look for extensions in both 32 and 64 bit area otherwise EXISTING extensions registered for 32 bit browser will not be loaded by 64 bit browser after upgrade.

Browser: Chrome 64 bit (beta)

Platform: Win 8.1

[PhistucK]

The beta and the stable versions (32 or 64 bit) are not loading extensions via the registry anymore (since Chrome 35, I think). Only using enterprise policy, if you are in a domain.

For more information, see the blog post -

http://chrome.blogspot.co.il/2014/05/protecting-chrome-users-from-malicious.html

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/b0edd7bb-11d6-4802-928b-4f9ae1c07844%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[VR]

That is true for loading extensions as local .crx files but Chrome will still load extensions from the store if "update_url" value is specified in the registry.

See the "Using the Windows registry" section in https://developer.chrome.com/extensions/external_extensions

This works fine in 32 and 64 bit chrome but 64 bit chrome doesn't respect the 32 bit registry area. When 32 bit browsers is upgraded to 64 bit version then any extension in 32 bit area will not be loaded because 64 bit Chrome is not looking in the 64 bit area.

So I think to be backward compatible 64 bit chrome should look for side loaded extensions in both 32 and 64 bit area.

V

 

On Monday, August 25, 2014 9:59:41 PM UTC+1, PhistucK wrote:

The beta and the stable versions (32 or 64 bit) are not loading extensions via the registry anymore (since Chrome 35, I think). Only using enterprise policy, if you are in a domain.

For more information, see the blog post -

http://chrome.blogspot.co.il/2014/05/protecting-chrome-users-from-malicious.html

☆PhistucK

On Sat, Aug 16, 2014 at 8:29 PM, VR <vijay....@gmail.com> wrote:

As per the documentation at https://developer.chrome.com/extensions/external_extensions , on 64 bit machines, extensions can be fetched from chrome store by creating a registry entry under HKEY_LOCAL_MACHINE\Software\Wow6432Node\Google\Chrome\Extensions

This works fine on 32 bit Chrome browser but the new 64 bit chrome browser is not respecting this registry area.

I guess the 64 bit Chrome is looking in the 64 bit registry area but I think at some point existing 32 bit browsers will be forcibly upgraded to 64 bit version and so for backward compatibility reasons, Chrome should look for extensions in both 32 and 64 bit area otherwise EXISTING extensions registered for 32 bit browser will not be loaded by 64 bit browser after upgrade.

Browser: Chrome 64 bit (beta)

Platform: Win 8.1

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

[Finnur Thorarinsson]

You should file a bug.

http://new.crbug.com

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.

To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/01d5b973-796e-4d54-a421-00c54a7c41ef%40chromium.org.

[Nandu]

if you don't want to wait for the fix, I'd recommend you to make registrations in both 32-bit and 64-bit hives.

[VR]

I have filed a bug - https://code.google.com/p/chromium/issues/detail?id=408018

[Oliver Cante]

Hi

I have exactly the same problem than yours on my Windows 8.1 64 bits. 

I have published an extension in the chrome store. 

On a windows 7 32 bits, i have added the registry entires and it works. Chrome asked me to enable the extension.

On a Windows 8 64 bits, Chrome does not ask to enable the extension.

Did you find a solution ?

Thanks for your help.

Regards,

Olivier