502575 - Firefox can´t update when kaspersky 2010 is running

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: Kaspersky AV, defect)

Description

[elguerreroesp]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090705 Minefield/3.6a1pre (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090705 Minefield/3.6a1pre (.NET CLR 3.5.30729)

When I try to update the browser, the update starts, but appears an error message, and finally the browser hasn´t updated.

Reproducible: Always

Steps to Reproduce:
1.Click in checks for updates.
2.Restart firefox to complete the update.
3.Firefox can´t update.
Actual Results:  
Firefox can´t update

Comment 1

[Matthias Versen [:Matti]]

>but appears an error message,
And what does this error message say ?

Comment 2

[elguerreroesp]

(In reply to comment #1)
> >but appears an error message,
> And what does this error message say ?

The error massage says:
"The update could not be installed. Pease make sure there are no other copies of Firefox running on your computer, and then restart Firefox to try again."

Comment 3

[Matthias Versen [:Matti]]

Can you try the full installer ?

Comment 4

[Dean]

Same thing happened to me.  I had to temporarily disable Kaspersky to get the update to work.

Not sure if it affects updates in general, or the specific update being installed though.

Comment 5

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.

Comment 6

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 7

[timeless]

We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.