Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

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

  • 4 antwoorde
  • 1 het hierdie probleem
  • 2 views
  • Laaste antwoord deur 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.

Gekose 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.

Lees dié antwoord in konteks 👍 0

All Replies (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

Gekose 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!