spacer
Support - Platinum Support
tab end BCS Web Site divider MySupport divider Log Out navbar end
navbar end home symantec alerting service security center knowledge base navbar end
spacer
BCS Knowledge Base

spacer
spacer

Rate This Document
1x3 spacer
1x1 spacer

print this documentDocument ID:2008010303273448
Last Modified:05/05/2010

Symantec AntiVirus: "Error 1920". "The Service failed to start. Verify that you have sufficient privileges to start system services."

Situation:Why is an Error code 1920 produced during installation with Message – “Symantec AntiVirus failed to start.”

Solution:Below are three possible resolutions:
  • Either a combination of, or any one of these resolutions may work.
  • It is possible that all three Resolutions will need to be followed before the problem is corrected.
    Resolution 1
    1. Click Start
    2. Click Run.
    3. Type regedit
    4. Click OK.
    5. Navigate to the following subkeys:
      • HKEY_LOCAL_MACHINE\Software\Intel
      • HKEY_LOCAL_MACHINE\Software\Symantec
      • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion
      • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths
      • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

    6. For each of these keys, ensure that "Administrator", "Administrators" and "System" have Full Control.
    Warning: If all of the groups: "Administrator", "Administrators" and "System" have Full Control, DO NOT CHANGE ANYTHING, instead proceed to Resolution 2.



    Resolution 2
    The Trusted Publishers Properties must have "Allow the following users to Select Trusted publishers" configured to "End Users." To change this setting follow the below steps:
    1. Go to Default Domain Controller Security Settings> Software Restriction Policies> Trusted publishers
    2. Change the settings from "Enterprise Administrators" to "End Users."
      • This sets AuthenticodeFlags = 0 under the following registry locations.
        • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\TrustedPublisher\Safer\AuthenticodeFlags
        • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Safer\AuthenticodeFlags
        • HKEY_CURRENT_USER\Software\Policies\Microsoft\SystemCertificates\TrustedPublisher\Safer\AuthenticodeFlags

    3. Perform the following: gpupdate /force, to force a refresh of the Group Policy on the AD Server.

    Resolution 3
    If the CustomSD entry for the Application Eventlog has been modified, then the "Symantec Settings Manager" will not be able to read/write to that Application Eventlog.

    Please read and follow the directions in the following Microsoft document to ensure that the CustomSD entry for the Application Eventlog is set to default:
    "How to set event log security locally or by using Group Policy in Windows Server 2003" at URL: http://support.microsoft.com/kb/323076

References:"How to set event log security locally or by using Group Policy in Windows Server 2003" at URL: http://support.microsoft.com/kb/323076

print this documentDocument ID:2008010303273448
Last Modified:05/05/2010


rate this document
Does this document answer your question?
Yes
No
Maybe, need to test
None of the above
Is this document well written and easy to use?
Submit specific suggestions to improve the quality of this document.


Product(s): Endpoint Protection 11, Symantec AntiVirus 10.1, Symantec AntiVirus 10.2, Symantec AntiVirus Corporate Edition 10.0
Operating Systems(s): Windows 2000, Windows XP Home, Windows XP Professional Edition, Windows XP 64-Bit Edition 2003, Windows Server 2003 32-bit Edition, Windows Server 2003 64-bit Edition, Windows XP Media Center Edition 2005, Windows Vista 32-bit Edition, Windows Vista 64-bit Edition, Windows Vista
Date Created: 01/02/2008

  © 1995-2014 Symantec Corporation. All rights reserved. feedback | legal notices | privacy policy