| Reference Number |
Related Article |
Found in
Version |
Resolved in Version |
Issue Description |
| EC-12375 / MA-15306 |
|
2305 |
TA 5.8.1 |
Issue: When you launch Adobe Acrobat, the following error message occurs:
The procedure entry point sqlite3_sourceid could not be located in the dynamic link library C:\Program Files\McAfee\Agent\ma_database.dll
Workaround:
- Click OK on the error prompt. This results in the script scanning not working for Acrobat.exe.
- Disabling Enable Script Scanning prevents the issue from occurring; however, this results in the script scanning being disabled system-wide, which isn't recommended.
Resolution: The issue has been resolved in TA 5.8.1. |
| EC-12260 |
KB96563 |
2210 |
ePO-SaaS |
Issue: In ePO - SaaS, MVISION Endpoint might inadvertently be uninstalled and replaced with Endpoint Security under the System Tree, Deploy tab.
Resolution: The issue is now resolved in the ePO-SaaS environment. |
| N/A |
N/A |
2007 |
|
Issue: When you attempt to migrate from Endpoint Security (ENS) to Trellix Endpoint, uninstallation of ENS is unsuccessful and the migration fails.
Workaround: Restart the endpoint and run the migration task again. |
| N/A |
N/A |
2210 |
|
Issue: The MVISION Endpoint product name has been renamed to Trellix Endpoint. Features and options in Trellix Endpoint, prefixed with the product name, will be updated iteratively. The ePO Software Catalog lists Trellix Endpoint as MVISION Endpoint.
NOTE: The name variation doesn't impact the product functionality and performance; you can manage and operate the product as usual. |
| EC-11572 |
KB96049 |
2202 and earlier |
2210 |
Issue: When you install or upgrade to Trellix Endpoint 2210, you might be required to reboot the endpoint. On some installs and upgrades, Trellix Endpoint 2210 installation doesn't proceed until the Endpoint is rebooted and the installation or upgrade is restarted.
Workaround: Reboot the endpoint if required and restart the installation or upgrade. |
| EC-4959 |
N/A |
2104 and earlier |
2107 |
Issue: If you don't upgrade MVISION Endpoint to 2107 or later by Q4 2021 in on-premises environments, the automatic updates won't be functional. This issue is due to the change in the architecture of the MVISION Endpoint ePO extensions involved. Manual effort is needed to adopt a new version post Q3 2021.
Workaround: Upgrade to the latest MVISION Endpoint extensions in on-premises ePO and Endpoint to avoid any automatic update-related issues. |
| EC-10385 |
N/A |
2107 |
2202 |
Issue: An MVISION Endpoint auto-update task in on-premises ePO has issues retaining the modifications made to its properties (such as task name, task description, and auto update frequency) after upgrading the MVISION Endpoint extensions. The property setting "Disabled" will be retained, so the value remains as it was before the upgrade, meaning no unintentional updates are initiated post upgrade.
Workaround: After the upgrade, set the task properties that aren't retained to desirable values.
Resolution: This issue is resolved in MVISION Endpoint 2202 and later. |
| EC-8914 |
N/A |
2009 |
2102 |
Issue: The following properties were added in MVISION Endpoint 2009 and later:
- Microsoft Cryptographic Services Status
- Group Policy Enforcement Status
The values of these properties incorrectly show as empty in the following places in ePO:
- In the System Tree, if you add the properties as columns in the Systems table.
- In Queries & Reports, query results showing the properties return empty values. An attempt to filter query results based on the values of the properties yields no results.
Workaround: You can view the values of the properties in the System Tree. After you select a system, navigate to the Products tab and then select MVISION Endpoint to view the values of the properties.
Resolution: This issue is resolved in MVISION Endpoint 2102 and later.
|
| EC-7561 |
N/A |
2007 |
|
Issue: ENS remnants are visible in ePO after you uninstall ENS as part of the ENS to MVISION Endpoint migration feature. In this case, ENS is uninstalled and MVISION Endpoint is installed and functional on the endpoint.
Workaround: Restart the endpoint. You can expect the issue to be resolved and no more ENS references are shown in ePO. |
| TSDE-3753 |
KB92637 |
2004 |
|
Issue: MVISION Endpoint might not work properly when migrating from the existing product ENS or VirusScan Enterprise on Windows Server 2016/2019. This problem isn't always reproducible, but when the problem occurs, you might see the following symptoms:
- The message Not installed displays in Windows Defender in the Server Manager.
- The EICAR file isn't detected.
Workaround: See the related article for migration steps and for more information.
|
| EC-6217 |
N/A |
2004 |
2006 |
Issue: Microsoft Windows Defender Attack Surface Reduction (ASR) technology can sometimes detect good processes as malicious behavior.
Workaround: If this scenario occurs, add an exclusion for such processes to ASR to allow the processes.
Resolution: This issue is resolved in MVISION Endpoint 2006 and later. |
| EC-6585 |
KB92453 |
2002 |
2004 |
Issue: Network card initialization is delayed. This issue causes short-term network connectivity issues such as the following:
- Lack of network connectivity
- Disconnected mapped drives
- Failure of any third parties that rely on the presence of a running network interface card, such as a VPN software suite
Workaround: The NDIS driver can be disabled to alleviate the symptoms.
Resolution: This issue is resolved in MVISION Endpoint 2004 and later. See the related article for more information.
|
| EC-5895 |
N/A |
1912 |
2004 |
Issue: There are intermittent crashes with Microsoft Office applications, for example, Autocad.
Resolution: This issue is resolved in MVISION Endpoint 2004 and later. |
| EC-5489 |
N/A |
1912 |
2002 |
Issue: Some Endpoints might go out of compliance in ePO after an MVISION Endpoint 1912 update. On some systems, a registry key remains after the previous version MSI uninstaller has completed. Presence of this key prevents MVISION Endpoint 1912 from updating on the first attempt. A redeployment of MVISION Endpoint 1912 succeeds.
Any system that encounters this issue retains the MVISION Endpoint ePO policy settings for Microsoft Native Security. For example, Microsoft Windows Defender, Microsoft Windows Defender Exploit Guard, and Microsoft Windows Firewall.
Workaround: Perform an ePO-redeployment task of MVISION Endpoint 1912 to the affected systems. These systems self-correct with the next automatic update of MVISION Endpoint.
Resolution: This issue is resolved in MVISION Endpoint 2002 and later. |
| EC-5524 |
N/A |
1912 |
2002 |
Issue: BitLocker compliance isn't displayed on the protection workspace in MVISION ePO.
Workaround: Compliance is available. You can see compliance in the Systems Information page after a query.
Resolution: This issue is resolved in MVISION Endpoint 2002 and later. |
| SEC-18197 |
N/A |
1912 |
|
Issue: The VSCore installation fails because the MVISION EDR service doesn't respond during the upgrade.
Workaround: Reboot and redeploy the MVISION Endpoint service. |
| EC-4701 |
N/A |
1904 |
1909 |
Issue: Unexpected behavior is observed when the Windows Firewall log size is set to greater than 32 MB.
Resolution: This issue is resolved in MVISION Endpoint 1909 and later. |
| EC-4863 |
N/A |
1909 |
1912 |
Issue: The "Delete" option remains active even after the user cancels a record in Standard Exploit Protection Program Settings.
Resolution: This issue is resolved in MVISION Endpoint 1912 and later. |
| EC-4717 |
N/A |
1909 |
2305 |
Issue: A ZIP file that contains a large number (about 2500) of Python files takes a long time to extract when using Windows native extraction.
Workaround: Scan the ZIP file with Windows Defender before you extract with 7-Zip or other third-party extraction tools.
Resolution: Fixed in 2305. |
| EC-4442 |
N/A |
1903 |
1909 |
Issue: MVISION Endpoint fails to install on Windows Server 2016 when the Windows Server is set up as a domain controller.
Resolution: This issue is resolved in MVISION Endpoint 1909 and later. |
| EC-4112 |
N/A |
1904 |
2102 |
Issue: Windows 10 May 2019 Update Tamper Protection blocks MVISION Endpoint from managing some Windows Defender settings.
Workaround: To fully manage all Windows Defender settings, disable Tamper Protection at the endpoint.
Resolution: This issue is resolved in MVISION Endpoint 2102 and later. |
| EC-4109 |
N/A |
1904 |
1906 |
Issue: File and folder exclusions that contain wildcards aren't supported.
Resolution: This issue is resolved in MVISION Endpoint 1906 and later. |
| EC-4100 |
N/A |
1904 |
1906 |
Issue: An MVISION Endpoint policy enforcement alert isn't shown for MVISION ePO.
Resolution: This issue is resolved in MVISION Endpoint 1906 and later. |
| 1268032 |
N/A |
1903
(ePO 5.10 issue) |
1906 |
Issue: You can't upgrade the MVISION Endpoint ePO Extension Bundle using a manual check-in through ePO 5.10 when the ePO language is set to French, Spanish, or Japanese. This issue occurs because of an issue with ePO 5.10.
Resolution: This issue is resolved in MVISION Endpoint 1906 and later. |
| EC-3809 |
N/A |
1903 |
1904 |
Issue: If you push more than one Firewall Rules policy that contains duplicate Firewall Rules to the same endpoint, the Compliance of the Firewall is incorrect.
Resolution: This issue is resolved in MVISION Endpoint 1904 and later. |
| 1258105 |
N/A |
1811 Update 1 |
1903 |
Issue: Credential Theft Protection reports a detection on the Microsoft Windows process taskhostw.exe.
Resolution: This issue is resolved in MVISION Endpoint 1903 and later. |
| 1257877 |
N/A |
1811 |
As Designed |
Issue: When you disable Threat Protection, some enhanced protection and remediation features remain active until the endpoint restarts. |
| EC-1388 |
N/A |
1808 |
As Designed |
Issue: If you enable Credential Theft Protection in Scan Settings, a system restart is needed. |
| 1247117 |
N/A |
1808 |
As Designed |
Issue: If VirusScan Enterprise, SiteAdvisor Enterprise, and Host Intrusion Prevention (Host IPS) are removed from an endpoint during the MVISION Endpoint installation, Host IPS Firewall shows as snoozed until after the next restart. This issue occurs because some files and folders can't be removed. Also, some drivers can't be unloaded until a restart occurs.
Resolution: This issue isn't expected to be resolved. |
| 1244797 |
N/A |
1808 |
1903 |
Issue: MVISION Endpoint doesn't support the remediation of threats on Microsoft Windows network shares.
Resolution: This issue is resolved in MVISION Endpoint 1903 and later. |
