Skip to content

Categories:

Problems With Logitech QuickCam Software and Mozilla Thunderbird Update 2.0.0.5

I am an early adopter, and I am running Windows Vista on my laptop.  I ran into an interesting problem where the auto-update to Thunderbird 2.0.0.5 kept failing.  It complained about a file that needed updating was in use.  I tried every potential workaround I knew to resolve the problem, including running Thunderbird as Administrator.  Luck was not on my side.

A bit of Googling turned up this gem in the Thunderbird forums.   Apparently, if you run the Logitech Quickcam software on your machine, you need to disable it to allow the updater to complete its work.  I found that to be slightly interesting, to be sure.  I can attest that disabling the Logitech software allows the update to run to its completion.

If you run into the same problem and happen to be running the Logitech QuickCam software, make sure to disable it before running the update.

Posted in Uncategorized.

Tagged with .


4 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. Geoff says

    And is there an explanation for this, or is it just assumed to be one of those things that happens ?

  2. Geoff says

    And is there an explanation for this, or is it just assumed to be one of those things that happens ?

  3. JJT says

    @Geoff: My only presumption here is that the Logitech software locks a system DLL, and hence it must be off in order for the update to presume. Remember that the QuickCam software has hooks into messaging applications–including email and instant messaging. While I did not fire up FileMon to see what was happening, I am fairly certain this is exactly what is happening.

  4. JJT says

    @Geoff: My only presumption here is that the Logitech software locks a system DLL, and hence it must be off in order for the update to presume. Remember that the QuickCam software has hooks into messaging applications–including email and instant messaging. While I did not fire up FileMon to see what was happening, I am fairly certain this is exactly what is happening.



Some HTML is OK

or, reply to this post via trackback.