Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

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

Bugs updating from ESR to 136 Release Channel and Owl

  • 3 replies
  • 1 has this problem
  • 23 views
  • Last reply by david

more options

Good morning, As the Release channel is the new default one, I updated my ESR version to the new 136.0. And now there are some things that doesn't work :-( I've my Exchange account configured with Owl addon. It's compatible, and it's enabled, but I see two bugs:

  • Msg filter are not applied automatically, I've to apply them manually. Very annoying!
  • The Exchange account Inbox messages are not displayed in the Inbox unified folder. I've to manually add it every time I restart.

Are these bugs from TB or Owl? How I should proceed?

Good morning, As the Release channel is the new default one, I updated my ESR version to the new 136.0. And now there are some things that doesn't work :-( I've my Exchange account configured with Owl addon. It's compatible, and it's enabled, but I see two bugs: * Msg filter are not applied automatically, I've to apply them manually. Very annoying! * The Exchange account Inbox messages are not displayed in the Inbox unified folder. I've to manually add it every time I restart. Are these bugs from TB or Owl? How I should proceed?

All Replies (3)

more options

My approach would be to revert to the esr. 136 is new and some addons are not updated. The esr is not dead and will continue to be supported and updated.

more options

Is it possible to revert to esr? I can install it over the release? It won't be a problem with the "downgrade" if my profile is already used with 136?

more options

exit thunderbird Install the esr over the top of the 136 In profile, delete the file named compatibility.ini start thunderbird