Hi folks!

Anyone know of a changelog for the product hotfix to .h today (3-31-2009)?

Would be cool to know what the cause of the hotfix is.

Best,

Marty

Hello,

ya i got that too. anyone can explain this hot fix?

Yeah, new klif.sys (.333/XP) will solve some memory leak problems and IE8 using on 64 bit systems.

/On hands and knees begging for some help

So can we PLEASE have changelogs before they actually happen. With this big April 1 Virus scare going on, my co-workers are flipping a lid over having to restart servers the day before "the big one".

A little advanced notice would help us administrators redirect some of the heat we get when we have to say. "Oh btw, Kaspersky released another module update, and we have to restart the servers...again..."

/endBeg

Would be nice to have a sticky in the forum about 24-hours beforehand w/ changelog -- I just wonder if the mods get advance notice, or do they receive the same notice we get (i hope not).

marty

My major issue with the way Kaspersky does it's Module updates, is that I have to call them to figure out what the heck they did so that I have a good reason to restart servers. See atleast with MS patches, I can just read the blurb, and tell my boss, "Here is WRITTEN explaination as to why we have to restart the servers." With Kaspersky, I have to call, and sometimes call again just to confirm, and then say "well I was told...."

Having changelogs in writing goes much further than word of mouth. Frankly, there is absolutely no reason there aren't changlogs for Minor Releases. This is the first AV solution that doesn't include that, and honestly, it's my biggest complaint with Kaspersky at this point. Especially considing past minor releases they have done...not so well.

I should know EXACTLY what the patch is if it requires a restart, and that is really the bottom line.

Are we fully protected after the last update then if we don’t reboot the servers now?
I have quite a lot of servers to reboot if that is what is needed, or can I take my time rebooting them then?

Yes you will be protected fully if you don't reboot the servers now.
The patch "h" changed the driver "klif". The reason of change klif was memory leak and then operation system was frozen and didn't work.
So if your computers work well you don't need reboot computers now. You can reboot your servers later.

Olesya --

Is it possible to either add a sticky (as necessary) to this branch of forum to keep everyone updated when updates are released (such as the .h hotfix yesterday), and similar to the beta testing announcment at the top of this branch?

It would probably save support staff (and moderators) time answering questions in multiple posts (such as the kilf.sys issue that prompted the prior hotfix), as well as having to merge many when the forum is overloaded with the same topic.

Best,

Marty

I found this thread right now and updated the application module on my PC.
But KAV installed the hotfix "i", not "h".

What happend with "h"?
Where's the changelog for "h" and "i"?

Kaspersky....administrators nightmare

Hi,

I think the reason for the update to .i (334) was that .h (333) did not appear to fix the memory leak. In fact, it may have made things worse.

I had been trying to work out why some of our servers were running out of paged pool memory and with the use of PoolMon.exe and MemSnap.exe, I narrowed it down to Kaspersky.

Now that the affected servers have been updated to 334 of Klif.sys, they no longer crash (it was happening at least weekly) but MemSnap.exe still shows a memory leak in Klif.sys.

Is anyone else seeing this behaviour?