Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

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

Since upgrade to Thunderbird Version 60.5.0, all Microsoft Attachments open with a "corrupt file" and then repair which eventually open except for Visio

  • 1 reply
  • 1 has this problem
  • 132 views
  • Last reply by BirdThunder
  • Archived

Since upgrade to Thunderbird Version 60.5.0, all Microsoft Attachments (xlsx, ppt, docx, vsdx) open with a "corrupt file" and then repair which eventually open except for Visio which seem completely corrupt. If I use company webmail or even Outlook, the same files open fie from those clients. On forum one possible solution is to download and install https://taskcluster-artifacts.net/AcRd5mSOROO3yWDvEyrmSQ/0/public/build/install/sea/target.installer.exe, but I'm not allowed to install this per company rules due to no authenticated certificate. Warning on install states "this file does not have a digital signature which verifies publisher".

Should I uninstall and revert back to an earlier version or will this be fixed soon without users having to do workarounds on their own?

Thanks,

Steve

Since upgrade to Thunderbird Version 60.5.0, all Microsoft Attachments (xlsx, ppt, docx, vsdx) open with a "corrupt file" and then repair which eventually open except for Visio which seem completely corrupt. If I use company webmail or even Outlook, the same files open fie from those clients. On forum one possible solution is to download and install https://taskcluster-artifacts.net/AcRd5mSOROO3yWDvEyrmSQ/0/public/build/install/sea/target.installer.exe, but I'm not allowed to install this per company rules due to no authenticated certificate. Warning on install states "this file does not have a digital signature which verifies publisher". Should I uninstall and revert back to an earlier version or will this be fixed soon without users having to do workarounds on their own? Thanks, Steve

All Replies (1)

Thanks for the response. I assume this be an automatic update and if in a few days, I can wait.

Thanks!