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

Thunderbird "Not Responding" when online, works only offline (SOLVED) after a Windows 10 update.

  • 3 replies
  • 1 has this problem
  • 17 views
  • Last reply by remoz

more options

Thunderbird stopped responding from the very second of starting it if it is starting online. When started offline (by shift-clicking the icon, Choose user profile, and selecting the start offline option) it works normally, until I go online.

The second it starts online (or goes online from offline state), it stops responding, I get a "Not Responding" in the title, the CPU usage goes up, and the only way to stop it is to kill the process.

I am running the latest Thunderbird (52.8.0; it identifies as 32 bit, this is the only installer I found) on windows 10, 64 bits. I already did the obvious things -- started a new profile, uninstalled Thunderbird and re-installed it, uninstalled it and installed the previous version, tried to run Thunderbird in "compatibility mode" -- nothing helps.

Thunderbird stopped responding from the very second of starting it if it is starting online. When started offline (by shift-clicking the icon, Choose user profile, and selecting the start offline option) it works normally, until I go online. The second it starts online (or goes online from offline state), it stops responding, I get a "Not Responding" in the title, the CPU usage goes up, and the only way to stop it is to kill the process. I am running the latest Thunderbird (52.8.0; it identifies as 32 bit, this is the only installer I found) on windows 10, 64 bits. I already did the obvious things -- started a new profile, uninstalled Thunderbird and re-installed it, uninstalled it and installed the previous version, tried to run Thunderbird in "compatibility mode" -- nothing helps.

Modified by Wayne Mery

All Replies (3)

more options

The problem was solved after a windows update.

remoz said

Thunderbird stopped responding from the very second of starting it if it is starting online. When started offline (by shift-clicking the icon, Choose user profile, and selecting the start offline option) it works normally, until I go online. The second it starts online (or goes online from offline state), it stops responding, I get a "Not Responding" in the title, the CPU usage goes up, and the only way to stop it is to kill the process. I am running the latest Thunderbird (52.8.0; it identifies as 32 bit, this is the only installer I found) on windows 10, 64 bits. I already did the obvious things -- started a new profile, uninstalled Thunderbird and re-installed it, uninstalled it and installed the previous version, tried to run Thunderbird in "compatibility mode" -- nothing helps.
more options

Wow, that is really interesting.

If the problem returns or if you develop a theory of what specifically changed to improve performance please update the topic.

more options

Several hours before this happened, I uninstalled a pre-installed trial copy of Microsoft Office. Perhaps the removal caused some problem, and then Windows Update fixed it. I am not knowledgeable enough to tell whether Thunderbird relies on windows components that other networked applications don't, and whether such components may have to do with MS Office, or with something that the MS Office uninstallation process can damage. It probably did have to do with some OS component, perhaps a driver, because it seems that Windows Update was what fixed the problem.


Wayne Mery said

Wow, that is really interesting. If the problem returns or if you develop a theory of what specifically changed to improve performance please update the topic.