Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

Thunderbird (60.6.1) on Windows 10 (v1809) will not start again after terminating, reporting "Thunderbird is already running, but is not responding."

  • 1 valiny
  • 1 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i sfhowes

Alchemist990
Alchemist990
more options

Recently, after terminating Thunderbird (60.6.1) on Windows 10 (v1809), it will not start again, reporting: "Thunderbird is already running, but is not responding. The old Thunderbird process must be closed to open a new window".

W10 Resource Monitor shows that process components remain in memory, long after thunderbird.exe has terminated.

I also have a similar problem with Firefox (v66.0.3), showing the same failure to eliminate Forefox components from memory after termination, and the same failure to restart.

The only way I have found to fix the problem is to reboot. Ugh!

Recently, after terminating Thunderbird (60.6.1) on Windows 10 (v1809), it will not start again, reporting: "Thunderbird is already running, but is not responding. The old Thunderbird process must be closed to open a new window". W10 Resource Monitor shows that process components remain in memory, long after thunderbird.exe has terminated. I also have a similar problem with Firefox (v66.0.3), showing the same failure to eliminate Forefox components from memory after termination, and the same failure to restart. The only way I have found to fix the problem is to reboot. Ugh!

All Replies (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

Duplicate, answered here: https://support.mozilla.org/en-US/questions/1256342