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

সহায়তা খুঁজুন

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.

আরও জানুন

Unusual screen during upgrade process

  • 2 উত্তরসমূহ
  • 0 এই সমস্যাটি আছে
  • 63 দেখুন
  • শেষ জবাব দ্বারা sfhowes
  • মীমাংসিত

While attempting to upgrade my Ubuntu Thunderbird client, I saw the attached screen. I'm concerned because of the unsophisticated style of the page, and the fact that it asks for my password, which makes me think "phishing". Can some trustworthy person confirm that this is a legitimate screen?

While attempting to upgrade my Ubuntu Thunderbird client, I saw the attached screen. I'm concerned because of the unsophisticated style of the page, and the fact that it asks for my password, which makes me think "phishing". Can some trustworthy person confirm that this is a legitimate screen?
স্ক্রিনশটসমূহ সংযুক্ত হয়েছে

সমাধান চয়ন করুন

It’s smart to be cautious if the upgrade screen looks unusual and asks for your password. It could be legitimate, but to be safe, try upgrading via the terminal with `sudo apt update` and `sudo apt upgrade` to avoid suspicious pop-ups. If the screen still seems off, don’t enter your password and cancel the upgrade. Always trust your instincts with password requests.

প্রেক্ষাপটে এই উত্তরটি পড়ুন। 👍 1

All Replies (2)

চয়ন করা সমাধান

It’s smart to be cautious if the upgrade screen looks unusual and asks for your password. It could be legitimate, but to be safe, try upgrading via the terminal with `sudo apt update` and `sudo apt upgrade` to avoid suspicious pop-ups. If the screen still seems off, don’t enter your password and cancel the upgrade. Always trust your instincts with password requests.

The screen is legitimate, and appears when TB is first installed. It can also appear in an existing setup if TB has lost the location of the profile and acts like a new install. Usually, this is due to a corrupted prefs.js.file:

https://support.mozilla.org/en-US/questions/1489403