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.

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

FF17 turn on twice?

  • 2 replies
  • 1 has this problem
  • 2 views
  • Last reply by kathlin409

more options

I just upgraded to FF17. My problem is that when I double click the FF icon and nothing happens. I wait and wait but nothing happens. Then I double click again and I get two windows of FF. This did not happen before when I had FF13. What's going on?

I just upgraded to FF17. My problem is that when I double click the FF icon and nothing happens. I wait and wait but nothing happens. Then I double click again and I get two windows of FF. This did not happen before when I had FF13. What's going on?

Chosen solution

Thanks, I checked that but it didn't work. What finally worked was watching my Task manager. Turns out it was the Java that was causing the problem. I disabled it in FF and now I don't have the problem anymore.

Read this answer in context 👍 0

All Replies (2)

more options

Which security software (firewall, anti-virus) do you have?

A possible cause is security software (firewall,anti-virus) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.

Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.

See:

more options

Chosen Solution

Thanks, I checked that but it didn't work. What finally worked was watching my Task manager. Turns out it was the Java that was causing the problem. I disabled it in FF and now I don't have the problem anymore.