Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

FF ESR 45.6 @ win10 legacy addons problems; while same FF profile @ win7 works flawlessly

  • 2 odgovora
  • 1 ima ovaj problem
  • 30 prikaza
  • Posljednji odgovor od aka179

aka179
aka179
more options

I have FF ESR 45.6 @ Win7 running flawlessly with two legacy commercial addons installed. I do need these unsigned addons as there are no alternative software.

On the new Win10 PC and exactly same Firefox ESR 45.6 these addons show compatibility errors while installing. I have disabled signed checks and forced nightly.disableCheckCompatibility=true. No luck. Then I have copied complete profile from Win7 FF installation. Now addons do appear in about:addons. Their state is disabled with no "Enable" button.

Any ideas?

(Win7 = Enterprise x64; Win10 = enterprise_2016_ltsb_n_x64_9057894)

I have FF ESR 45.6 @ Win7 running flawlessly with two legacy commercial addons installed. I do need these unsigned addons as there are no alternative software. On the new Win10 PC and exactly same Firefox ESR 45.6 these addons show compatibility errors while installing. I have disabled signed checks and forced nightly.disableCheckCompatibility=true. No luck. Then I have copied complete profile from Win7 FF installation. Now addons do appear in about:addons. Their state is disabled with no "Enable" button. Any ideas? (Win7 = Enterprise x64; Win10 = enterprise_2016_ltsb_n_x64_9057894)

Izabrano rješenje

If you follow the "More" link for each extension to the detail page, do they show the extensions were disabled because they cannot be verified? I believe that wording is specific to the signature issue.

After copying over the profile, did you again toggle the signing requirement? (I don't think nightly preferences are relevant to the ESR release.)

I notice your Firefox identified itself as the 64-bit Windows release (on Windows 10). On Windows 7, are you running the standard 32-bit release? I'm not aware of differences in this area, but it might be relevant.

Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Odabrano rješenje

If you follow the "More" link for each extension to the detail page, do they show the extensions were disabled because they cannot be verified? I believe that wording is specific to the signature issue.

After copying over the profile, did you again toggle the signing requirement? (I don't think nightly preferences are relevant to the ESR release.)

I notice your Firefox identified itself as the 64-bit Windows release (on Windows 10). On Windows 7, are you running the standard 32-bit release? I'm not aware of differences in this area, but it might be relevant.

aka179
aka179 Vlasnik pitanja
more options

Exactly - I have messed with x64 FF on W10. I was used to Firefox being x32 only. Now it works perfectly!