Symantec endpoint protection 11 updates not updating

24 Oct

More specifically the last certified definitions that was published on December 31, 2009 was “12/31/2009 rev. The next certified definitions to be published will have a revision number greater than 041.As of Thursday January 7, 2010; the Symantec Endpoint Protection Antivirus definition version "12/31/2009 rev. Rev 119 includes all of the latest definition updates through January 7, 2010.Below is an excerpt from the Symantec Antivirus knowledgebase, Symantec antivirus, although it updates the same as before, doesn't recognize a date newer than 2009.The fix: release new definition updates, but keep the December 31, 2009 date.

Preparing to unpack .../bash-completion_1:2.1-4ubuntu0.2_... Unpacking bash-completion (1:2.1-4ubuntu0.2) over (1:2.1-4ubuntu0.1) .. (You can experiment by copying or perhaps windows-hard-linking to some other folder where Explorer doesn't play games with [email protected]:~$ sudo apt-get update [sudo] password for cheshkin: Get:1 In Release [65.9 k B] Get:2 amd64 Packages [517 k B] Get:3 amd64 Packages [13.0 k B] Get:4 amd64 Packages [133 k B] Get:5 amd64 Packages [4,990 B] Get:6 Translation-en [284 k B] Get:7 Translation-en [2,570 B] Get:8 Translation-en [3,206 B] Get:9 Translation-en [78.7 k B] Ign In Release Ign In Release Err Cannot initiate the connection to archive.ubuntu.com:80 (20c:1501::14).- connect (113: No route to host) [IP: 20c:1501::14 80] 100% [Connecting to archive.(91.1)] For completeness, if the AV is confirmed to not be the cause, one might want to confirm that the firewall in use in Windows allows the WSL environment to communicate outbound on the network. You might want to be helpful to others by listing the specific firewall/AV you had to turn off, so if they search here they can find a reference.If the settings for functionality such as alerts or notifications have been altered from the default values, it is possible that your experiences may vary from those below.Managed Clients: An issue has been identified in the Symantec Endpoint Protection Manager (SEPM) which causes Security Content newer than 12/31/2009 PM to be considered older than content previous to that date/time.