Showing results for 
Show  only  | Search instead for 
Did you mean: 

Update failed to version Engine: 5301.4018 DAT: 5586.0000


i use VirusScan Enterprise 8.5.0i, for years

Scanmodul-Version (Engine) 5300.2777, since september 2008

DAT-Version 5585.000, manual installation from today

on WindowsXP pro SP2 - newest updates (no XP3)

now i got the following AutoUpdate message:

"Update failed to version Engine: 5301.4018 DAT: 5585.0000"

after succesfull manual sdat5585.exe installation during today
i got the AutoUpdate message this evening

"Update failed to version Engine: 5301.4018 DAT: 5586.0000"

i cant get the newes Scan-Engine 5301.4018

also not, if i try the manuel way with the sdat5585.exe

can you help, can i get the 5301eng.exe?

and VsTskMgr.exe + Mcshield.exe are running wild for some time,
with 99% CPU usage for minutes, like never before...

grettings from Hamburg

Oliver A. Glasow
2 Replies
Level 7
Report Inappropriate Content
Message 2 of 3

RE: Update failed to version Engine: 5301.4018 DAT: 5586.0000


we also experienced HEAVY CPU LOADS while updating to this new engine with VSE 8.5i and Windows XP. We had to reinstall the virusscanner on several machines.

RE: Update failed to version Engine: 5301.4018 DAT: 5586.0000

I have exactly the same problem. About a 1/3rd of our servers are failing to update to the latest engine version.

The McScript.log shows :-

Copying Engine
Update failed to version Engine: 5301.4018 DAT: 5586.0000.

All other logfiles point to this script entry.

There are no engine updates available from McAfee's website for this version (unless you use ePo, which we don't) and the latest SDAT doesn't include this engine version either.

Incidentally, a workaround to just get the latest DAT version installed is to disable the 'Get newer detection engine and dats if available' option in the AutoUpdate Properties. This works for the current DAT versions, but who's to say how long this will work for, and the engine is still going to be out of date!

Update :-

In my case, it turns out that the clients weren't at the latest patch level. Updating to patch 8 seems to have fixed this on at least one of my servers. I'll be checking others shortly.

Also, I've found a master KB article (KB60795) with links to other KB articles describing how to manually update to 5301 using the ePO update :-

And for those of you out there with v8.0 clients, it won't install full stop! (KB59951) :-

There's more info on engine 5301 here (KB51132) :-

Hope these help 🙂

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community