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.

Rohkem teavet

Cannot access In box and sent box

  • 6 vastust
  • 11 on selline probleem
  • 1 view
  • Viimati vastas RogerH

more options

After upgrading to Thunderbird 38.3 I could no longer open the In Box, Outbox or any others but was stuck on the settings and setting up new account page. Had to re-install previous version.

After upgrading to Thunderbird 38.3 I could no longer open the In Box, Outbox or any others but was stuck on the settings and setting up new account page. Had to re-install previous version.

Valitud lahendus

How did you get on Roghil

Loe vastust kontekstis 👍 0

All Replies (6)

more options

Do you use the Calendar addon ?

In another forum question Wayne Mery reported:

Reports indicate this is caused by the Calendar addon, in conjunction with version 38.3.0.

For Windows, 1. install older version from http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/38.2.0/win32/en-US/Thunderbird%20Setup%2038.2.0.exe 2. remove calendar addon, restart thunderbird 3. update thunderbird at help | About 4. reinstall calendar addon

Does that help?

more options

I had already returned to 38.1 version, but I removed "Lightning"which was disabled anyway, so I will now try reinstalling 38.3 and hopefully, will have no more problems.

Thanks

more options

Valitud lahendus

How did you get on Roghil

more options

Hi Matt,

I deleted the calendar add on and just went back to previous version of Thunderbird and haven't bothered to update. Thanks for your help.

Regards

Roger

more options

Well now you have the instructions you can update to the more secure later version. Although hopefully 38.4 will contain the relevant fix to prevent this happening again.

more options

I will just leave as it is for the moment.