Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Thunderbird upgrade doesn't seem to have completed

  • 2 ответа
  • 5 имеют эту проблему
  • 1 просмотр
  • Последний ответ от Tizzie

more options

I attempted to upgrade to Thunderbird version 52.1.1 but this seems to have failed. It prompted for a reboot, which I did. But now the icon is showing as the setup icon, and when I click on it it prompts for the reboot again. I checked in task manager and there no thunderbird processes running. I have also tried to reinstall the program but it still prompts for a reboot to complete the previous install.

Can anyone help please? It's driving me mad!

I attempted to upgrade to Thunderbird version 52.1.1 but this seems to have failed. It prompted for a reboot, which I did. But now the icon is showing as the setup icon, and when I click on it it prompts for the reboot again. I checked in task manager and there no thunderbird processes running. I have also tried to reinstall the program but it still prompts for a reboot to complete the previous install. Can anyone help please? It's driving me mad!

Все ответы (2)

more options

rather weird in that Thunderbird DOES NOT REQUIRE A REBOOT to install. I would be inclined to think there may have been an issue with the install before the Thunderbird update, what ever that was.

But go to getthunderbird.com download a fresh copy and install it and see if that works better for you.

more options

Trying to reInstall had no effect except throwing up the message again. Uninstalling was just the same. In the end I renamed the Thunderbird folder under Program files and tried installing again (after deleting the parent.lock file from the data folder) which seems to have fixed the problem.

Now I'm wondering whether the install had in fact worked, but perhaps there was a flag somewhere that hadn't been reset when I rebooted, which was stopping me from getting any further.