McAfee virus bug crashes Windows

By Eric J. Bowden, BugNet
06 November 2000 11:13 AM
Tags: mcafee, virus, scan, virusscan, definition, engine, bug, update

Update Version 4.0.4102 to blame

The virus definition file in question is version 4.0.4102.

BugNet used KeyLabs to verify this bug. After downloading and installing the latest virus definition files, our computer system restarted without prompting, making us a little concerned right from the get go. The test systems appeared to be starting correctly, but as soon as we entered the logon passwords, the systems froze. Even Control+Alt+Delete wouldn't invoke the Task Manager. The only alternative was to hit the power button to restart the machine.

All Windows platforms could be affected by this bug if the installed version of the VirusScan has a scan engine version of 4.0.02. To check the version number, launch VirusScan and select About from the Help menu.

According to McAfee, the virus definition file contains a driver that emulates the virus. The two-year-old anti-virus scan engine does not understand the new virus definition which, in turn, causes the computer system to crash.

It is important to keep these engines updated so that users can keep up with the features of the latest virus definitions. McAfee also warns users that after upgrading the scan engine, they will likely find new viruses that were on their systems but previously undetected.

When asked why the update mechanism doesn't check for compatibility before applying the update, McAfee responded by saying they didn't know, but there is probably no reason why it couldn't. Given the severity of this bug, bundling future software upgrades with the updated virus definition file would be in order.

Advertisement

Talkback 2 comments

    I am not sure as to the releva ...Anonymous -- 20/04/01

    I am not sure as to the relevance to this but I look after a corporate network with Mcafee installed everywhere and the DAT file is 4134, the version in the article is 4102 which is quite old as far as I know

    I just installed 4.0.4226 on a ...Tom Olson -- 02/10/02

    I just installed 4.0.4226 on a new system (Windows 2000 Pro) and had the same problem. The problem with safe mode, however, was that I could not start McAfee. The trick I used was to rename the installation directory and then change it back when the system booted.

Add your opinion

Latest Videos

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

Tags

Back to top

Featured