This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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.

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

  • 3 fhreagra
  • 16 leis an bhfadhb seo
  • 1 view
  • Freagra is déanaí ó 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

All Replies (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".