Kav 5.0.383---NEVER AGAIN

Indeed, where is it? I know it is completely off topic but sometimes curiosity wins over everything. The lake surrounded by trees look like Acadia (National Park) but the mountains do not look like Acadian mountains.

Acadia

 

I wish I could tell the name of the place but the name of the wallpaper is just (E-Glare)

 

Ahh, with people in my family owning a few HP's I now see how this may happen.

I had this issue about 1.5 years ago with a HP. If I remember correctly I was uninstalling some of the proprietary HP OEM software and this when it occured.
But since BigC, I will assume, is not using the factory image and has a clean XP install, it would seem to point to some of the drivers you need to load for all of the HP specific hardware.

Stuck here for now until we find out if it is/was a OEM image or a clean XP install.

 

I am not competent to make many judgments here. However, I have thought that if I left Bit Defender I would go to KAV, but I do not have the expertise to make any special rules. Anything I get must be reliable and functional with the default settings.

Having used esan MWAV, I have seen FP with the old and new versions. That has made me wonder if KAV would not also have many FP. From what I read on this forum, it appears that it does.

But the bottom line is that if it does not work "out of the box" I don't want it.

Jerry

 

I think i might have nailed it BigC.

There was a virus hidden in your wallpaper image ! Only kidding, just trying to lighten things up a touch.

I've often been tempted to try KAV 4.5, might do it one of these days too.


StevieO

 

I used XP disc's supplied by HP for this specific computer. Instead of needing six disc's to reinstall I only need one and about a half. This is because of what customizing was done before delivery.

 

Why would you use the disc supplied by HP? Everyone knows that the discs supplied by HP (Compaq) install all of their useless software and all kinds of other junk, some of which is spyware. It's not a "clean" install of XP, it should be against the law for them not to give you an original XP cd.

This thread is really beginning to make me wonder.

 

You don't seem to read or understand what it is you are reading you just take off on a rant. Like I said it takes one and a half cd's to install my XP, it installs so sparse the add remove is completely empty. there are not even any sound drivers installed. That is about as clean an install as you are going to get. That is less than a gigabyte for a full xp pro install.

 

May I make a suggestion. Since the configuration should be the same, why not just re-run KAV 5 with auto turned off. This would surely find the dll in question. If you do not want to re-install KAV, it may be possible for KAV to provide you with a web version to do a completel scan.

Something is really wrong here and it would be nice to get to the bottom of it. Hopefully KAV will cooperate, because actually I think it should be quite easy to get to the bottom of this. It may be possible to simply scan the HP drivers. The number of possible programs that have to be scanned is very small. It is only the ones that are required for startup in safe mode that are not Windows XP files. This has to be an extremely small number of files, and they may be all on the HP cd.

Rich

 

Let me put it this way. I am not the least bit interested in running Kav on my computer again. I started this thread just as an alert that this can happen with Kav. I have done that and now I am running a different av that in many years use it has never given me any trouble. I was only checking the new version of Kav out,it was not my default av. and yes I uninstalled my regular av to try kav. I have said all that I feel I want to say on the subject. Since I am not trying to find a way to run Kav I am now officially off of this thread.

Thanks for everyones participation.

bigc

 

One last note, like I have said several times it would not even try to boot at all. In any mode. It just had a black screen with the missing system file warning in white letters.

 

Come on, you said this was a "clean" install of XP, now it was from HP's discs and you had uninstalled another antivirus program prior to installing KAV.

From your previous posts you made it sound as if you had just installed XP with nothing else then installed KAV and the problem occurred, but that's not the case at all.

It is apparent to me there was a problem with KAV or your pc if it immediately turned off, that shouldn't happen regardless of what settings you were using with KAV.

I'm amazed that someone so computer savvy wouldn't try to figure out exactly what happened. You have bashed a product based on an isolated incident without even giving accurate details to what actually happened, if you are simply posting this thread "just as an alert that this can happen with Kav" then why not troubleshoot it to help others if it happened to them?

 

Yes, clearly this problem can be very quickly narrowed down to maybe one critical, non-Windows XP file, that is needed for startup, since you didn't even get into safe mode. Since you have your configuration files, maybe you can send the CD to KAV for a scan.

What I got out of this thread is this:

1) One should never run any scanner/remover package in Auto mode, since the possibility always exist that a false positive can occur with any package, and this is especially critical if any system file is involved. Do not turn on Auto delete under any circumstances!! Anyone who has run AV, AT, or AS (especially AS) scans knows this.

2) It may be wise for vendors of software packages that could potentially delete system files to totally disable Auto delete capabilities in their products because of this possibility and because new users may not be knowledgeable of this possibility. Of course, once someone has this problem (as I did with another AV package ), one learns.

Hopefully, still we are able to narrow down the few critical, non-Windows XP files that were on the machine, get them scanned, and make sure that they are no longer in KAV's database. Hopefully this will prevent others from meeting the same fate.

Regards,
Rich

 

There you go misquoting again. if you will go back and look at what I said you would see that I had reformated to days before it is even colored in blue, pretty hard to miss. And no where have I bashed Kav, I have posted about a problem I had while running it and that I didn't care for the Kav 6 beta either. It is not bashing to state that I don't care fora product. and as far as wanting to find what the undisputable cause was is just not something I care to spend my time doing. I was just trying the new version to see if I liked it, well I discovered I don't care for it so as far as I am concerned, case closed.

 

I've been using KAV since the 5.0.383 update and even after several full scans I have had no problems to report. It has been operating smooth as silk on my computer.

 

