ابحث في الدعم

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

Can't Update Adobe Acrobat NPAPI Plug-in?

  • 49 ردًا
  • 721 have this problem
  • آخر ردّ كتبه jscher2000

more options

...Pretty much exactly like the title says. I checked the plugin checker after updating to Firefox 30 to see if there was anything that needed updating. Of course, there was: Shockwave and "Adobe Acrobat NPAPI Plug-in".

While I was able to get Shockwave up to date just fine, the Adobe Acrobat NPAPI Plug-in is presenting some trouble. As in, when I click "Update Now", instead of redirecting to an update page, it redirects right back to the Plugin Check page.

Where can I go to update this plugin? Does it need to be updated? Is this a glitch in the checker, and therefore I don't need to do anything?

All Replies (20)

more options

ponyparty, I just posted this exact question twenty minutes before yours. I am glad to see I'm not the only one. Your problem is identical to mine, and started with the update to 30, although I had some related issues starting with 29. I hope we get an answer...

more options

Same story here. Ok, Firefox, you are reallllllly pushing the limits in your "take over user responsibility" efforts. I have about had it.

more options

To update the Adobe Acrobat plugin, please check for updates from inside your Adobe desktop product, either Adobe Reader or Adobe Acrobat. On the Help menu, you can find Check for Updates. Once this is updated, Firefox should detect the new plugin version the next time you start it up.

more options

@jscher2000: Okay, I tried what you suggested....and my program/product (Adobe Reader) said that no updates were available. http://i.imgur.com/hzhibvq.png

However, going to the plugin checker, it's still saying that my plugin is vulnerable/outdated: http://i.imgur.com/aq9pQ2v.png

So....what's the deal?

more options

Hello jscher2000--

Did that. Several times. Did you read the latest release notes for FF 30?

"With the exception of those bundled inside an extension or ones that are whitelisted, plugins will no longer be activated by default (see blog post)"

Really, this is unacceptable. I already have to babysit my browser for 15 min every morning to get it to create a restore point and to clear the history using the Expire History by Days plugin.

Now when I go to my online banking, I can not view my statements without downloading...if I payed attention to whatever the mad developers decided when they determined that Adobe Reader was such a huge security risk I can't be trusted to chose which sites I wish to view Adobe docs in. But I can no longer trust your plug-in checker if it is going to tell me what was yesterday O.K., but today is a "clear and present danger."

Slowly, upgrade by upgrade, they are taking away our freedom to decide how to best protect ourselves.

In IE, I can still view Adobe docs just fine. This is really bad.

This sucks!

more options

All: I filed a bug on this. "Adobe Acrobat NPAPI Plug-in" means the site is mistakenly comparing the current version for Mac with our Windows plugin, which does not match. Presumably they can fix that quickly so we Windows users get a correct detection and the all clear.

Hi Axis, the current version of the Adobe PDF plugin should not be blocked. The block list is completely separate from the plugin checker. If you check the Add-ons page, it should show either "Ask to Activate" or "Always Activate" and you should be able to pick your preference. You can set that using either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. Adobe should be at or near the top of the list.

Even if you choose to keep "Ask to Activate", you should be able to use the plugin on demand by clicking the icon in the address bar that looks like a Lego block. If that does not appear, you also can set site permissions on the Page Info dialog (right-click page or Tools menu), Permissions tab.

It's the same choice you have had for several versions now, but yes, it is another step in the grand plan to eventually phase out binary plugins in favor of HTML5 code, extensions, web apps, or other methods of rendering in-page content.

Modified by jscher2000

more options

@jscher2000: "All: I filed a bug on this. "Adobe Acrobat NPAPI Plug-in" means the site is mistakenly comparing the current version for Mac with our Windows plugin, which does not match. Presumably then can fix that quickly so we Windows users get a correct detection and the all clear."

So in short, it's a glitch, you think?

more options

Yes, if you are current as far as Adobe is concerned (, then that is the best you can do. The plugin check site is wrong from time and time, and clearly it is wrong currently for Windows users.

more options

@jscher2000: Yeah, that appears to be what I have.

more options

Same here. I guess we just wait for another update to be available and hope for the best. At least the plug-in works after I updated it manually through the actual Adobe Reader GUI.

more options

yo tambien tengo este problema con Adobe Acrobat NPAPI Plug-in pero tambien tengo este problema con Unity Player 4.3.5f1 y no hay ninguna actualizacion por eso no se puede actualizar. FIREFOX debe de tener la obligacion de saber que no existen nuevas versiones por lo tanto no se pueden actualizar. nos vuelven locos a los usuarios y FIREFOX debe saber que no voy a deshabilitar estos plug-ins porque los necesito. FIREFOX debe estar al corriente de este GRAN PROBLEMA. en la version 29 yo ya notifique a FIREFOX que el diseño no es tan importante y son tonterias notifique que mas importante era solucionar para siempre que los plug-ins fueran actualizados automaticamente y no volver locos a los usuarios tanto con experiencia y sin experiencia pues siempre hay gente novata que no sabe solucionar estos problemas. sin mas saludos a todos los usuarios de FIREFOX.

more options

Hi lauralamar8, thank you for your comment. The last time I checked, it seems the plugin check site does not have the correct information for the Unity Player plugin. Hopefully someone will fill that in soon. Until then, please refer to the source of the plugin to confirm that your version is up-to-date.

more options

hola jscher2000 soy lauralamar8 y lo primero gracias por contestar eres muy amable. te dire que el plug-in Unity Web Player esta informado desde ayer y ayer mismo recibi una respuesta de Unity Web Player que en 48 horas se pondria en contacto un representante de la unidad conmigo. cuando me contesten ya informare al foro de FIREFOX para ayudar a otras personas pero hasta ahora mismo no se nada como solucionar este problema. por mi parte en cuanto sepa algo ya lo informare y si alguien se adelanta y sabe algo pues que lo diga y asi nos ayudamos todos. jscher2000 te mando un cordial saludo.

more options

Hi lauralamar8, can someone from Unity file a "bug" in the tracking system:


For whoever is entering the bug:

To most quickly assign the bug to the plugin check site, scroll to the bottom of that page and use the product finder search box. Type or paste plugins. and click

Websites :: plugins.mozilla.org

more options

Hello jscher2000 and all--

It look like the plugin check site is now working!

more options

Yes, it's working OK now.

more options

FANTASTICO!!!!!!!!!!!! FIREFOX vuelve a funcionar correctamente ya estan actualizados todos los plug-ins. doy gracias al equipo de firefox que ha solucionado tan rapidamente el problema y por eso siempre navegare con mi navegador preferido que es FIREFOX.

Modified by lauradelpueblo

more options

Not working for original NPAPI issue in pluginchecker in Nightly 33. Same issue as OP.

Modified by maxmaggot

more options

Hi maxmaggot, Firefox 30 on Windows 7 x64 is showing this detection:

Adobe PDF Plug-In For Firefox and Netscape 11.0.07

with the correct result. Do you want to start a new thread for Nightly? Or maybe there's a better place to flag up issues with Nightly?

more options

Maybe it would be better to start a new thread on this as they have seemed to solve the problem with FX30. I'll file a bug on bugzilla as well for this. Thanks for the reply jscher2000

  1. 1
  2. 2
  3. 3