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

Firefox won't start (not even in Safe Mode) on Windows 7 x64

  • 5 replies
  • 109 have this problem
  • 7 views
  • Last reply by rockledge

more options

I am Running Windows 7 x64 and Firefox 3.6.15.

Since the day before yesterday I am unable to start Firefox. Even in Safe Mode it just won't start.

I click the Firefox icon, the mouse cursor changes to indicate the computer is doing something. After 3 seconds or so the mouse cursor again changes back to its default state. Nothing else happens. The Task Manager in Windows shows me that an instance of firefox.exe is running, but I see no Firefox window. Then if I again click to open Firefox, another firefox.exe instance starts, but again I see no Firefox window.

There isn't even a warning about one instance of Firefox already running.

What I have tried: I have uninstalled Firefox, removed all the Firefox files and folders from c:\users\username\AppData\Local and Roamning. I re-downloaded the 3.6.15 installation package and re-installed.

No change.

I am Running Windows 7 x64 and Firefox 3.6.15. Since the day before yesterday I am unable to start Firefox. Even in Safe Mode it just won't start. I click the Firefox icon, the mouse cursor changes to indicate the computer is doing something. After 3 seconds or so the mouse cursor again changes back to its default state. Nothing else happens. The Task Manager in Windows shows me that an instance of firefox.exe is running, but I see no Firefox window. Then if I again click to open Firefox, another firefox.exe instance starts, but again I see no Firefox window. There isn't even a warning about one instance of Firefox already running. What I have tried: I have uninstalled Firefox, removed all the Firefox files and folders from c:\users\username\AppData\Local and Roamning. I re-downloaded the 3.6.15 installation package and re-installed. No change.

All Replies (5)

more options

I removed opentext nfs solo v14 (hummingbird) it is just worked.

more options

I don't know what opentext nfs solo v14 is, but if that's an extension, I never used it. I re-installed Windows and then re-installed Firefox and then everything was fine. What a weird bug...

more options

I have the same problem. The only Firefox version working is the 64bit nightly build 6.0a1. No 32Bit version of Firefox works!. Chrome, Safari and Internet Explorer all work well. Another Problem I have in this context is, that the Firefox Installer hangs in the tidy up step - even for the nightly 64Bit version. I have to kill the setup.exe process but the Installation seems to be completed.

Before my change to Win7 64Bit I had OpenText NFS Solo 14 installed on a 32Bit Windows7 and no Problems.

Is there a solution for this problem without uninstalling OpenText NFS Solo 14? I need the NFS Server at work.

Modified by bmarx

more options

Today I discovered an OpenTextNFSSolo14x64_SerivePack4 in the service area of OpenText which solved the problem.

See this help topic: Firefox 32Bit won't start after Open Text NFS Solo 14 installation


Firefox 4.01 is now running again.

Modified by bmarx

more options

I found a solution that worked for me. Right click on Foxmail, click on the "Compatability" tab, and click "Disable Visual Themes".

 I did this and it seems to have worked, even though my version of windows doesn't show in the "run in compatability mode" options.
 I hope this helps others, this was a real pain in the ass.