Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Getting message that Thunderbird must be restarted to finish a previous upgrade following a Windows Restore Point recall.

  • 2 odgovora
  • 2 imaju ovaj problem
  • 1 prikaz
  • Posljednji odgovor od Wayne Mery

more options

I experienced an error in Windows 10 that required me to drop back to the last restore point. (1 day prior) Now Thunderbird is giving me an error that "Your computer must be restarted to complete a previous upgrade of Thunderbird." Rebooting fails to correct the situation. Is there a registry changethat will correct this, or some other solution? Thunderbird had fully installed the most recent update prior to the Windows error.

Regards, -Ray

I experienced an error in Windows 10 that required me to drop back to the last restore point. (1 day prior) Now Thunderbird is giving me an error that "Your computer must be restarted to complete a previous upgrade of Thunderbird." Rebooting fails to correct the situation. Is there a registry changethat will correct this, or some other solution? Thunderbird had fully installed the most recent update prior to the Windows error. Regards, -Ray

Izmjenjeno od Wayne Mery

Izabrano rješenje

Made a backup of my Thunderbird Profile as a safety measure. Tried to uninstall the application, but received the same error message. Removed the application directory, downloaded the current install image and reinstalled. Fixed the issue, though this was probably overkill. Something that could have been corrected in registry or an .ini setting...

Pročitaj ovaj odgovor u kontekstu 👍 2

Svi odgovori (2)

more options

Odabrano rješenje

Made a backup of my Thunderbird Profile as a safety measure. Tried to uninstall the application, but received the same error message. Removed the application directory, downloaded the current install image and reinstalled. Fixed the issue, though this was probably overkill. Something that could have been corrected in registry or an .ini setting...

more options

Thanks for posting your solution. It's safe than providing instructions to edit registry