Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

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

  • 3 respostas
  • 1 tem este problema
  • 5 visualizações
  • Última resposta por 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

Todas as respostas (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.