In 64-bit Firefox, extensions are not searched from Wow6432Node registry

RESOLVED INVALID

Status

()

Toolkit
Add-ons Manager
RESOLVED INVALID
2 years ago
2 years ago

People

(Reporter: Huemac, Unassigned)

Tracking

43 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20151108015950

Steps to reproduce:

- Install Firefox 43.0.4 64-bit version in 64-bit Windows 10

- Install a plugin via registry using these instructions: 
https://developer.mozilla.org/en-US/docs/Adding_Extensions_using_the_Windows_Registry

- Install and open up Process Monitor 
https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx


Actual results:

- Firefox makes queries to "HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Firefox\Extensions"
- Plugins are not loaded


Expected results:

- Firefox loads plugins using registry path "HKEY_LOCAL_MACHINE\Wow6432Node\SOFTWARE\Mozilla\Firefox\Extensions" like Firefox 43.0.4 32-bit with 64-bit Windows 10
(Reporter)

Comment 1

2 years ago
Sorry, I meant extensions with the word plugin.

Comment 2

2 years ago
It is correct, 64bit version does not go through WoW64 mechanism, unless it deliberately search for it.
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit
Summary: In 64-bit Firefox, extensions are searched from wrong path in Windows registry → In 64-bit Firefox, extensions are not searched from Wow6432Node registry
The registry key that Firefox reads from varies depending on the architecture of Firefox and Windows and this is controlled by the OS. You will need to add your registry key in both places if you want to support all possible architecture combinations.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 4

2 years ago
"You will need to add your registry key in both places if you want to support all possible architecture combinations."


Sounds like an ugly solution to a simple issue. It can and should be fixed from your side.
(In reply to Huemac from comment #4)
> "You will need to add your registry key in both places if you want to
> support all possible architecture combinations."
> 
> 
> Sounds like an ugly solution to a simple issue. It can and should be fixed
> from your side.

I don't think so. WOW64 means "32-bit apps running on 64-bit Windows". If you want a different version of an extension (maybe of an extension including some binary executable code, like the Lightning calendar for Thunderbird and SeaMonkey does) depending on whether the program invoking it is "actual" 64-bit code, or 32-bit code running on your 64-bit OS, you will need a different key for each, and looking in both places would be a bug, which in some cases might even lead to a crash.

Note that the Firefox 38 (ESR 38 I suppose) browser with which this bug was reported was such a 32-bit app running on a 64-bit OS, as can be seen from the "WOW64" in its User-Agent string near the top of comment #0.
Wow6432Node registry will point 32-bit DLLs that 64-bit Firefox can not load anyway. Moreover, Win64 Firefox 43+ no longer supports plugins except Flash and Silverlight.

Marking INVALID that means "Works as expected, not a Firefox bug".
Resolution: WONTFIX → INVALID
(Reporter)

Comment 7

2 years ago
(In reply to Tony Mechelynck [:tonymec] from comment #5)
> (In reply to Huemac from comment #4)
> Note that the Firefox 38 (ESR 38 I suppose) browser with which this bug was
> reported was such a 32-bit app running on a 64-bit OS, as can be seen from
> the "WOW64" in its User-Agent string near the top of comment #0.

The bug was not for Firefox 38. It was for Firefox 43.0.4. I made the report using older Firefox.

(In reply to Masatoshi Kimura [:emk] from comment #6)
> Wow6432Node registry will point 32-bit DLLs that 64-bit Firefox can not load
> anyway. Moreover, Win64 Firefox 43+ no longer supports plugins except Flash
> and Silverlight.

I said this earlier:

(In reply to Huemac from comment #1)
> Sorry, I meant extensions with the word plugin.


My use case is that I programmatically install an extension and it does not get installed to Firefox 64-bit. 32-bit works fine.

I will go ahead with this:

(In reply to Dave Townsend [:mossop] from comment #3)
> You will need to add your registry key in both places if you want to support all
> possible architecture combinations.
You need to log in before you can comment on or make changes to this bug.