Endpoints fail to update after adding XML configuration or custom files to the update location (CID) Authentication failed error 00000067

  • N.º del artículo: 118821
  • Calificación:
  • 7 clientes puntuaron este artículo con un 1.9 sobre 6 de media.
  • Actualizado: 15 may 2014


00000067 is a generic error code returned when a component or sub-component has failed to install. If this article does not deal with the issues you are seeing, refer to article 113312 for more general troubleshooting steps on this error.


Endpoints that have upgraded to the 10.2.4 package version (Sophos Auto Update version 2.9.0) fail to update following the addition of XML configuration and/or custom files to the CID using the ConfigCID.exe tool. 

The Sophos Console will show the following error:

Failed to install SAVXP: Package authentication failed with corresponding code 00000067

Note: The error will be reported against the component that failed to update.

The Auto Update log will show the following error:

Manifest failure for product [product name]

The Sophos Auto Update trace log shows the following error:

CheckCustomManifest: invalid package:invalid custom manifest: [BADFILE]: 3: 'C:\Program Files\Sophos\AutoUpdate\cache\savxp\cmanifest.dat'

Note: The package affected will vary depending on where the fixed configuration and/or custom files have been added, in this example it's the Sophos Anti-Virus folder 'savxp'.

First seen in
Sophos Anti-Virus for Windows 2000+ 10.2


Sophos Auto Update version 2.9.0 (and later) now performs a check that all files added to an update location are signed and included in the manifest. XML configuration and custom files must be added to the CID with version of ConfigCID.exe or later, supplied with Sophos Update Manager 1.4.2 and later.

What To Do

Use the latest version of ConfigCID.exe (version and above) to add custom files to a CID.

How to check the version you are using

Check you are using ConfigCID.exe version and later:

  1. Right click on the ConfigCID.exe file in use, select properties.
  2. On the Details tab, check the File version field.
  3. If the version is below (Released around January 11th 2013), ensure you locate and use the latest version as described here (Under 'Locating the utility').

Si necesita más ayuda, póngase en contacto con soporte técnico.

Valore el artículo

Muy malo Excelente