The following McAfee Client Proxy (MCP) versions cannot be upgraded on systems where DE has been installed in FIPS mode with McAfee Agent 4.8.x:

• MCP 2.1.1.106 (from ePO)
• MCP 2.1.3.105 (locally)

NOTE: Both of the above MCP versions have reached EOL (March 15, 2018).

The installation logs show that the McAfee Hive registry keys cannot be changed.

The following error is reported when trying to manually edit the McAfee Hive registry keys:
 

Upgrades from McAfee Agent 4.8.x to 5.x fail on systems where DE has been installed in FIPS mode with McAfee Agent 4.8.x.

NOTE: MA 4.8.x has reached EOL (March 15, 2018).

One of the following types of failure is seen with MA:

• One failure mentions a volatile key.
• A second failure type involves the inability to write to the key and displays the following error:

Scenario 1:

• MA fails to upgrade, and then fails to successfully roll back when the installer tries to delete the key in question and cannot.
• McAfee Agent is left in a broken state.

Scenario 2:

• Agent fails to upgrade, but does roll back. But, the DE Agent is no longer recognized. 
• The following DE Agent registry key does exist:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Network Associates\ePolicy Orchestrator\Application Plugins\EEADMIN_1000
  Name Type Data
  Enforce Flag DWORD 00000003(3)

In addition, the EEADMIN1000 datastore.bin and the properties files are removed and replaced by: