Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 3 antwoorden
  • 2 hebben dit probleem
  • 5 weergaven
  • Laatste antwoord van bosko2

more options

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.

Gekozen oplossing

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

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

Dit antwoord in context lezen 👍 0

Alle antwoorden (3)

more options

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.

more options

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

I'll try resetting the useragent.

more options

Gekozen oplossing

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

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