A local upgrade of the McAfee Agent fails when called from PowerShell
Last Modified: 2021-10-05 16:25:28 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
A local upgrade of the McAfee Agent fails when called from PowerShell
Technical Articles ID:
KB94946
Last Modified: 2021-10-05 16:25:28 Etc/GMT Environment
McAfee Agent (MA) 5.x McAfee Endpoint Security (ENS) 10.6.x and later Microsoft Windows PowerShell Problem 1
A McAfee Agent upgrade fails when you try to upgrade to a later version while invoking the local install from a Windows PowerShell. NOTE: Silent installs also fail. You see this issue on systems that have either or both of the following products installed:
NOTE: The Frame Package name can be different, and depends on the naming convention in the environment. The McAfee Agent displays the error message below: Administrator: Windows PowerShell Cancel Retry Ignore Problem 2
You see the errors below recorded in the MSI (s) (A0:C8) [10:12:31:774]: 7 application(s) had been reported to have files in use. Info 1603.The file C:\Program Files\McAfee\Agent\ssleay32.dll is being held in use by the following process: Name: masvc, ID: 8700, Window Title: (not determined yet). Close that application and retry. Cause
The AMSI framework The data collected through Workaround
Disable the policy option and deploy the McAfee Agent from ePolicy Orchestrator (ePO):
Affected ProductsLanguages:This article is available in the following languages: |
|