Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Shockwave Player shown as vulnerable but updated 3X & Flash Player up to date.

  • 1 wótegrono
  • 2 matej toś ten problem
  • 21 naglědow
  • Slědne wótegrono wót teeter

more options

Plugin Status loaded in Firefox. It showed both Adobe Flash Player and Adobe Shockwave Player as vulnerable. Updating Adobe Flasy Player to Shockwave Flash 22.0.0.292 seemed to work and show it uptodate but Adobe Shockwave Player remained vulnerable. I keep going to the link to update Adobe Shockwave Player, but after I do I still get the vulnerable designation (after refreshing). I have tried to uninstall and reinstall. I have restarted Firefox, although it doesn't say I need to. I'm wondering if this is a problem that Adobe changed the name. Or that the two are synonymous now. Martha Teeter

Plugin Status loaded in Firefox. It showed both Adobe Flash Player and Adobe Shockwave Player as vulnerable. Updating Adobe Flasy Player to Shockwave Flash 22.0.0.292 seemed to work and show it uptodate but Adobe Shockwave Player remained vulnerable. I keep going to the link to update Adobe Shockwave Player, but after I do I still get the vulnerable designation (after refreshing). I have tried to uninstall and reinstall. I have restarted Firefox, although it doesn't say I need to. I'm wondering if this is a problem that Adobe changed the name. Or that the two are synonymous now. Martha Teeter
Pśipowjesone fota wobrazowki

Wšykne wótegrona (1)

more options

I meant 22.0.0.192. Well in looking for support, I refreshed Firefox. And now the problem seems to have disappeared. No vulnerable Adobe Shockwave Flash.