'Failed to launch self-updater child process! Error code = 3' shown in the Sophos Update Manager trace log

  • Article ID: 113857
  • Rating:
  • 1 customers rated this article 1.0 out of 6
  • Updated: 28 Aug 2015

Issue

The following error is shown in one of the Sophos Update Manager (SUM) SUMTraceLog files:

[TIMESTAMP] : EventLog: 3758112805 1 Inserts:> "Payload-SDDM" "22.5" "Failed to launch self-updater child process! Error code = 3"
[TIMESTAMP] : Cmd-ALL << [E4025][Payload-SDDM][22.5][Failed to launch self-updater child process! Error code = 3] Failed to self-update from payload 'Payload-SDDM', version 22.5. Details: Failed to launch self-updater child process! Error code = 3
[TIMESTAMP] : Cmd-ALL << [E400D][ActionSelfUpdate-SDDM][DispatcherPrograms-[DATE]T[TIME]] Action 'ActionSelfUpdate-SDDM' with caller 'DispatcherPrograms-[DATE]T[TIME]' failed!

The Windows event log also shows:

The description for Event ID ( 16421 ) in Source ( SophosUpdateManager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Payload-SDDM, 22.5, Failed to launch self-updater child process! Error code = 3.

The description for Event ID ( 16422 ) in Source ( SophosUpdateManager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Payload-SDDM, 22.5, 1603.

First seen in
Sophos Update Manager 1.0.3

Cause

The SUM.msi file is trying to run as part of the self-updating mechanism of the Update Manager and encountering a lot of collisions in the Windows temporary folder.

What To Do

  1. In Windows Explorer browse to: C:\Windows\Temp\
  2. Delete the temporary installer files listed in this folder.

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments