norwegian
Premium
join:2005-02-15
Outback
 ·WestNet Broadband
| reply to dadkins
Re: Kaspersky Update error, and fix.
said by dadkins  :I must have missed it... doing fine here.  Now that's a first.
Going by the posts in that link, from the moment DVi and Igor where notified it was just on 1 1/2 hours till there was a fix.
Quick turn around; they are known for that. 
--
The only thing necessary for the triumph of evil is for good men to do nothing - Edmund Burke |
|
jack b
Gone Fishing
Premium,MVM
join:2000-09-08
Cape Cod
clubs:
 ·Comcast
| I'm generally one who waits in the wings for a few days with any new program distribution, and as it turns out it might have been wise to wait a day or so in this case.
No big deal though, as it was less than 24 hours for the bug and a fix to surface.
Still a KIS fan.
--
~Help Find a Cure for Cancer~
~Proud Member of Team Discovery ~ |
|
Mele20
Premium
join:2001-06-05
Hilo, HI
| This wasn't a bug in MP1. I was the first to post a thread about it at Kaspersky forums. It was a BAD UPDATE. It affected ALL versions of KAV/KIS 2006. Kaspersky had to roll back the servers and then provided a tool to remove the bad update.
KAV crashed suddenly (which generated ProcessGuard popups regarding Drwtson and popups from Microsoft wanting an error report and other popups) and restarted and crashed (all popups again) and restarted and crashed, etc. I had it set to update every 5 minutes so when it downloaded this bad update file and crashed, every time it started it tried again and crashed again...over and over. Before posting about it, I ran the Microsoft debugger for XP and could see that it was the updater causing the problem. My post was confirmed almost immediately by Kaspersky saying they had uploaded a bad update and were in the process of reversing that.
The tool Igor provided didn't work for me. I got an error when I tried to run it. I couldn't delete the bad update file as KAV had self protection enabled. I had a hard time disabling self protection temporarily because I couldn't get to that area of the GUI before KAV would crash again. I finally got the bad file deleted and after that everything was fine.
I was very impressed with how fast Kaspersky acted on this and they were right there in my thread posting and monitoring. Igor even posted a zip version of the tool to fix the problem because I lost WinRar recently and so I couldn't open the RAR file he first uploaded.
The important point though is that this was NOT a bug in the newly released MP1 version. This was a bad update file.
--
"If you want to do DRM on a PC then you need to treat the user as the enemy." Ross Anderson in "`Trusted Computing' Frequently Asked Questions"
»www.msfirefox.com/ |
|
jack b
Gone Fishing
Premium,MVM
join:2000-09-08
Cape Cod
clubs:
·Comcast
1 edit | Thanks for the additional details behind the issue, Mele20.
It's not like a *vendor never pushed out an update that went OOoPS... *(insert least favorite company, here)
I had the new version of KIS installed and running smoothly yesterday afternoon, and was 'training it' right up until I went to bed.
I found it in 'crash-mode' in the morning when I got up, and found this thread had already started. I ran the clean-up file from Kaspersky forum and rebooted, and it's been fine since.
I just saw your thread over there, now.
--
~Help Find a Cure for Cancer~
~Proud Member of Team Discovery ~ |
|
Chris 313
Come get some
Premium
join:2004-07-18
Houma, LA
clubs:
·Comcast
·Comcast
·Charter Pipeline
 ·Comcast Digital Vo..
·AT&T CallVantage
| said by jack b :Thanks for the additional details behind the issue, Mele20. It's not like a *vendor never pushed out an update that went OOoPS... *(insert least favorite company, here) I had the new version of KIS installed and running smoothly yesterday afternoon, and was 'training it' right up until I went to bed. I found it in 'crash-mode' in the morning when I got up, and found this thread had already started. I ran the clean-up file from Kaspersky forum and rebooted, and it's been fine since. I just saw your thread over there, now. Damn, I re-installed KAV cause of this. I wish I'd have looked here first for the repair file. By the time I re-installed, KAV must've pushed out the fix. |
|
