38.7.2 Bricked My Installation - Any Suggestions?
38.7.2 installed on my machine this morning.
Upon restart, Thunderbird becomes immediately non responsive and pegs CPU usage at bout 30%.
I let this run for several hours - it did not resolve.
The configuration has not changed for months.
I am able to access my mail server logs, it appears that 3 of my accounts are able to successfully negotiate an SSL/TLS IMAP connection. However after this, no other logs are created by the Thunderbird client.
Mail server logs are normal, and it has been receiving, processing mail all day. I am able to access and interact with my android IMAP client.
Any ideas on how to go about resolving this?
الحل المُختار
Wayne Mery said
A corrupted system file might help cause BSOD, but not a bad application file
Hi Wayne.
I meant that the OS BSOD occurred while TB was writing a file associated with the problem account's profile causing it to be corrupted.
With a clean install on another machine, I was able to download all messages for the problem account without issue. My guess is a file is corrupt in my home installation, and TB is hanging because of this corruption.
Read this answer in context 👍 0All Replies (4)
Ok if it is a brick in is irreparable, bin the device and start again with a new one. I really doubt however that it is bricked. What I am almost certain of is the issue will resolve to two outcomes.
The mail sever is using outdated SSL/TLS technologies. Logging in without SSL/TLS will test that.
There is an issue with firewall/Anti virus products. Anything of that type on Windows 10 is suspect. Windows defender if it is the primary anti virus requires you to exclude the Thunderbird process. Most anti virus product require you to exclude the Thunderbird profile from their aggressive scanning.
Beyond that there is the possibility of an add-on has gone south. Restart Thunderbird in safe mode (hold shift while starting) to disable add-ons and themes to test.
Hello Matt.
Sorry for the delay in response. No firewall or antivirus.
SSL/TLS is working fine for my other TB accounts against the same mail server.
I parsed all of the IMAP messages after logging in against the problem account and everything looks in good working order. After the final fetch command (all responded OK from the server) is completed TB hangs and times out failing to communicate back to the server.
As I said in the original post, I have no issues with accessing this same account with an android client.
I had a blue screen recently, and I am afraid maybe a profile file for this account was corrupted.
If I have a backup of the .msf file and the account directory contained in the "ImapMail" directory, can I just use those? Or do I have to restore the entire profile directory to an older version?
Modified by confuzius
A corrupted system file might help cause BSOD, but not a bad application file
الحل المُختار
Wayne Mery said
A corrupted system file might help cause BSOD, but not a bad application file
Hi Wayne.
I meant that the OS BSOD occurred while TB was writing a file associated with the problem account's profile causing it to be corrupted.
With a clean install on another machine, I was able to download all messages for the problem account without issue. My guess is a file is corrupt in my home installation, and TB is hanging because of this corruption.
Modified by confuzius