Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

On starting Thunderbird, I get a pop-up "mozalloc.dll" not found, but it still seems to work OK - does this matter ?

  • 3 respostas
  • 16 têm este problema
  • 1 exibição
  • Última resposta de JoeB

more options

I haven't deleted anything - and a search finds it in C:\Program Files\EMAIL\Thunderbird Setup 17.0.7. I'm on version 24.0.1

I also have Firefox, and so I have a version in C:\Program Files (x86)\Mozilla Firefox

What should I do (if anything) ? - Thunderbird appears to still work . . .

thx

MJ

I haven't deleted anything - and a search finds it in C:\Program Files\EMAIL\Thunderbird Setup 17.0.7. I'm on version 24.0.1 I also have Firefox, and so I have a version in C:\Program Files (x86)\Mozilla Firefox What should I do (if anything) ? - Thunderbird appears to still work . . . thx MJ

Todas as respostas (3)

more options

working from the theory everything is important (sometime it is not) simply reinstall Thunderbird from http://getthunderbird.com The issue is probably simply a misstated key in your registry, but a reinstall is far easier and less error prone that fiddling with the registry manually.

As data is separate from programs in Thunderbird that should get rid of the message and nothing else.

more options

thanks Matt - odd thing is , I did shutdown/start-up a few times, made no diff, popup appeared, then on my current startup, all clean. I guess an install (possibly an update ?) if it becomes an issue should solve it

cheers

MJ

more options

It depends on what that file does, or what calls it - at specific times. It may be idle for a while, until correct events cause something to call it - except it's missing, corrupted or a registry issue, as Matt said.

You might be able to re-register the dll. It may / may not help, but won't hurt. Fairly simple - just search "registering .dll".