You've loaded an older version of Firefox from Thunderbird email link
I get the message "You've loaded an older version of Firefox" when I click on any email link in Thunderbird 102.5.0 A blank Firefox appears to open with the above message, wanting me to set up a new profile or exit.
However this only happens when the default Firefox is not already open. When Firefox default profile is open, then Thunderbird opens a new tab from the link.
I have 3 Firefox profiles, just on set as default and all 3 profiles have the latest Firefox 107.0 (64-bit)
الحل المُختار
OK Thanks, I found the problem, due to your comment.
After an update install of Firefox, the original version was still hanging around and had not been uninstalled.
This led to the fact that some files were linking correctly to the latest version and some to the previous version.
The profiles had gone to the newer version so were no longer linked to the previous version, which led to the message above.
Read this answer in context 👍 0All Replies (3)
I am transferring this to the Firefox forum as the issue will be about the Firefox install and what is set as a default in Windows and not something about Thunderbird. Thunderbird only passes the link to windows to open it.
I had to mark it as not resolving the problem, but it also may be pointing to the solution.
The default for windows works from every other package except Thunderbird. If I click on a link in anything else, be that a pdf view or a link in a document, then my default Firfox is loaded.
However when I click on a link to a map, then the same thing happens as Thunderbird, so no it is not specific to Thunderbird per se.
It does however beg the question that maybe there are two lots of firefox for default linked to different things.
I will ofc investigate this.
Modified by mjward
الحل المُختار
OK Thanks, I found the problem, due to your comment.
After an update install of Firefox, the original version was still hanging around and had not been uninstalled.
This led to the fact that some files were linking correctly to the latest version and some to the previous version.
The profiles had gone to the newer version so were no longer linked to the previous version, which led to the message above.