Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

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
Resolto Arquivado

AVG2015 keeps blocking the prefs.js file due to "potentially being OSX/Spigot"

FredMcD replied
NeoSpearBlade

Well, you saw the title.

This just started happening last night and I don't know why as it never happened before. I'm sure this is a false positive but I'm not sure how to make AVG know that.

The prefs.js file is located in "AppData/Roaming".

When AVG blocks the file, it also prevents it from generating another automatically. I have to restart my computer in order for FireFox to generate another prefs.js.....which then gets blocked again for the same reasons.

I don't know what to do next at this point.

I know that uninstalling and reinstalling FireFox is my last resort as I have 7 years of data I don't want to lose.

Right now, I have FireFox in Safe mode and still works as I left it (same bookmarks, same saved passwords, cookies not affected, etc.). I just can't save any preferences.

I hope this is just one of those random fits AVG has. Otherwise, this foreshadows a more serious problem and I really do hope that's not the case.

Well, you saw the title. This just started happening last night and I don't know why as it never happened before. I'm sure this is a false positive but I'm not sure how to make AVG know that. The prefs.js file is located in "AppData/Roaming". When AVG blocks the file, it also prevents it from generating another automatically. I have to restart my computer in order for FireFox to generate another prefs.js.....which then gets blocked again for the same reasons. I don't know what to do next at this point. I know that uninstalling and reinstalling FireFox is my last resort as I have 7 years of data I don't want to lose. Right now, I have FireFox in Safe mode and still works as I left it (same bookmarks, same saved passwords, cookies not affected, etc.). I just can't save any preferences. I hope this is just one of those random fits AVG has. Otherwise, this foreshadows a more serious problem and I really do hope that's not the case.
Ler a resposta no contexto

Chosen Solution

Sorry for the long delay. While this is important, I had other stuff to do.

Well, it seems that it was a false positive. After a scan from Advance SystemCare and a restart, AVG just stopped blocking it.

I was about to post a bunch of stuff that might help figure this out but now it's pointless.....However, after checking AVG's detection history, it turns out that this issue of mine has happened before 2 months ago. I honestly forgot about that, as well as how I resolved it, if I did anything. I probably did the same thing I did to fix this one.

So, this was a case of AVG returning a false positive. I feel much better now.....

Sorry to waste your time.

ADDENDUM: I'm not sure whether to mark this topic as solved. For the moment, I'll leave it as is, if that's OK.

NeoSpearBlade modificouno o

All Replies (5)

Open the options for AVG, and tell it to leave Firefox alone.

Maybe it's not a false positive. Have you noticed anything odd happening in the past 48 hours?

The prefs.js file contains custom settings, such as your home page, and various items added by extensions. Is it possible you have a new extension, or that you recently added and removed on? Spigot may be associated with Conduit Community Toolbar add-ons, coupon extensions, one called Searchme that takes over your default search, etc.

I suggest starting on the Add-ons page:

Check for Suspicious Extensions

Either:

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

In the left column, click Extensions. Then cast a critical eye over the list on the right. If it doesn't look like something you remember installing, disable or remove it.

Often a link will appear above at least one disabled extension to restart Firefox. You can complete your work on the tab and click one of the links as the last step.

Check for Left Over Settings

You might want to back up your prefs.js file before doing this in case you accidentally clear valuable data, such as your pinned/blocked tabs on the new tab page, or your toolbar icon layout.*

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

(2) Click the column heading Status to bring all the "user set" settings to the top; you may need to return to the top of the list

(3) Scroll down and look at the rows for anything mentioning spigot, mybrowserbar, conduit, community toolbars, or other unnecessary/obsolete settings related to any extensions you removed. To clear a row, right-click > Reset it.


* To back up prefs.js:

Open your current Firefox settings (AKA Firefox profile) folder using either

  • "3-bar" menu button > "?" button > Troubleshooting Information
  • (menu bar) Help > Troubleshooting Information
  • type or paste about:support in the address bar and press Enter

In the first table on the page, click the "Show Folder" button. This should launch a new window listing various files and folders in Windows Explorer.

Scroll down and find prefs.js, right-click > Copy it and then right-click > Paste it in a safe location such as your Documents folder or Desktop.

Note: By default, Windows hides the .js file extension. To work with files as accurately as possible, I suggest unhiding them. This Microsoft support article has the steps: http://windows.microsoft.com/en-us/wi.../show-hide-file-name-extensions.

Did you check the prefs.js file or search the about:config page for spigot?

Chosen Solution

Sorry for the long delay. While this is important, I had other stuff to do.

Well, it seems that it was a false positive. After a scan from Advance SystemCare and a restart, AVG just stopped blocking it.

I was about to post a bunch of stuff that might help figure this out but now it's pointless.....However, after checking AVG's detection history, it turns out that this issue of mine has happened before 2 months ago. I honestly forgot about that, as well as how I resolved it, if I did anything. I probably did the same thing I did to fix this one.

So, this was a case of AVG returning a false positive. I feel much better now.....

Sorry to waste your time.

ADDENDUM: I'm not sure whether to mark this topic as solved. For the moment, I'll leave it as is, if that's OK.

NeoSpearBlade modificouno o

NeoSpearBlade said

Sorry to waste your time.

Asking a question is not a waste of time.

That was very good work. Well Done. Please flag your last post as Solved Problem so others will know.