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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

update not working

  • 18 uphendule
  • 84 zinale nkinga
  • 19 views
  • Igcine ukuphendulwa ngu tedych

more options

I have two PCs. One if them has updated to version 48 yestarday. The other one will not update. When I go to the 'about firefox" page it checks and says my firefox is up to date with 47.0.1.

Isisombululo esikhethiwe

yes that's still expected at this point but should change over the next few hours... (in order to quicken things up, you can install the firefox hotfix from https://addons.mozilla.org/firefox/addon/firefox-hotfix/ and check for updates again)

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 2

All Replies (18)

more options

hello, updates to version 48 are currently disabled for windows users until a startup crash with firefox and a particular third-party software is looked into and addressed with a version 48.0.2.

more options

That would explain it.

Thanks

more options

Still not working. 48.0.2 downloaded on one PC and the 47.0.1 PC will not find any updates.

more options

Isisombululo Esikhethiwe

yes that's still expected at this point but should change over the next few hours... (in order to quicken things up, you can install the firefox hotfix from https://addons.mozilla.org/firefox/addon/firefox-hotfix/ and check for updates again)

more options

philipp said

yes that's still expected at this point but should change over the next few hours... (in order to quicken things up, you can install the firefox hotfix from https://addons.mozilla.org/firefox/addon/firefox-hotfix/ and check for updates again)

Ahem... these next few hours have become a full week by now :-) I installed the hotfix, and indeed the update seems to happen now. Thanks.

more options

It's now about 2 months later and I still can't update my 47.0.1! 49.0.1 is out. I refuse to take additional steps just to be able to update my browser. I always do it manually via Help - About, for years. I've never heard of Websense or such s***. Why did Mozilla just make it permanently impossible to update the browser for all users who had not updated it within some timeframe?! One of the machines got past 47.0.1 and updated to 48 (and now 49.0.1) a week or two ago. The addon mentioned in several articles, did not help. Is it the only way to download the latest full version and install on top?! What do we do if we have hundreds of workstations not being able to update themselves? This is plain stupid!

Okulungisiwe ngu tedych

more options

Still not working. Everyday PC has updated to 49 and this PC is still saying it is up to date on 47.

more options

@jdevlin: even with the hotfix addon installed?

more options

I have not installed the hot fix. The other machine doesn't have it. I don't like putting unnecessary addons onto may machine. I will try it.

more options

OK it is updating to 48. Why didn't it go direct to 49? I am wasting my bandwidth downloading unnecessary stuff.

more options

And now it updated to 49.

more options

Does anybody know what's and why is happening? The app.update.url setting seems right as it has always been. I thought 48.0.2 (and presumably 49) had fixed the websense issue, no? Then why they still won't update everyone (47.0.1) with their current (and standard) app.update URL??

more options

This is a complete joke to users. Still 47.0.1 "is up to date". Mozilla is forcing users to leave Firefox and migrate to the already only browser on the planet (unfortunately). Combined with ridiculously slow electrolysis advance and introduction to userbase, and other factors, strongly shakes the confidence for even the die-hard fans of FF, like me. I guess this is the wanted behavior, there is no other excuse.

more options

tedych schrieb

It's now about 2 months later and I still can't update my 47.0.1! 49.0.1 is out. I refuse to take additional steps just to be able to update my browser. I always do it manually via Help - About, for years. I've never heard of Websense or such s***. Why did Mozilla just make it permanently impossible to update the browser for all users who had not updated it within some timeframe?! One of the machines got past 47.0.1 and updated to 48 (and now 49.0.1) a week or two ago. The addon mentioned in several articles, did not help. Is it the only way to download the latest full version and install on top?! What do we do if we have hundreds of workstations not being able to update themselves? This is plain stupid!

Same Problem here, on one machine it worked after installing the Firefox Hotfix, but on the other machines it still says 47.0.1 is up to date! Update is not working. Bad Situation.

more options

It turned out that when your Version is 47.0.1 and you have set the LOCKPREF Setting lockPref("app.update.url"); the Update will not work! I had to remove the lockPref Setting for the app.update.url and after that, the update worked.

more options

Kevin Eastwood said

It turned out that when your Version is 47.0.1 and you have set the LOCKPREF Setting lockPref("app.update.url"); the Update will not work! I had to remove the lockPref Setting for the app.update.url and after that, the update worked.

Kevin, you had manually set this option before? I don't have such customzation and never knew about such option. Still "up to date".

more options

tedych schrieb

Kevin Eastwood said
It turned out that when your Version is 47.0.1 and you have set the LOCKPREF Setting lockPref("app.update.url"); the Update will not work! I had to remove the lockPref Setting for the app.update.url and after that, the update worked.

Kevin, you had manually set this option before? I don't have such customzation and never knew about such option. Still "up to date".

Yes the Lockpref has to be set manually before. This is used to prevent users from changing settings he should not.

more options

Ok, now with the abovementioned add-on, my main FF updated to 48.0.1 (or was .2 ..), then I removed the add-on, and FF updated to 49.0.1 successfully. Why have we had to go through this stuff to cross past 47.x, is beyond me.

Okulungisiwe ngu tedych