McAfee VirusScan Drops Poison Pill in Recent .DAT
from the problems... dept
Michael Buccino writes “Late last night, I responded to several calls from Windows users on our LAN that they were unable to log in. Their logins were hanging on the login script. After troubleshooting the problem, I found that disabling McAfee Antivirus cured the problem. This problem occurred with Windows NT and Windows 9.x machines.” Michael then goes on to explain in more detail what the problem is and wants to spread the word. I have no idea of the validity of the claims, but figure I’ll post this as a public service announcement. If anyone finds out any more about this please let me know. In the meantime, the details can be read by clicking the link below. Update: TheRegister has picked up on this story as well, though they also admit they don’t fully understand what’s going on either.Late last night, I responded to several calls from Windows users on our LAN that they were unable to log in. Their logins were hanging on the login script.
After troubleshooting the problem, I found that disabling McAfee Antivirus cured the problem. This problem occurred with Windows NT and Windows 9.x machines.
I then queried users as to whether they had updated their virus definition files (.DAT files)lately. In turns out they had. Further investigation indicated that the 4102 McAfee .DAT update was the source of our problem.
When I tried to call corporate technical support at McAfee, I was put on hold, told by a recording that it would take a long time to answer my call due to extended call volumes, and given the Kevorkian disconnect.
Frazzled by now, I called our sales rep at NAI and asked if he knew anything about the latest .DAT file causing problems. He went through his e-mail and found that, indeed there was a problem with the 4102 .DAT file. He forwarded the information to me. Here is a portion of the internal NAI e-mail referring to the problem:
"We believe we have found the problem and are creating a new set of DATs. We STILL have not been able to reproduce the problem, or had absolute confirmation that there is any engine other than 4.0.02 that has the problem.
Every customer that has been worked with out of the Aylesbury QA lab has had the 4.0.02 engine.
If any one has reproduced the problem internally with another engine please contact me directly. No one in AVERT, has reproduced this, nor has there been any absolute confirmation from a customer site.
In light of this we are going to REV the DATs to the 4103 ASAP.
I'll update you ASAP on when this will happen, but at this time we are looking at 1-2 hours for this to happen.
In addition, we are pulling the 4102 DATs and rolling back to the 4101 DATs.
We are also working on a statement that will be posted to the web ASAP."
Well, that was this morning and now it is late afternoon on the West Coast. I went to McAfee's web site and saw no announcement. I bear them no malice, but want to inform Techdirt readers that they will experience this problem if they have the 188.8.131.52 engine, and not just with Windows NT computers. The fix is to uninstall McAfee and reinstall, and then update to the 4103 update. Or choose another product.
Comments on “McAfee VirusScan Drops Poison Pill in Recent .DAT”
Yay for McAfee!
I sure am glad I quit working there.
Coincidentally, so did several friends of mine who were QA engineers. 😉
NAI and the Poison Pill
NAI posted their side of the story on their web site today at http://www.mcafeeb2b.com/other/4102dat.asp.
In it, they blame their customers for having old virus engines. Guilty. Fixed the problem by choosing Norton AntiVirus.
Thank you for your input.
Re: NAI and the Poison Pill
Wait until you get a taste of what Symantec can do like not even updating your Virus protection.
DAT file problems at McAfee
The problem with the Browser not working also occurred with their 4153 DAT file.
My latest problem is that after downloading 4161xdat.exe and trying to install it, I get a message “Unable to find any qualifying product(s)”
Anyone know what this means? Do I need to buy the latest McAfee AntiVirus software. I was using ver. 4.0, have since switched most of my computers over to Norton AntiVirus 2001.
As an network administrator for the past five years, McAFee has never given me a virus alert; whereas, Norton has notified me of viruses upon installing it. Does McAFee work?
McAfee AntiVirus (5.21.1000)
Didn’t have a problem logging in, not using a network – but found that I couldn’t connect to the internet as the Modem froze when the Virus Shield was running. Is this unusual?
Re: McAfee AntiVirus (5.21.1000)
Yes, I have found that to happen. The program has been nothing but frustration since I downloaded the online virus protection. I have also experienced annoying freezing in general, sluggishness, and crashing. They are nice enough to offer software that fixes this problem that I never had before…
Customer service has been non-existent. Recently, when I went to “scan” online, it said I was not protected!!!! Went to the corresponding website and it seemed I’d have to download another product. I was reluctant, but eventually I did and found I had a virus from 4-2000. Their online scanning did NOT pick this up before.
Supposedly, I was properly enrolled, it would even show a pop-up screen that would “scan” my system. Then the warning message, etc., I am somewhat confused. Except that perhaps the product(s) is/are cr**.
I rue the day I purchased anything McAfee.
Re: McAfee AntiVirus (5.21.1000)
Have a customer who recently added VirusScan 6.0 to his **Win 95** machine. All was well for about a week, then his external U.S. Robotics modem froze up — All lights on. Reboot would not resolve the problem.
I had to remove McAfee, uninstall the modem drivers, disable the COM port, enable the port as a different COM port number, and reinstall the modem drivers. While I suspected McAfee to be the culprit, I wasn’t sure — so …
I tested the modem with several dial up sessions & various programs. OK. I re-installed McAfee, and as soon as the program & definition updates finished: BANG — the modem was locked up tight as a drum.
Again, I had to uninstall & reinstall everything — right down to the COM Port. But when I re-installed with Norton Antivirus 2001 (since 2002 doesn’t support Win 95), everything is A-OK.
I have also had customers who run McAfee and keep their definitions up to date get infected with viruses — which their friends and co-workers’ copies of Norton identified.
mcafee antivirus problems
yesterday i donwloaded the latest DAT and as you mentioned it is giveng me the same error regarding “qualifying product” etc. I used w98.
Prior to installing mcafee antivirus AND the personal firewall my problems were minor.
After I installed the the above items I could not do any browsing, after a dial coneection. Any other application that was ruuning ok prior to dial up to the internet frezzed.
Right after dial up I got a warning that a “virus” was trying to mail itself. After that warning the pc frezzed.
I reboot several times but the problem appeared esactly the same way.
I am starting to dislike mcafee…
Their instruction in the web site to solve the xxx@mm virus problem is confusing and fragmented.
Re: mcafee antivirus problems
Been having similar problem with McAfee with scan engine 4.5.1. Worst problem was with few systems still on 4.3 engine. Updated those and still had problem with systems locking at boot and requiring several boots to get Windows up. Seems inspite of taking several thousands of dollars each year for anti-virus upgrades, McAfee decided not to support their users with Windows 98. They must have stock in Microsoft or something because they announced last year they wouldn’t support 98 but still took the money. Now we are using a patch and have to uninstall every McAfee installation and reinstall. Wish it were my decision as I’d never use McAfee again ever. Certainly never use it on my several home systems, nor recommend to anyone. Not real happy with their website changes with no notice, either.