Messaging Gateway virus definition update failing with error 80840001 (Component update failure only starting 08/25/2026)

Products

• Messaging Gateway

Issue/Introduction

Starting on August 25th, 2026, the Messaging Gateway LiveUpdate process may report an error indicating that a component has failed to update. Despite this error, the Messaging Gateway continues to download and apply malware/virus definitions successfully. The error looks similar to the following:

2026-08-28T08:20:19-03:00 (ERROR:3707.563828288): [42120] SG Decomposer: LiveUpdate LUX error (80840001).
2026-08-28T08:20:19-03:00 (ERROR:3707.563828288): [42115] SG Decomposer: Error during LiveUpdate.
2026-08-28T08:20:36-03:00 (ERROR:3707.563828288): [42120] SG Decomposer: LiveUpdate LUX error (80840001).
2026-08-28T08:20:36-03:00 (ERROR:3707.563828288): [42115] SG Decomposer: Error during LiveUpdate.
2026-08-28T08:20:36-03:00 (ERROR:3707.563828288): [42120] SG Decomposer: LiveUpdate LUX error (80840001).
2026-08-28T08:20:36-03:00 (ERROR:3707.563828288): [42149] SG Decomposer: Second virus definition update attempt failed with error code (80840001); first attempt failed with error code (80840001).  Continuing to use existing definitions.

Symptoms

• LiveUpdate logs may display error codes related to component-specific download or installation failures.
• However, the dashboard and Status > Hosts > Software and Services will confirm that Virus Definitions are current.

Environment

Messaging Gateway all versions

Cause

The error is related to the update process of a system component and does not directly impact malware definitions.

Resolution

Impact

This issue is non-impactful to the primary functionality of the Messaging Gateway.

• Virus/Malware Definitions: Updates continue to download and apply as expected.
• Scanning Processes: The Brightmail Engine and MTA scanning services remain operational and are unaffected by this LiveUpdate component failure.

Resolution / Workaround

This issue was resolved by the malware definition team on September 3rd. The resolution is distributed as part of the LiveUpdate process, no manual action is needed.