hi stella, since this is often a symptom of malicious software active on a system, please run a scan with various other security tools like the free version of malwarebytes, adwcleaner & eset online one-time scanner.

philipp said

hi stella, since this is often a symptom of malicious software active on a system, please run a scan with various other security tools like the free version of malwarebytes, adwcleaner & eset online one-time scanner.

Hi and thank you for your reply! I have both malwarebytes and avast antivirus and neither could find any problem. It's odd because I did a second restart and then everything worked...until the next day, when I had to restart my computer one time to get it to work, same problem nothing happened when I clicked the icon. I've never had any problems with firefox before, it's after the latest firefox update that it stopped working.

If you are not getting any kind of crash dialog, either from Windows or from Firefox (Mozilla Crash Reporter), Windows may be "killing" Firefox early in the startup for some reason. Perhaps...

A Recent Issue for 64-bit Windows Users with 64-bit Firefox

One of the main effects of the Firefox 56.0.1 update was to switch 64-bit Windows users from the traditional 32-bit version of Firefox to the 64-bit version. We've received a number of puzzling reports of Firefox either not starting (probably due to incompatibilities with 64-bit drivers that Firefox expects/requires) or not loading any pages after this migration.

One user discovered that Windows was silently killing Firefox at startup and recording it in the Windows event logs (you can view event logs using the Event Viewer). Based on one of the reports in the log, we were able to trace that to an out-of-date Logitech camera driver, of all things. Four other users reported that uninstalling the Logitech camera resolved their problem as well.

• https://support.mozilla.org/questions/1179822#answer-1019375
• https://support.mozilla.org/questions/1181740#answer-1021470
• https://support.mozilla.org/questions/1181405#answer-1022798
• https://support.mozilla.org/questions/1182572#answer-1023413
• https://support.mozilla.org/questions/1182847#answer-1024290

Do you want some assistance in looking at event logs, or do you have such a camera?

If the investigation doesn't yield any solutions, it is worth trying a return to 32-bit Firefox.

While normally this kind of change is seamless -- the installer detects your existing data and preserves everything -- you might want to make a backup "just in case."

• Back up and restore information in Firefox profiles
• How to opt out of 32-bit Firefox migration to 64-bit

Note: If you decide to try 64-bit Firefox on the same system at some point in the future, see: How to switch from 32-bit to 64-bit Firefox.

jscher2000 said

If you are not getting any kind of crash dialog, either from Windows or from Firefox (Mozilla Crash Reporter), Windows may be "killing" Firefox early in the startup for some reason. Perhaps... A Recent Issue for 64-bit Windows Users with 64-bit Firefox One of the main effects of the Firefox 56.0.1 update was to switch 64-bit Windows users from the traditional 32-bit version of Firefox to the 64-bit version. We've received a number of puzzling reports of Firefox either not starting (probably due to incompatibilities with 64-bit drivers that Firefox expects/requires) or not loading any pages after this migration. One user discovered that Windows was silently killing Firefox at startup and recording it in the Windows event logs (you can view event logs using the Event Viewer). Based on one of the reports in the log, we were able to trace that to an out-of-date Logitech camera driver, of all things. Four other users reported that uninstalling the Logitech camera resolved their problem as well.

• https://support.mozilla.org/questions/1179822#answer-1019375
• https://support.mozilla.org/questions/1181740#answer-1021470
• https://support.mozilla.org/questions/1181405#answer-1022798
• https://support.mozilla.org/questions/1182572#answer-1023413
• https://support.mozilla.org/questions/1182847#answer-1024290

Do you want some assistance in looking at event logs, or do you have such a camera? If the investigation doesn't yield any solutions, it is worth trying a return to 32-bit Firefox. While normally this kind of change is seamless -- the installer detects your existing data and preserves everything -- you might want to make a backup "just in case."

• Back up and restore information in Firefox profiles
• How to opt out of 32-bit Firefox migration to 64-bit

Note: If you decide to try 64-bit Firefox on the same system at some point in the future, see: How to switch from 32-bit to 64-bit Firefox.

Thank you for your help!! :) This worked, I would never have even thought that it could possibly have something to do with Logitech, but uninstalling did resolve the problem.