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

Lost all address books after upgrade from 68.10 to 78.01

  • 6 majibu
  • 1 ana tatizo hili
  • 2 views
  • Last reply by Stans

more options

Hello to all, I upgraded Thunderbird on my Windows 10 laptop from 68.10 to 78.01 and can't see any address books. Is this upgrade suppose to keep and display your address books? I tried to follow all recommendations that I could find and nothing helped. I even tried to export my address books from my second Windows 10 pc and import to PC 1, and I still couldn't see anything. Finally I had to uninstall (and delete all directories) all versions from laptop 1 and copy everything from laptop 2. Now I'm back on version 68.10 and everything seems to be OK. Is there a bug in conversion to 78.01? Thanks, Yuri

Hello to all, I upgraded Thunderbird on my Windows 10 laptop from 68.10 to 78.01 and can't see any address books. Is this upgrade suppose to keep and display your address books? I tried to follow all recommendations that I could find and nothing helped. I even tried to export my address books from my second Windows 10 pc and import to PC 1, and I still couldn't see anything. Finally I had to uninstall (and delete all directories) all versions from laptop 1 and copy everything from laptop 2. Now I'm back on version 68.10 and everything seems to be OK. Is there a bug in conversion to 78.01? Thanks, Yuri

Chosen solution

Now I understand why address book was not migrated. Unfortunately ti should have been made clear when automatic migration happened. Now I'll wait until this "bug" will be fixed.

Read this answer in context 👍 0

All Replies (6)

more options
more options

Also, Version 78.1.0 is available - Help > About

more options

Was this issue fixed in 78.1.0? Was it even recognized as an issue?

more options
more options

Suluhisho teule

Now I understand why address book was not migrated. Unfortunately ti should have been made clear when automatic migration happened. Now I'll wait until this "bug" will be fixed.

more options

I believe the bug has been fixed in 78.1.0, which is why I posted the link to the release notes so that you could read for yourself the fixes that were done in this release.