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

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více
Vyřešeno Archivováno

I have the latest version, but constantly getting messages that I'm outdated.

bosko2 odpověděl(a)
bosko2

I've got the latest version of firefox installed, yet I'm constantly getting messages that it's outdated - on Mozilla's site as well as many others.

I've deleted almost all of my plugins and extensions (and updated those I do use - though the Moz update your plugings page seems to have trouble with Shockwave Flash as well) ... and I still get the error.

The only thing I can think of is that I've somehow been too aggressive with my NoScript forbidding.

I've got the latest version of firefox installed, yet I'm constantly getting messages that it's outdated - on Mozilla's site as well as many others. I've deleted almost all of my plugins and extensions (and updated those I do use - though the Moz update your plugings page seems to have trouble with Shockwave Flash as well) ... and I still get the error. The only thing I can think of is that I've somehow been too aggressive with my NoScript forbidding.
Přečíst dotaz v kontextu

Zvolené řešení

Thanks, resetting the user agent as per the article seems to have solved it.

(the modified one that needed reset was general:extra:microsoftdotnet )

Všechny odpovědi (3)

Make sure that you are using Firefox 10? See Find what version of Firefox you are using to find your Firefox version, Latest version can be found here

You may need to reset your user agent as outlined in the article below.

Yes, as I mentioned I have the latest version - uninstalled and reinstalled, even.

I'll try resetting the useragent.

Zvolené řešení

Thanks, resetting the user agent as per the article seems to have solved it.

(the modified one that needed reset was general:extra:microsoftdotnet )