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

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

  • 2 replies
  • 2 have this problem
  • 3 views
  • Paskiausią atsakymą parašė 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

Modified by Wayne Mery

Chosen solution

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...

Skaityti atsakymą kartu su kontekstu 👍 2

All Replies (2)

more options

Chosen Solution

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