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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Mozilla keeps auto-generate string values for newtab and search engine

  • 3 fhreagra
  • 1 leis an bhfadhb seo
  • 5 views
  • Freagra is déanaí ó cor-el

more options

I've accidentaly installed babylon toolbar on my system. now I've uninstalled the toolbar and deleted all the registry values that contained babylon. But when I open my Firefox, babylon modifies the newtab and searchengine strings so that babylon is the page to open in a new tab.. I've resetted the values in about:config several times and I've also re-installed firefox (with deleting everything). Do you have any solution for this problem? Also, I have an addon called "Browser Protect", which I'm unable to delete.

Best regards, Mathieu Blauw

I've accidentaly installed babylon toolbar on my system. now I've uninstalled the toolbar and deleted all the registry values that contained babylon. But when I open my Firefox, babylon modifies the newtab and searchengine strings so that babylon is the page to open in a new tab.. I've resetted the values in about:config several times and I've also re-installed firefox (with deleting everything). Do you have any solution for this problem? Also, I have an addon called "Browser Protect", which I'm unable to delete. Best regards, Mathieu Blauw

All Replies (3)

more options

Hello Mathieu, see the steps : How to remove the Babylon toolbar, home page and search engine

thank you

more options

Yes, I did everything from there and all the other post about babylon I found. Nothing seems to work. Would it help to install babylon again and try to deïnstall? Maybe I did it the wrong way and is that why it is not working correct at the moment?

more options

If you do not keep changes after a restart then see:

You can check for problems with preferences and try to rename or delete the prefs.js file and possible numbered prefs-##.js files and a possible user.js file to reset all prefs to the default values.