| Reference Number |
Related Article |
Found
ENSM Version |
Resolved ENSM Version |
Issue Description |
| ENSM-5292 |
|
10.7.8 |
|
Issue: There's a compatibility issue with USB-C Ethernet and the System Extension framework predominantly on Apple M1 Max/Pro chipset running Monterey macOS 12.x.
NOTE: The issue is raised with Apple as it can be seen with the Sample System Extension framework. We're working closely with Apple as part of Apple defect FB9873934. |
| ENSM-5261 |
|
10.7.7 |
|
Issue: There’s a vShield Scanner crash during the upgrade of the latest Mac engine. This crash occurs only once and there's no functionality loss due to the crash. |
| ENSM-5131 |
|
10.7.8 |
|
Issue: You're unable to start the applications from the Menulet application only on M1 Monterey systems.
Workaround: You can start the application from the /Applications folder.
NOTE: The issue is identified to be an issue with Apple (FB9586412) and we’re working with Apple. |
| ENSM-4940 |
|
10.7.6 |
10.7.7 |
Issue: A Scan Engine 6300 upgrade fails with ENSM 10.7.6.
Resolution: This issue is resolved in ENSM 10.7.7. |
| ENSM-4750 |
|
10.6.x |
10.7.x |
Issue: The 5-digit V2 DAT update fails with ENSM 10.6.x.
Resolution: This issue is resolved in ENSM 10.7.x. |
| ENSM-4738 |
|
10.7.5 |
10.7.7 |
Issue: Sometimes, kernel panics occur on macOS Catalina when the system resumes from sleep with ENSM Firewall 10.7.5 or 10.7.6.
Resolution: Install or upgrade to ENSM 10.7.7, which addresses this issue only on macOS Catalina. This issue is fixed in macOS BigSur. |
| ENSM-4678 |
|
10.7.5 |
10.7.6 |
Issue: Traffic doesn't match the rule when the port number and port range are specified in the same rule in a policy.
Resolution: This issue is resolved in ENSM 10.7.6. |
| ENSM-4542 |
|
10.7.5 |
10.7.6 |
Issue: ENSM Firewall can't coexist with Cisco AnyConnect VPN and CrowdStrike Falcon network extensions.
Resolution: This issue is resolved in ENSM 10.7.6. |
| ENSM-4759 |
|
10.7.5 |
|
Issue: Changes made to the Firewall Catalog don't take effect on macOS endpoints unless you edit and save the policy.
Workaround: Edit and save the policy before you enforce the updated policy. |
ENSM-4672
ENSM-4533
ENSM-4333
ENSM-4332 |
|
10.7.0 |
10.7.6 |
Issue: The ENSM Threat Prevention on-demand scan process crashes while executing.
Resolution: This issue is resolved in ENSM 10.7.6. |
| ENSW-101862 |
KB85855 |
10.7.0 |
10.7.0 September 2020 Update
10.6.1 September 2020 Update |
Issue: When you create firewall rules within the ENSM Firewall Rules policy, under the Application section, it states (Windows only). Per KB85005 - Comparison of Endpoint Security Firewall features supported on Windows, Linux, and Macintosh, the Applications functionality for firewall rules works for the ENSM Firewall product. But, the "Mac" label is missing. Under the Firewall Rules policy menu, the correct statement would be Applications (Windows and Mac only).
Workaround: The Applications functionality within a firewall rule works for both Windows and macOS ENS clients. Create an Application, define the Executable, and specify the path/filename details of the macOS application using the Name and File Name or Path fields.
Resolution: This issue is resolved in the ENS 10.6.1/10.7.0 September 2020 Update extensions. See the related article for more information. |
ENSM-3617
ENSM-3622 |
|
10.7.0
10.6.5 |
10.7.1
10.6.10 |
Issue: A Scan Engine 6100 upgrade fails with ENSM.
Resolution: This issue is resolved in ENSM 10.6.10 and ENSM 10.7.1. |
| |
KB92592 |
10.6.5 |
10.7.5 |
Issue: Starting with macOS Catalina 10.15.4, Apple displays the notification shown below when our applications load system extensions on the macOS system. macOS systems display the message when a legacy system extension is loaded for the first time. It also periodically displays the message while the extension remains in use:
Legacy System Extension
Existing software on your system loaded a system extension signed by "McAfee, Inc." which will be incompatible with a future version of macOS. Contact the developer for support.
Resolution: ENSM 10.7.5 is the version that has transitioned away from the legacy system extensions to the new Endpoint Security APIs and network extension. For earlier versions of ENSM, click OK and close the Legacy System Extension notification. The notification doesn’t impact product functions. See the related article for more information. |
| ENSM-1503 |
|
10.6.5 |
10.6.6 |
Issue: Threat Prevention, running in Kextless mode, doesn't function correctly when upgrading from macOS 10.14 to macOS 10.15 on some systems.
Resolution: This issue is resolved in ENSM 10.6.6. |
| ENSM-1447 |
KB90888 |
10.6.5 |
|
Issue: The user interface of the following products isn't listed in the console when installing with ENSM 10.6.5.
- Data Loss Prevention 11.3.0
- Management of Native Encryption 4.1.5
- McAfee Client Proxy 2.3.6
|
| ENSM-1438 |
|
10.6.5 |
10.6.6 |
Issue: The Minimum Escalation Requirements (MER) tool isn't invoked correctly when run from the Help menu of ENSM.
Workaround: Run the MER tool from the command line as described in KB87626 - Collect Minimum Escalation Requirements for Endpoint Protection for Mac, Endpoint Security for Mac, or VirusScan for Mac.
Resolution: This issue is resolved in ENSM 10.6.6. |
| MA-7463 |
KB92888 |
10.6.2 |
McAfee Agent 5.6.2 Hotfix 1, 5.6.3 Hotfix 3, 5.6.4 Hotfix 3, 5.6.5 Hotfix 2 |
Issue: A Scan Engine upgrade fails on the system when an outdated Scan Engine is present.
Resolution: This issue is resolved in McAfee Agent 5.6.2 Hotfix 1, 5.6.3 Hotfix 3, 5.6.4 Hotfix 3, and 5.6.5 Hotfix 2. See the related article for more information. |
| 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 doesn't have user consent to load the kext. The appropriate experience matches the behavior described in KB89728 - End-user experience when installing Endpoint Security for Mac on macOS High Sierra 10.13 and later.
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 isn't valid for the renamed kext: com.McAfee.FileCore.kext.
Resolution: This behavior is as designed. The user needs to open System Preferences, Security & Privacy and click Allow for the kernel extension to load on the system. |
| ENSM-689 |
|
10.6.0 |
10.6.1 |
Issue: Wild cards are enforced and displayed in the client preferences user interface. But, wild cards aren't supported in firewall rules.
Resolution: This issue is resolved in ENSM 10.6.1. |
| ENSM-683 |
|
10.6.0 |
10.6.1 |
Issue: After you disable ENSM Web Control from ePolicy Orchestrator (ePO), the menulet shows a yellow exclamation point. This issue doesn’t occur when you disable ENSM Threat Prevention and ENSM Firewall from ePO.
Resolution: This issue is resolved in ENSM 10.6.1. |
| 1266150 |
|
10.6.0 |
|
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.6.0 |
|
Issue: The Repository List tab in the Update preferences of the local client user interface doesn't list the Repository URL of the ePO Spipe repository. |
| 1259847 |
|
10.6.0 |
DLP Endpoint 11.1.0 Hotfix 3 |
Issue: On a macOS system running ENSM, 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.6.0 |
10.6.2 |
Issue: Quarantined files that have unicode characters in their name don't display on the Quarantine screen.
Resolution: This issue is resolved in ENSM 10.6.2. |
| 1249594 |
|
10.6.0 |
As Designed |
Issue: User interface elements of 32-bit managed products don't display in the ENSM 64-bit console.
Resolution: This behavior is as designed. Upgrade the 32-bit managed products to their 64-bit variants. Only user interface elements of the managed products aren't loaded. All functional features of the products must work as expected, because 64-bit ENSM provides backward compatibility support for 32-bit managed products. |
| 1250801 |
|
10.6.0 |
As Designed |
Issue: Sometimes, the following message displays in macOS Mojave when the Minimum Escalation Requirements (MER) tool is invoked to collect MER logs:
"McAfee Endpoint Security for Mac" would like to control the application "Terminal"
Resolution: This behavior is as designed. With macOS Mojave, Apple changes the way applications try to access another application. If you see such a message, it's safe to approve the request for ENSM to control the Terminal.
|
| 1250488 |
|
10.6.0 |
As Designed |
Issue: The ENSM console displays the following error message when ENSM 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 Threat Prevention must not be uninstalled before you uninstall other 32-bit managed products from the system.
|
| 1248901 |
|
10.6.0 |
As Designed |
Issue: ENSM Threat Prevention on-access scan detection stops working after you upgrade any other ENSM module, such as Firewall or Web Control.
Resolution: This behavior is as designed. When you upgrade ENSM from a previous version of the product, upgrade all modules of ENSM on the system. |
| 1248528 |
KB92181 |
10.6.0 |
As Designed |
Issue: Installation of the standalone package of McAfee Agent through the ENSM standalone installer package (.dmg) changes the existing McAfee Agent manageability status from managed to unmanaged. This issue occurs on systems where ePO manages ENS.
Workaround: To install locally or use a third-party deployment method to deploy ENSM, follow the solution in KB92181 - McAfee Agent unmanaged after using standalone installer DMG.
Resolution: This behavior is as designed. Perform ENSM upgrades on an ePO-managed system, from ePO through a deployment task. |
| 1244716 |
|
10.6.0 |
As Designed |
Issue: Sometimes, spin dumps are logged to System Reports in macOS Mojave, for the menulet and Endpoint Security for Mac application processes.
Resolution: This behavior is as designed. |
| 1219538 |
|
10.6.0 |
As Designed |
Issue: On a macOS system running ENSM, on-demand scan policy settings don't display in the client UI.
Resolution: This behavior is as designed. |
| 1154900 |
|
10.6.0 |
As Designed |
Issue: The Endpoint Security Web Control extension for the Safari browser isn't installed on a macOS Sierra 10.12 system.
Resolution: This behavior is as designed. When you install the Endpoint Security Web Control extension, you must click Trust when prompted. |
