ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

Firefox plugin check never makes list

  • 2 การตอบกลับ
  • 2 คนมีปัญหานี้
  • 23 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย Luckyrod

more options

I have reinstalled FF and I have updated adobe flash player 16 NPAPI and Shockwave for Director but the plugin check still spins.

I have reinstalled FF and I have updated adobe flash player 16 NPAPI and Shockwave for Director but the plugin check still spins.

การตอบกลับทั้งหมด (2)

more options

Note that your System Details List shows multiple Adobe Shockwave for Director plugins.

  • Adobe Shockwave for Director Netscape plug-in, version 12.1.5.155
  • Adobe Shockwave for Director Netscape plug-in, version 12.1.6.156

You can find the installation path of all plugins on the about:plugins page.


There are other things that need your attention.

Your System Details list shows that you have a user.js file in the profile folder to initialize prefs each time Firefox starts. The user.js file is only present if you or other software has created this file and normally it wouldn't be there.

You can check its content with a plain text editor (right-click: "Open with"; do not double-click). The user.js file is read each time Firefox is started and initializes preferences to the value specified in this file, so preferences set via user.js can only be changed temporarily for the current session.

You can delete the user.js file if you didn't create this file yourself.

You can use this button to go to the currently used Firefox profile folder:

See also:

more options

Thanks for the reply.

I wasn't able to find the path for these plugins Adobe Shockwave for Director Netscape plug-in, version 12.1.5.155 and Adobe Shockwave for Director Netscape plug-in, version 12.1.6.156 so I disabled them.

The user.js file was created when I reinstalled FF. It was empty so I deleted it also. The problem still persists. the updating of the plugin page loads forever.