All I can say on this matter is that as a typical average user. If I install a new program of any type I go with the default settings at least initially. Why? Because average users figure that the program creators know the program best. So if the creators say use these settings the average guy is going to go with that at least until he stumbles upon something like Wilder's and starts tweaking.

 

Hi Hammer,

Same here. I try to avoid "tweaking" until I really understand what is going on. In so far as "auto delete" goes, I learned a long time ago about false positives, especially false positives on critical files, and I never, ever, put on auto delete. However, for safety reasons, I think it behooves vendors, to place special protections in place that require users to confirm any deletion of known critical files. In this way, the situation that we are now discussing could have at least been forewarned.

But it is a good thread. It highlights, as you said, 1) the fact that users should not start "tweaking" default settings unless they know what that they are doing and 2) that auto delete is a very dangerous setting unless there is no chance that the scanning software will not delete any system files.

Cya around!

Rich

 

Since Big C claims he wasn't bashing, and accuses others of putting words in his mouth, here are some selections from his original post, straight from the horse's mouth:

"this great saviour to mankind Kav antivirus" --- bashing
"any av that puts so many crap signatures in it's database" -- bashing
"a trigger happy antivirus" -- bashing
"Well enough of the rant" -- even acknowledges it was bashing!
"because Kav can jump up and bite you in the Butt at any time in my experience" -- bashing, the phrase "in my experience" was a nice false touch

Why don't you change your nick to Big BS, since you clearly were bashing according to your own words and admission: enough people have pointed out that this is an isolated issue with your own system. If the issue was false positives, there is no way the original post was written to reflect that: based on an isolated incident, you were prepared to warn everyone off KAV, which you did, despite the fact that this has not been a reproducible error on anyone else's system with the same configuration.

This was irresponsible, ridiculous behaviour from a moderator who should have known better, but coming from a NOD32 fanboy site, it doesn't surprise me. A similar thread on NOD32 would have brought all the moderators out defending the product from product bashers, but all they were willing to do in this instance is a lame "this is about false positives only", and "stick to the facts." Well, Big C wasn't being particularly factual, objective or scientific himself: how come no moderator has called him out on that?

I've also experienced false positives with NOD32 and other AVs including KAV so?

 

In my post#13 I also stated it was my fault and that it was just a stupid program that does what it is told to do as any AV will . I had it set to delete (which is what Kav suggests.) It is possible that another AV might have done the same thing. But in the two days since a reformat my other AV didn't do it, but Kav after just two hours did. I have had very good luck with Kav in the past but The newer versions I don't care for . I had a problem with it and said so. Any software of any kind can and do screw up and Kav is no exception.

and a rant and bashing are two different things and if I thought Kav was a total Pile I would just say so. But In reality Kav is a good product but I had a problem with it and and prefer not to use it any further..

 

Yes, as most of us have have. In this situation, the problem files should be easily isolated to a small number of critical, non-Windows XP files, that are either: 1) on BigC's system right now (they have to be there if the system was restored to the original state as it was before KAV as installed), or 2) on a non-Windows XP CD that contained these files during the install. In either case, I hope that the source CD that contains these files/drivers are sent to Kaspersky's labs for analysis as soon as possible. If they are HP drivers (even if they are very old ones or custom ones), they should be exempt not only from KAV's databases but all AV databases.

Regards,
Rich

 

If KAV removed a legit system file that crashed your system then how come nobody else has reported this?

I have KAV installed on countless clients pcs and have it set to update every 3 hours and scan every night at 4AM, always utilizing the extended database and to automatically remove anything found. I use KAV Pro with the redundant database and my pc scans every night at 4AM.

I haven't had any calls from any of my clients saying their systems crashed, my pc hasn't crashed..... so obviously it isn't a system file that was falsely removed by KAV that caused the issue. It was something specific to your pc, software installed or hardware..... but you didn't take the time to figure it out, you just posted on a top notch security forum that a lot of people read bashing a very good product..... without all of the details.

 

I think that this whole thing can be solved by simply taking an image copy of the system, install KAV 5, run KAV with auto delete off, find and identify the sucker, and uninstall KAV.

Rich

 

I will make a concession on this mess. I will contact HP Special Products Devision that built this computer for me, and also created the special disc's that restore the modified system and will ask for permission tp copy the disc's. If they say it is all right then I will burn a copy and send it to Kav. If they scan the disc it should find the same files installed or not. because if they were on my comp they are on the disc.

 

I just called HP but the department I need to talk to ( second tier customer support) will not be available until Monday morning. They are supposed to call me early in the morning. If they don't I will call them back. I know several of the people there pretty well from when I had my shop so there shouldn't be a problem when I explain the situation. As soon as I have comfirmation I will post back here to let you all know that I have sent the disc to Kav to be analized.

 

You see, BigC is da man.

Some of you were kind of beligerant, buffoonish, and brazen with BigC, yet he continued to explain and re-explain his predicament again and again.

And even though he stated he was done with the thread repeatedly, he did not lock it, to give everybody a chance to have their peace. And then when people kept misrepresenting him, he kept coming back to clarify things, and in the end, he is trying to help make the software better --- the same software that took him down.

Now that's a good guy. Reminds me of my mechanic Ray, that guy put in a couple extra hours because he didn't know how complicated it is to change a water pump on a Ford Escort, but he kept the cost at the estimate just because integrity is so important to him.

Too bad BigC is retired, because somebody that honest and forthright is hard to find. Last time my keyboard went bad because I dropped taco meat in it, I took it to a guy who said he could clean it out. He could not make it work, but still wanted to charge me about the price of a new keyboard!!