The Dreaded WebScanX.exe Crash Is Back

  • Thread starter Thread starter David F. White
  • Start date Start date
D

David F. White

I just installed the update for Internet Explorer 6 from the Microsoft web
site. I am running Windows 2000 Professional with McAfee VirusScan version
6.02.3000, scan engine 4.3.20, and the latest definitions. After applying
the update WebScanX.exe crashes when my system starts up. I knew this was
a problem with earlier versions of VirusScan but I didn't expect to see it
again. Anyone else run into this problem?

Thanks...

Dave White
 
| I just installed the update for Internet Explorer 6 from the Microsoft web
| site. I am running Windows 2000 Professional with McAfee VirusScan version
| 6.02.3000, scan engine 4.3.20, and the latest definitions. After applying
| the update WebScanX.exe crashes when my system starts up. I knew this was
| a problem with earlier versions of VirusScan but I didn't expect to see it
| again. Anyone else run into this problem?
|
| Thanks...
|
| Dave White

That version of software is out-of-date and is probably no longer supported.

The ENGINE is has to be v4400 to work with the latest DAT files.

You may be able to download the latest SuperDAT and execute it with the --> /F
Switch parameter to FORCE the update.

ftp://ftp.mcafee.com/pub/antivirus/superdat/intel/

The latest (as of this post) is sdat4468.exe

Start --> run
sdat4468.exe /f
 
I am having the same problem as Dave and I can confirm that I am
running v4400 and dat files 4468. Any other ideas?
 
| I am having the same problem as Dave and I can confirm that I am
| running v4400 and dat files 4468. Any other ideas?
|


Please define your problems and not in terms od David whites's as you are using an
enterprise/corp. version that is supported and while David is using a retail version that is
probably no longer supported.

Are you using v4.5.1 SP1 ?
 
Also having the same problem on multiple Windows 2000 machines in my
office. We are running McAfee 6.02.3000, 4.4.00 engine, various DAT
files from within the last couple of weeks. All of our Windows 2000
machines are SP4 and up to date with Windows Updates. Is this problem
widespread, I wonder? Because it seems to be affecting nearly every W2K
machine in our office...

Eric
 
| Also having the same problem on multiple Windows 2000 machines in my
| office. We are running McAfee 6.02.3000, 4.4.00 engine, various DAT
| files from within the last couple of weeks. All of our Windows 2000
| machines are SP4 and up to date with Windows Updates. Is this problem
| widespread, I wonder? Because it seems to be affecting nearly every W2K
| machine in our office...
|
| Eric

Like I said, that version of software is out-of-date and is probably no longer supported.

It actuality isn't !

http://us.mcafee.com/root/support.asp?id=retail_policy
 
Also having the same problem on multiple Windows 2000 machines in my
office. We are running McAfee 6.02.3000, 4.4.00 engine, various DAT
files from within the last couple of weeks. All of our Windows 2000
machines are SP4 and up to date with Windows Updates. Is this problem
widespread, I wonder? Because it seems to be affecting nearly every W2K
machine in our office...

Eric
Click to expand...
I've been away (honeymoon)
I run W2K and haven't had a ny problems with my McAfee at all -
but it's Enterprise 8.0i
Otherwise the same - engine and dats etc
You wouldn't think the different front end would affect things,
but there will be many different registry entries and the
Framework may work differently.
It's most likely that it's conflicting with some other software
you run, though. I have ZonealarmPro and it lives OK with that,
and the MS Spyware app is running too and that doesn't upset
it. Do you have anything interesting running all the time? What
are you using for your network connectivity?
 
From: "Dave Budd" <[email protected]>

| Ta.
| There may or may not be some pics on a webpage sometime...
| --
| "Hallo, Rabbit," he said, "is that you?"
| "Let's pretend it isn't," said Rabbit, "and see what happens."

C O O L !
 
Back
Top