Console module reports as "Unknown" after upgrade

Technical Articles ID: KB92095
Last Modified: 2021-11-09 17:41:52 Etc/GMT

Environment

Endpoint Security (ENS) Threat Prevention 10.6.1 July Update Repost (and later)

Problem

After you upgrade ENS, the installation client might encounter an issue that leads to corruption in the product's XML files. As a consequence, the local ENS console might display abnormal behavior including one of the following:

One or more modules report as "Unknown."
A password prompt displays, but there’s no password policy in place.
Systems report as out of compliance in ePolicy Orchestrator (ePO) despite update tasks appearing successful.

You might observe Event ID 1000 - Application Errors in relation to common ENS executables with McAfee DLLs as the faulting modules.

You might also observe the following errors in the EndpointSecurityPlatform_Errors.log:

Failed to create container using xml/xsd!!!
Failed to load xml document, 0x00000001

Cause

During the ENS upgrade, an issue might be encountered that causes corruption of dependency XML files within ENS. This corruption can directly affect the loading of the XML files and cause dependent processes to crash.

Solution

This issue is resolved in ENS 10.6.1 December 2019 Update.

Our product software, upgrades, maintenance releases, and documentation are available on the Product Downloads site.

NOTE: You need a valid Grant Number for access. See KB56057 - How to download product updates and documentation for more information about the Product Downloads site, and alternate locations for some products.

Workaround

To restore functionality, repair the impacted modules using either of the following options.

Use the Endpoint Product Removal (EPR) tool to repair all impacted modules:
EPR can call the ENS repair functionality. For instructions to run EPR at the command line using the repair arguments, see: KB91978 - REGISTERED - Endpoint Product Removal Tool User Guide.

Run the ENS RepairCache utilities against all impacted modules:
The repair installation tools are silent, and must be run one after another. To determine whether a repair installation tool has completed, check the MSI task in Task Manager.

Open an administrator command prompt.
Execute the following commands one at a time. Allow each MSI installer to complete before proceeding to the next command. The /famus switches run a repair action while forcing the rewriting of all ENS files and registry entries to resolve any potential corruption sources.

"C:\Program Files\McAfee\Endpoint Security\Endpoint Security Platform\RepairCache\setupCC.exe" /famus

"C:\Program Files\McAfee\Endpoint Security\Threat Prevention\RepairCache\setupTP.exe" /famus

"C:\Program Files\McAfee\Endpoint Security\Adaptive Threat Protection\RepairCache\setupATP.exe" /famus

"C:\Program Files\McAfee\Endpoint Security\Firewall\RepairCache\setupFW.exe" /famus
Restart the system.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Console module reports as "Unknown" after upgrade

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

Console module reports as "Unknown" after upgrade

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title