We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

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

  • 1 resposta
  • 1 tem este problema
  • 3 visualizações
  • Última resposta por 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!
Capturas de ecrã anexadas

Todas as respostas (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

Try removing the profile lock file:

http://kb.mozillazine.org/Profile_in_use#Remove_the_profile_lock_file

Works for TB and Firefox.