Avatar for Username

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

update from 47.0.1 to 49.0.2

  • 2 răspunsuri
  • 5 au această problemă
  • 2 vizualizări
  • Ultimul răspuns de jnygren

Lazerous
Lazerous
more options

Beta news just announced Firefox 49.0.2 (windows 32/64) but my version (47.0.1) says it's fully up to date what gives?

Is beta news faster to get the most recent Firefox than Mozilla's own update channel?

Beta news just announced Firefox 49.0.2 (windows 32/64) but my version (47.0.1) says it's fully up to date what gives? Is beta news faster to get the most recent Firefox than Mozilla's own update channel?

Soluție aleasă

I have almost the same problem. I started a PC I haven't used for a while, which was at version 44.something. I get a notification to update to 47.0.1. The update button on the 'About Firefox' screen shows the same. The description of the hotfix mentioned above doesn't sound like it has anything to do with this problem. Is this link correct?

Citește acest răspuns în context 👍 2

Toate răspunsurile (2)

philipp
philipp
  • Moderator
more options

hi, if you have not set firefox to update automatically, you may have to manually install the following hotfix addon to be able to jump over 47.0.1... https://addons.mozilla.org/firefox/addon/firefox-hotfix/

the reason for this is a bit complicated - it's basically a certain third-party software ("websense") that causes firefox 48+ to crash on startup so we are only updating installations where we know that they aren't users of this thirdparty tool at the moment.

jnygren
jnygren
more options

Soluție aleasă

I have almost the same problem. I started a PC I haven't used for a while, which was at version 44.something. I get a notification to update to 47.0.1. The update button on the 'About Firefox' screen shows the same. The description of the hotfix mentioned above doesn't sound like it has anything to do with this problem. Is this link correct?