I can't say why the update happened, but you should be able to still use ExQuilla in TB 60:

https://addons.thunderbird.net/en-US/thunderbird/addon/exquilla-exchange-web-services/

It auto updated to Version 64.0b1 Thunderbird automatically disabled the extension since it said it was incompatible.

Thanks,

TB 64 is the beta version that breaks almost all add-ons. Install TB 60.3, the release version, from this page:

https://www.thunderbird.net/en-US/thunderbird/all/

Thank you, but it installed itself, and that is alot of re-setup. Thanks That is the purpose of this thread, a update installed itself, and at that, a beta version. What is going on here?

This kind of problem often happens when the user has a 3rd-party program, e.g. Avast, that updates your other programs, irrespective of the setting in a particular program. Until the source of the problem is found, you can install the release TB over the beta version and it should read your existing profile (stored in a separate location), without any re-setup.

In the Thunderbird's program directory find defaults\pref\channel-prefs.js. What do you see to the right of app.update.channel ?

sigh - you try to help, and get silence

Thank you for your help. BUT nobody has been able to explain why that a Beta got automatically installed in the first place. I do appreciate the help, but nobody was able to explain that. With that said, I cannot use a mail client that I have paid for a extension (that the developer will probably no longer support), that gets hosed because a beta get's auto downloaded and installed.

I did not have any 3rd party anti virus programs installed, and I already have it removed from my computer, so I am not able to provide what was in that preferences file. I did not agree to or change any default settings to get any beta releases, it was a default install.

There are several users at ms308680 said

With that said, I cannot use a mail client that I have paid for a extension (that the developer will probably no longer support), that gets hosed because a beta get's auto downloaded and installed.

As a quality tester of Thunderbird I update Thunderbird probably hundreds of times per year. I have never seen what you describe, nor am I aware that it has happened to anyone else. I also know that Thunderbird can't update from release to beta unless either a) the channel is changed at the client (user end) or b) the update server is misconfigured. As release manager who helps determine the update server configuration, "b" has never happen to my knowledge. The likely scenario which perfectly matches the description and timing of your posting, is that you have been on beta for a very long time where Exquilla would have worked perfectly fine, and you would have been running version 60 BETA for several months where Exquilla does work (I just tested it). And then you would have gotten updated to version 64 beta in early November because that is when we enabled updates from 60 beta.

It is clear from the author's website that a) the previous license to use (it was never a permanent license) was dirt cheap, b) per https://github.com/rkent/exquilla/wiki/Free it is now free, c) that it works in version 60 per https://addons.thunderbird.net/en-US/thunderbird/addon/exquilla-exchange-web-services/reviews/ d) that the author clearly states he suspects it would not work past version 60.

Based user reports, Exquilla should work if you choose to install version 60, and it will not update to anything higher until at least July 2019 when version 68 is expected per the release chart https://wiki.mozilla.org/Release_Management/Calendar

I know the author personally so I can tell you with authority that he has retired from his programming life. And well deserved.