Unpredictable results can occur when inconsistent versions of Endpoint Security modules coexist on the same endpoint

Technical Articles ID: KB95340
Last Modified: 2022-04-06 18:05:45 Etc/GMT

Environment

Endpoint Security (ENS) Threat Prevention 10.x

Summary

Mixing of modules from different ENS releases on the same endpoint isn't supported. For example, ENS 10.7.0 February 2022 Update has the following build numbers:

Threat Prevention Client is build number 10.7.0.3299.
Common Client is build number 10.7.0.3255.

Use of ENS modules on the same endpoint from release versions other than February 2022 Update can result in unexpected behavior. For example, if Adaptive Threat Protection (ATP) Client 10.7.0.3183 from September 2021 is installed rather than the correct February 2022 10.7.0.3437 version, unexpected results might occur.

For ENS versioning details, see KB82761 - Supported platforms for Endpoint Security.

Problem

Use of ENS modules on the same endpoint from different release versions can result in unexpected behavior. Here's an example of an issue that can occur when mismatched ENS modules are present together.

Scenario: A user previously updated Common Client, but ATP wasn't updated to the same release. Occasionally, during subsequent updates a crash occurs in mfeatp.exe. This issue is due to an incompatibility between the old and new versions with this unsupported combination.

The Windows Error Reporting reports the following:

Faulting application name: mfeatp.exe, version: 10.6.1.1473, time stamp: 0x5d81248b Faulting module name: ReputationCommunicator.dll, version: 21.12.0.83, time stamp: 0x619e1f74 Exception code: 0xc0000409 Fault offset: 0x000929e6 Faulting process id: 0x2fa0 Faulting application start time: 0x01d80bca756c9ce4 Faulting application path: C:\Program Files\McAfee\Endpoint Security\Adaptive Threat Protection\mfeatp.exe Faulting module path: C:\Program Files\McAfee\Endpoint Security\Endpoint Security Platform\ReputationCommunicator.dll Report Id: 0743c1d0-be7a-47d5-9d8d-cec79984a247 Faulting package full name: Faulting package-relative application ID:

Cause

There's an incompatibility between the old and new versions because the release versions are inconsistent.

Solution

Make sure versions of ENS modules on the same endpoint are consistent for the release in use. ePolicy Orchestrator provides details about what versions of each of the individual modules are in use.

If a crash occurs during an update, continue with the update until it succeeds for all components.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Unpredictable results can occur when inconsistent versions of Endpoint Security modules coexist on the same endpoint

Environment

Summary

Problem

Cause

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

Unpredictable results can occur when inconsistent versions of Endpoint Security modules coexist on the same endpoint

Environment

Summary

Problem

Cause

Solution

Affected Products

Languages:

Choose your region

Title

Title