cannot re enable the add ons after the new 13.0.1 update ,it shows no update available and all the add-ons are disabled
cannot re enable the add ons after the new 13.0.1 update ,it shows no update available and all the add-ons are disabled
All Replies (5)
Which add-ons specifically are you talking about?
It is possible that there is a problem with the file(s) that store the extensions registry.
Delete the files extensions.* (e.g. extensions.sqlite, extensions.ini, extensions.cache) and compatibility.ini in the Firefox profile folder to reset the extensions registry.
New files will be created when required.
See "Corrupt extension files":
- http://kb.mozillazine.org/Unable_to_install_themes_or_extensions
- https://support.mozilla.org/kb/Unable+to+install+add-ons
If you see disabled, not compatible, extensions in "Tools > Add-ons > Extensions" then click the Tools button at the left side of the Search Bar (or click the "Find Updates" button in older Firefox versions) to check if there is a compatibility update available.
kaspaskey URL adviser,Anti-Banner,IDM
in this case you'd have to contact the vendors of the addons, since they are responsible for providing updates.
you could also use WOT, adblock plus & down-them-all as alternatives, since they work well with the current firefox (& the release schedule):
https://addons.mozilla.org/firefox/addon/wot-safe-browsing-tool/
I have the same problem. One minute everything was okay, the next minute all my addons were disabled.
Adobe Acrobat 10.1.3.23 AVG Site Safety Plugin 11.1.0.4 Google Update 1.3.21.115 Java Deployment Toolkit 7.0.50.255 10.5.1.255 Java Platform SE 7 U5 10.5.1.255 Shockwave Flash 11.3.300.265 VLC Web Plugin 2.0.2.0 Windows Presentation Foundation 3.5.30739.1
I can reenable them but FF will disable them on the next startup. I uninstalled version 13 and installed version 12. Problem gone! So I'm still using version 12 and am afraid to update to version 13.
This problem began when I was trying to research and fix a problem (no history all-of-a-sudden) so it probably was something I caused. Can't recall everything I did though.
So: Does the addon problem I described have a solution? If so, I'll update my version 12 to version 13. Please respond.....
Modified