Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Two add-ons update every time I open Firefox; same versions, over and over.

  • 4 antwurd
  • 1 hat dit probleem
  • 5 werjeftes
  • Lêste antwurd fan OrangeBuzzard

more options

NoScript and Download Helper launch updates every time I open Firefox (latest ver). If I close browser, they launch again immediately.

NoScript and Download Helper launch updates every time I open Firefox (latest ver). If I close browser, they launch again immediately.

Keazen oplossing

You can check the home page setting:

  • Tools > Options > General > Startup: Home page

Firefox supports multiple home pages separated by '|' (pipe) symbols.

You can check for problems with preferences.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (4)

more options

Try this, remove both. Restart Firefox. Any problem? Now install one add-on from its Mozilla Add-ons Web Page.

Restart. Any problem? Now do the other add-on.

more options

FredMcD said

Try this, remove both. Restart Firefox. Any problem? Now install one add-on from its Mozilla Add-ons Web Page. Restart. Any problem? Now do the other add-on.

Thanks, Fred. Tried that and tried it again, restarting between attempts. No dice. Firefox still wants to download both every time. I can even apply my license to Download Helper. It runs while Firefox is open, but tries to reinstall DLH next time I open Firefox.

more options

Keazen oplossing

You can check the home page setting:

  • Tools > Options > General > Startup: Home page

Firefox supports multiple home pages separated by '|' (pipe) symbols.

You can check for problems with preferences.

more options

OrangeBuzzard said

NoScript and Download Helper launch updates every time I open Firefox (latest ver). If I close browser, they launch again immediately.

Problem seems to have resolved itself. Related to a new scanning utility, but publisher denied being the cause. Thanks for the help folks!