![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
Thunderbird 78.10.0 suddenly stopped working under Mac OSX 10.13.6
Thunderbird had been working perfectly for years under Mac OSX 10.13.6 (High Sierra) until this morning. Now attempts to start it result in an error message "You can't use this version of the application 'Thunderbird_78_10_0.app' with this version of MacOS. You have MacOS 10.13.6. The application requires MacOS 10.15 or later." The app shows a modified date of July 12, 2024, i.e., this morning and a size of 434.7MB. Perhaps it auto updated itself without checking that the update was compatible with the environment? Any suggestions about how to reverse that update or otherwise fix the problem would be appreciated!!! Garth Fletcher
Gekose oplossing
SUPER! THis is a good time to do a full profile backup. be sure to exit thunderbird prior to doing it.
Lees dié antwoord in konteks 👍 1All Replies (16)
I do not know MACs, but you may be able to verify Thunderbird status by clicking the settings>general and looking for a button for update history. Since you are using ver 78, that might be Preferences>general. The text you posted, though, does not indicate an update happened. You can also click Help>about to verify the version number.
Can't run the possibly auto-updated app, so can't check update history. Installed 78.10.1 from a 2021 .dmg. It runs with its own Profile. About profile shows the current profiles and the previous profile from 2 AM when I shut down. However, selecting the previous profile and clicking Launch profile produces an error message says it can only be used with newer versions of Thunderbird.
So, one question is: how do I update 78.10.1 to newer versions without taking the last one which may have created the problem. Alternatively, what could I copy from the previous profile to recover my emails, address book, etc., without triggering an error message...
Many thanks for the help
Is it possible that you were using an older version than 78.10.0 and thunderbird updated to that version? If so, then you would be wanting the prior version, not a later version. Is there a compatibilities.ini file in the preferred profile that you could rename and try again? Run 78.10.1 and click preferences>general and check update history there, as it may tell. If the prior version is needed (78.9.1), the download link is at https://ftp.mozilla.org/pub/thunderbird/releases/78.9.1/mac/ I also suggest you verify that auto update is OFF, since you are dependent on the current MAC OS.
I'm embarrassed. Turns out the Thunderbird_78_10_0.app name was misleading; left over from an earlier install which was subsequently updated without my changing the name :-(
Get info on the failing app reveals "Thunderbird 128.0esr". I have no idea about the migrations from 78.10.
Following my install of 78.10.1 from a 2021 .dmg, I allowed it to update to 78.14.0, which runs OK. Dragging my Mail folder from the previous Profile into 78.14.0' current Profile, and changing a nested folder name has restored my email - 14 GB worth, phew! Now working on my address books...
The failing Thunderbird app is 434.7 MB, the fresh 78.14.0 is 207 MB. Makes me wonder about file corruption as opposed to a rogue update.
So, I think I'm on the way to recovery. I'll keep you updated.
Many thanks
Well there you go, I was not aware that V128 had been released. That is what happens when you don't read your email for 2 days.
Now I suggest you get the latest version and we help you fix it. What you are doing is not the correct way, and really if you get away with it this time, next time the update will probably make the same mess because the cause has not been fixed.
Many thanks. I am working my way up through the update chain, I'll let you know when I reach the top. After each update, I check to make sure it is running and my email intact, then I go into Preferences to see if there is another update offered. I'm now upd to 91.13.1 (64 bit) and being offered 102.15.1
On DSL at ~ 350 KB/sec, so updates take a while... Hopefully getting fiber tomorrow for 30X speed boost.
And after that, you will be offered 115.12.2. I suggest pausing there, as there are major updates in 115 -- and 128 is just now rolling out.
OK, finally up to date at 115.12.2 email is working, send & receive old emails (14GB) intact Launching the old profile works! Address books restored!
No idea what went wrong, but seem to have fully recovered.
Many many thanks for your support and encouragement! Garth Fletcher
Gekose oplossing
SUPER! THis is a good time to do a full profile backup. be sure to exit thunderbird prior to doing it.
Note that Thunderbird 115 and Firefox 115 are the last to support the old EOL macOS 10.12, 10.13, 10.14 as Tb 116.0 and Fx 116.0 and later including the 128.0 Releases requires macOS 10.15 (ten.fifteen) at minimum to run.
https://support.mozilla.org/en-US/kb/firefox-users-macos-1012-1013-1014-moving-to-extended-support
https://www.thunderbird.net/thunderbird/128.0esr/system-requirements/ https://www.mozilla.org/firefox/128.0/system-requirements/
Thanks for the info. I think what must have happened is an auto-update last night updated me from 115 to 128. This morning during boot up the update would have installed, hence the error messages. Would be good if auto-updates always verified their compatibility with the host OS before installing.
Thanks to all for wonderful support!
Garth
Exactly the same problem as reported by Garth. After 25 years using Eudora/Thunderbird on a Mac I have been forced to join the forum. Using High Sierra 10.13 TB wnet from fully functional to the message as reported by Garth. Can only assume that my system has been automatically updated to obsolescent. As Garth wonderted - why didnt the TB upgrade process check first? Anyway back to the main issue - TB is completely blocked from launching with a no go symbol across the icon in the dock. Cant be launched to learn anything except for the little message box as noted by Garth.
It was commented that Garths recovery routine was non-standard. I agree having done many such routines.
Can Matt the Moderator point us stranded Mac 10.13 users to the preferred recovery process that he hinted at? Much appreciated.
This is my suggested/intended approach until informed otherwise.
Roll back TB to the previous version - since Im locked out of the app and I dont know what version was running Im going back to TB 102 - but perhaps it should be 115? Looking around in the TB package content I can see that it thinks it is version 128 and that the updater says it doesnt work on 10.13 and requires 10.15. Since automatic updates were allowed ( I trusted Mozilla with my connection to life the universe and everything!) this update may need to learn to check before getting into this logical cul de sac.
Rollback procedure: Backup TB folder plus Time Machine backup as well Remove compatibility.ini file from Library to a safe place Place TB 128 into the trash but dont empty Run .dmg installer for the selected old version of TB It should open with all emails, contacts etc in place?
What do you think? Thanks ina dvance.
It would appear that only Garth and I are in this situation across all of Planet Earth.....
ciao Ecolarge
To my knowledge, 128 is still not an auto update, so if that version installed, my assumption is that your computer is using another updater. Ver 115 has been out for a year, and should be a safe install. On your last comment, we have seen several here who had been using non-thunderbird updaters and all of them had similar problems.
The current Thunderbird Releases are Tb 115.13.0 and Tb 128.0
Tb 115 should not give updates to Tb 128 until Tb 115 is made EOL. Even then it should only do updates on a supported OS as macOS 10.13 users should ideally not be getting internal Thunderbird update prompts to Tb 128.0
Thunderbird 115.13.0.dmg (en-US) for macOS is at https://archive.mozilla.org/pub/thunderbird/releases/115.13.0/mac/en-US/ other language locales https://archive.mozilla.org/pub/thunderbird/releases/115.13.0/mac/
Gewysig op
There was an error in the update rules that offered these versions of Mac to update to 128. THis has been resolved. Sorry for the confusion.