Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

Anyone having trouble with Norton Toolbar Vault button not working after a while with FF 28?

  • 1 cavab
  • 17 have this problem
  • 3 views
  • Last reply by Vadershine

Vadershine
Vadershine
more options

NIS Norton Toolbar Vault button becomes unresponsive after 3/4 logins. The 3 dot settings button also becomes inop/unresponsive. Works fine for a bit after first starting up FF, but come back in a bit and it quits responding. Click on it, nothing. We've uninstalled/resinstalled NIS. Ran Nortons Auto-Fix. Uninstalled/resinstalled FF. One by one disabled add-ons. FF up to date, NIS up to date. Not getting anywhere with Norton support, they haven't been able to resolve it. Issue remains.

TIA

NIS Norton Toolbar Vault button becomes unresponsive after 3/4 logins. The 3 dot settings button also becomes inop/unresponsive. Works fine for a bit after first starting up FF, but come back in a bit and it quits responding. Click on it, nothing. We've uninstalled/resinstalled NIS. Ran Nortons Auto-Fix. Uninstalled/resinstalled FF. One by one disabled add-ons. FF up to date, NIS up to date. Not getting anywhere with Norton support, they haven't been able to resolve it. Issue remains. TIA

All Replies (1)

Vadershine
Vadershine Question owner
more options

This issue is actually occuring on a Win 7 Home Premium machine, not WinXP. Thanks!