Warning: Latest Kasperky 2009 def update does not detect any malware

I'm very interested in this version & I tried the current release but it was only on my machine for 4 hours, I would leave it on as permanent solution. If it were RC that would be diferent but I think we're not quite there yet. I hold high hopes that it'll be soon...

 

Whats to discuss after its been fixed and back to normal
It'll just be useless posts after that point.

 

Couldn't agree more.


Cheers

 

It has already passed the RC stage.

 

where can I get the RC?

 

I'm sure you've seen the thread on here about the technical release, that is, build 8.0.0.357. That is the version beyond RC stage.

Just an additional point, RC1 was build 8.0.0.324 and RC2 was build 8.0.0.346.

In case you've missed the thread, here it is:

https://www.wilderssecurity.com/showthread.php?t=207778

Edit: added additional info.

 

Baz Kasp explained what the TR is here:

https://www.wilderssecurity.com/showpost.php?p=1245215&postcount=13

 

You are correct

Still, I can do nothing but give a good laugh at this topic

 

how can i know if i'm already infected by malware?

geez!!! Beta or Official Release, its still "Kaspersky"....this kind of shitty shouldn't happen (12hours unprotected is toooo long)!

 

1) Its been fixed now, do a scan then you'll find out
2) If you're not prepared to get any incidents, use the official release version then. Its unreasonable to expect a unreleased version to be as stable a released... If you're not willing to accept the costs of using an unreleased version, don't use it. Simple.

Post #13 and #15 sum it all up.

 

Unreleased version or not, this makes you wonder about their backend quality assurance process on the defs.. This new version is about 15 days from release and they have no excuse for screwing this up.

 

It was fixed already... I do not see what there is to discuss

They can screw up whatever they like because it us Un-re-leased... if you are using an unreleased version and such stuff happens then there is only one person to blame. Guess who that is

If you still havent understood, that this problem did not affect any released products then your comment about "backend quality assurance" is completely out of place....because the only defs that caused this error were unreleased defs for an unreleased product

 

Does continuing this thread actually serve a porpouse. Everyody, including the resident norton fanboy shared thier thoughts. It is a beta product, it was fixed, kaspersky was bashed. I think everything that should have been said was said and continuing will only result in more bashing.

 

Agreed. No point in continuing, Time to move on.

 

this thread should be closed to avoid anyone getting confused.

 

That's a good enough reason for terminating this thread, especially since the problem has now been resolved.

thread is now closed.

Bubba