Is this folder suppose be empty under user/name/appdata/roaming/mozilla/extensions
I recently used Dr. Web Cure It to find some Trojans and the file path it showed for the Trojans was user/name/appdata/roaming/mozilla/extensions and after it deleted them the Firefox extensions were acting buggy for example I updated VTzilla and it didn't ask me to restart Firefox so I closed Firefox and uninstalled and reinstalled Firefox will I installed version that is and after I did that tried to update VTzilla again and no problem but when I updated Firefox VTzilla was disabled and the new version 1.2 is supposed to work with Firefox version 8 it gave me message saying its not compatible so I removed it and reinstalled it again other than that all other extensions seem to be working fine for now but the second extension folder is empty under user/name/appdata/roaming/mozilla/extensions so is my Firefox going to be fine or not?
Chosen solution
Actually Firefox wasn't the real problem it was my Windows OS it was corrupt I had to reinstall it.
Read this answer in context 👍 0All Replies (2)
Extensions that are installed globally for all profiles are installed in the folder with the Firefox GUID {ec8030f7-c20a-464f-9b0e-13a3a9e97384} in that extension folder.
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.com/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 do a compatibility check or see if there is a compatibility update available.
Chosen Solution
Actually Firefox wasn't the real problem it was my Windows OS it was corrupt I had to reinstall it.
Modified