Video Screencast Help

Symantec Antivirus virus definition could not update

Created: 25 Nov 2012 • Updated: 26 Nov 2012 | 12 comments

Recently, my client windows 98 pc which installed managed symantec antivirus, the virus definition stop receive update.


-- The Symantec System Center version is

-- The Parent Server version is 

-- The Symantec Antivirus Client mapped by the parent server

Tried method:

1. Tick the "allow this server to manage 9.x and earlier clients....." option on symantec system console(no solve problem)

2. Click the "LIVEUPDATE" button on client pc and run the whole downloading with installing process successfull,but the virus definition still no update(no solve problem)

3. Install an unmanage symantec antivirus 9.0 on win98 pc also cannot update the virus definition.(no solve problem)

Can anybody help me?

Comments 12 CommentsJump to latest comment

pete_4u2002's picture


however you can manually download the definition file from Symantec and try updating the client machine.

SSun's picture

Hello, Pete_4u2002. Thank for your reply.

    Your mean is download the Intelligent Updater file manually and update the client machine?

If yes, Intelligent Updater is totally no respone in my client machine.

SSun's picture

After install the xbd file and restart my client machine. The CPU has run something, but SAV still no change the definition date at the endsad.

SSun's picture

"vd3af206.xdb" can copy to Windows 98 client machine directly?

SSun's picture

After apply "vd3af206.xdb" to C:\Program Files\Symantec Antivirus\, still no update. 

Ashish-Sharma's picture

To copy an .xdb file to a Symantec AntiVirus server

  • Copy the .xdb file to the Symantec AntiVirus program folder.
    • For NetWare servers, the default location is SYS:SAV.
    • For antivirus servers on Windows computers, the default is C:\Program Files\SAV\ for Symantec AntiVirus 8.x, or C:\Program Files\Symantec AntiVirus for Symantec AntiVirus 9.x.

The location of the folder can vary if you upgraded from a previous version.
For help with this, see the "To find the Symantec AntiVirus program folder" section in the Technical Information section of this document.

To copy an .xdb file to a Symantec AntiVirus client

  • Copy the .xdb file to the correct folder, depending on the program version:
    • For clients that run Windows 2003/XP/2000, the default folder is one of the following:
      • C:\Documents and Settings\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\
      • C:\Documents and Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate Edition\7.5\

        The Application Data folder may be hidden. To show hidden and system folders, read the document How to make Windows show all files.

    • For clients that run Windows 98/Me, the following is the default folder:
      C:\Program Files\Symantec_Client_Security\Symantec AntiVirus\ or C:\Program Files\Symantec AntiVirus\
    • For clients that run Windows NT 4.0, the following is the default folder:
      C:\WinNT\Profiles\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\

Check this thread

Thanks In Advance

Ashish Sharma

pete_4u2002's picture

if you still want to be running SAV 9, i can suggest reinstall the client.

ideally xdb folder should be processed and this file should disappear.

sandra.g's picture

Modern virus definition sets are far too much for SAV 9.0 to handle (the XDB is about 222MB, which is not actually listed as supporting SAV 9.0):

Supports the following versions of Symantec antivirus software:

  • Symantec AntiVirus 10.0 Corporate Edition Server
  • Symantec AntiVirus 10.1 Corporate Edition Server
  • Symantec AntiVirus 10.2 Corporate Edition Server

I can understand wanting to help your client, but to be honest, they have been very fortunate that this has worked as long as it has in a totally unsupported state. I can't remember exactly when support for SAV 9.0 definitions ended, but as best as I can determine, the product version they have (9.0, no MRs) was end-of-lifed in 2005.

In short, I'm not sure there is a fix for this particular issue, so you may need to prepare them for that eventuality. sad


Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!