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.

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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

When I start FF from pinned icon in my Win7 Taskbar - new icon of FF appreas, isntaed of highlighting the existing(pinned) one.

  • 2 amsoshi
  • 7 sa na da wannan matsala
  • 2 views
  • Amsa ta ƙarshe daga tasss

more options

When I start a Firefox there are two icons in my taskbar - the one is pinned in taskbar(where I clink on it - firefox starts), the second one is the active icon that indicates that firefox is starts. But this second icon shouldn't be visible - only pinned icon should indicate that firefox is started. This is link for picture which describes the issue: http://dox.bg/files/dw?a=490940c6df

When I start a Firefox there are two icons in my taskbar - the one is pinned in taskbar(where I clink on it - firefox starts), the second one is the active icon that indicates that firefox is starts. But this second icon shouldn't be visible - only pinned icon should indicate that firefox is started. This is link for picture which describes the issue: http://dox.bg/files/dw?a=490940c6df

All Replies (2)

more options

Great news. I update my FF to 6.0.1 and this issue is now fixed. :)

more options

This can't be seriously. Now this issue is fixed and FF works fine on my home laptop - Win7 x86. But the problem occurs on my work laptop - Win7 x64. This happens when update to 6.0.2.

Very buggy .. !