Updated the "ENSM Threat Prevention product release information" section with ENSM 10.6.7.
October 8, 2019
Updated the "ENSM Threat Prevention product release information" section with ENSM 10.6.6. Updated issues ENSM-1438 and ENSM-1503 in the "Non-critical known issues" section as resolved in ENSM 10.6.6.
September 12, 2019
Added issue ENSM-1447 to the "Non-critical known issues" section.
September 10, 2019
Updated the "ENSM Threat Prevention product release information" section with ENSM 10.6.5. Added issue ENSM-1438 to the "Non-critical known issues" section.
August 13, 2019
Updated the "ENSM Threat Prevention product release information" section with ENSM 10.6.4.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Contents
Click to expand the section you want to view:
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, visit the Product Downloads site at http://www.mcafee.com/us/downloads/downloads.aspx.
Issue: The Minimum Escalation Requirements (MER) tool is not invoked correctly when run from the Help menu of ENSM.
Workaround: Run the MER tool from the command line as described in KB87626.
Resolution: This issue is resolved in ENSM 10.6.6.
ENSM-788
10.6.1
Issue: When a product deployment fails, two client events with ID 2412 are generated for the system.
ENSM-708
10.6.0
10.6.1
Issue: An attempt to load com.McAfee.FileCore.kext happens during an ENSM Threat Prevention upgrade even if the system does not have user consent to load the kext. The appropriate experience matches the behavior described in KB89728.
Resolution: This issue is resolved in ENSM 10.6.1.
ENSM-680
10.6.0
As Designed
Issue: The user on the macOS system must approve the FileCore extension again to load on the system. The reason is because the earlier approval for com.intelsecurity.FileCore.kext is not valid for the renamed kext: com.McAfee.FileCore.kext.
Resolution: This behavior is as designed. The user has to open System Preferences, Security & Privacy and click Allow for the McAfee kernel extension to load on the system.
1266150
10.5.9
Issue: Editing a repository name on the Update preferences Repository List tab of the local client user interface adds a duplicate entry with the new name. But, it retains the repository entry with the older name.
Workaround: Delete the older repository from the user interface.
1265479
10.5.9
Issue: The Repository List tab in the Update preferences of the local client user interface does not list the Repository URL of the ePolicy Orchestrator Spipe repository.
10.5.7
As Designed
Issue: After you upgrade to ENSM 10.5.7, the file format of quarantined items changes to ZIP. As a result, if ENSM is reverted to a version earlier than 10.5.7, the restore from quarantine feature does not work for files in the new format.
Resolution: This behavior is as designed. To restore quarantined items, manually extract the quarantined items using the "Archive Utility" application on the Mac system.
1259847
10.5.6
Data Loss Prevention Endpoint 11.1.0 Hotfix 3
Issue: On a Mac system running ENSM 10.5.6 or later, installation of Data Loss Prevention Endpoint (DLP Endpoint) 11.1.0.45 downgrades certain common components used by ENSM.
Workaround: Install DLP Endpoint 11.1.0.45 before you install ENSM.
Resolution: This issue is resolved in DLP Endpoint 11.1.0 Hotfix 3.
1254777
10.5.5
10.6.2
Issue: Quarantined files that have unicode characters in their name do not display on the Quarantine screen.
Resolution: This issue is resolved in ENSM 10.6.2.
1250488
10.5.5
As Designed
Issue: The ENSM console displays the following error message, when ENSM 10.5.5 Threat Prevention is uninstalled, and Management of Native Encryption and Data Loss Prevention are left on the system:
Your MAC is at Risk
Resolution: This behavior is as designed. Upgrade the 32-bit managed products to their 64-bit variants. ENSM 10.5.5 Threat Prevention must not be uninstalled before you uninstall other 32-bit managed products from the system.
1248901
10.5.5
As Designed
Issue: ENSM 10.5.0 Threat Prevention on-access scan detection stops working after you upgrade any other ENSM module, such as Firewall or Web Control, from 10.5.0 to 10.5.5.
Resolution: This behavior is as designed. When you upgrade to ENSM 10.5.5 from a previous version of the product, upgrade all modules of ENSM on the system.
Issue: Users see emails stuck in their outbox or slowness when they send emails using Apple Mail. This issue is experienced when ENSM Threat Prevention 10.2.3 or 10.5.0 is installed on macOS High Sierra running on an APFS partition. This issue does not occur when On-Access Scan is turned off.
Resolution: This issue is resolved in ENSM Threat Prevention 10.2.3 Hotfix 1238954 and ENSM Threat Prevention 10.5.0 Hotfix 1244068. See the related article for more information.
Issue: ENSM runs as a 32-bit application. When you start "McAfee Endpoint Security for Mac.app" for the first time on macOS High Sierra 10.13.4 and later, you see the following alert. The alert notifies you that the ENSM application is not optimized for Mac.
"McAfee Endpoint Security for Mac" is not optimized for your Mac.
Workaround: The alert appears only once. It does not impact the product functionality, so you can safely ignore the alert. For more information, see the Apple article at https://support.apple.com/en-in/HT208436.
Resolution: This issue is resolved in ENSM 10.5.5, which has native 64-bit binaries. See the related article for more information.
10.2.3
As Designed
Issue: ENSM Threat Prevention 10.2.2 can't co-exist with the ENSM 10.2.3 Firewall and Web Control modules.
Resolution: This behavior is as designed. When you upgrade to ENSM 10.2.3 from a previous version of the product, upgrade all modules of ENSM on the system.
1181639
10.2.1
10.2.2
Issue: ProductConfig.xml gets corrupted when ENSM blades are installed on an existing installation of Data Loss Prevention, File and Removable Media Protection, Management of Native Encryption, or McAfee Client Proxy.
Resolution: This issue is resolved in ENSM 10.2.2.
1177587
10.2.1
10.2.2
Issue: The Functional Module Platform daemon (fmpd) crashes after an upgrade, from McAfee Client Proxy 2.2.0 to McAfee Client Proxy 2.2.1.103, on a Mac system.
Resolution: This issue is resolved in ENSM 10.2.2.
1158287
10.2.1
Issue: You installed or upgraded to ENSM 10.2.1 on Mac OS X El Capitan 10.11.x or Mac OS X Yosemite 10.10.x. Then, after you upgraded the operating system to Mac OS X Sierra 10.12, the product does not display a notification when it detects malware.
Workaround: After you upgrade the operating system to Mac OS X Sierra 10.12, restart the Mac system.
1144747
10.1.0
10.2.0
Issue: Installation of ENSM 10.1 after Data Loss Prevention (DLP) Endpoint for Mac 10.0 has been installed, causes both ENSM and DLP Endpoint for Mac to stop working.
Workaround: To run both applications, install ENSM 10.1 first, and then DLP Endpoint for Mac 10.0.
Resolution: This issue is resolved in ENSM 10.2.0.
1077269
10.0.0
10.2.2
Issue: Incorrect self-protection violation events are generated for Threat Prevention and Web Control locations after product deployment.
Workaround: If the processes that are stopped during deployment are Mkdir, CP, or WebKitPluginHost, you can safely ignore the events. The event ID is 1092.
Resolution: This issue is resolved in ENSM 10.2.2.
If you are a registered user, type your User Id and Password, and then click Log In.
If you are not a registered user, click Register and complete the required fields. Your password and logon instructions will be emailed to you.
NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision.
