| Release Notes | Version | General Availability |
| Release Notes | 4.12.2 | April 14, 2021 |
| 4.12 | November 17, 2020 | |
| Release Notes | 4.10.2 | September 23, 2020 |
| 4.10.0 | June 18, 2020 | |
| Release Notes | 4.8.2 | March 10, 2020 |
| 4.8 | November 12, 2019 | |
| Release Notes | 4.6.2 | March 12, 2019 |
| Release Notes | 4.6 | November 13, 2018 |
| Release Notes | 4.4.2 | July 10, 2018 |
| Release Notes | 4.4.0 | May 8, 2018 |
| Release Notes | 4.2.2 | February 21, 2018 |
| Release Notes | 4.2 | November 29, 2017 |
| Release Notes | 4.0.6 | February 21, 2018 |
| Release Notes | 4.0.4 | September 6, 2017 |
| Release Notes | 4.0 | June 26, 2017 |
Advanced Threat Defense 4.x Known Issues
Technical Articles ID:
KB89507
Last Modified: 4/16/2021
Last Modified: 4/16/2021
Environment
McAfee Advanced Threat Defense (ATD) 4.x
Summary
Recent updates to this article
| Date | Update |
| April 16, 2021 | Added 4.12.2. |
| March 26, 2021 | Added the fixed in version for ATD-9285. |
| November 18, 2020 | Added ATD-9285 to the "Non-critical known issues" section. Added 4.12 release information. |
| October 16, 2020 | Added ATD-4416 to the "Non-critical known issues" section. |
| October 9, 2020 | Added TSNS-10338 to TSNS-10190 to Critical issues. |
Para recibir una notificación por correo electrónico cuando se actualice este artículo, haga clic en Suscribirse en la parte derecha de la página. Para suscribirse debe haber iniciado sesión.
Contents
Click to expand the section you want to view:
Las soluciones de problemas en actualizaciones y grandes lanzamientos son acumulativas; Soporte técnico le recomienda que instale la última versión. Para encontrar la versión más reciente de su producto, visite el sitio web de descargas de productos en http://www.mcafee.com/us/downloads/downloads.aspx.
| Reference Number | Found in Version | Fixed in Version | Related Article | Issue Description |
| TSNS-10190 TSNS-10338 |
4.10.0 | Issue: ATD fails to create VM profiles of the Windows 10 1909 where the build number is, for example:
18363.1016
18363.900 Cause: McAfee validated Windows 10 1909 build 18363.418 through 18363.778 as supported in ATD 4.10. The maximum supported build for Windows 10 1909 is 18363.778. The recent Windows 10 1909 builds, such as 18363.900 and 18363.1016, have additions that are not yet supported by ATD. If you try to create a VM profile of Windows 10 1909 with one of those unsupported builds, it fails. Workaround: Use Windows 10 1909 with a build number between 18363.418 and 18363.778 inclusive, for your VM profile. |
||
| ATD-4191 | 4.8 | 4.10 | KB93050 | Issue: Advanced Threat Defense does not show reports for last x Minutes, x Hours, or x Days. Solution: See the Related Article. |
| 4.x | N/A | Issue: If an application error occurs during sandbox analysis, the sample does not run correctly and you do not get the expected verdict. An example application error is that Acrobat Reader crashes. Examples of why the error occurs is improper installation, missing application dependencies, or security hardening setting. Solution:
|
||
| ATD-4167 | 4.8 | N/A | KB92804 | Issue: Adobe Acrobat Reader crashes during sandbox a scan, which causes false malicious conviction for all PDF samples. Solution: Update or upgrade Adobe Acrobat Reader in your VM. See the related article the details. |
| ATD-3677 | 4.8.0 | 4.8.2 | Issue: You can't apply the 4.8.0.17 Detection package to ATD through the manager manually (Manage, Image & Software, Content Update, Detection Solution: ATD 4.8.2 resolves this issue. Workaround: Use the Auto Upload option or perform the upgrade using the CLI: From the ATD Manager:
Para obtener documentos de productos de McAfee, vaya al portal Documentación de producto empresarial en https://docs.mcafee.com.
|
|
| ATD-3553 | 4.8.0 | 4.8.0 repost | KB92234 | Issue: Migration from ATD 4.6.x to ATD 4.8.0 fails, and the process hangs (stops responding). Cause: During the migration to 4.6.0, you used the system msu, instead of the ATD 4.6.0 migration msu. Solution: See the related article. |
| ATD-3637 | 4.8.0 | 4.8.2 | Issue: ATD manager does not list previous examples of the locally saved backup. Cause: API for the list of previous backup files returns malformed output. Solution: ATD 4.8.2 resolves this issue. Workaround: Technical Support can address the API over a remote session. To apply this fix using a remote session, contact Technical Support. |
|
| ATD-2128 | 4.x | Issue: Microsoft Office 2010 loses activation on Microsoft Windows 10 VM after you create a VM profile. Microsoft Windows 10 sandbox VM scans a sample. Microsoft Office 2010 displays the Microsoft Office Activation wizard, and requires activation. But, you successfully activated Office in the Activate screen of the ATD manager, and you have correctly created the VM profile. Cause: The Office Software Protection Platform Service intervenes on your Office license while ATD creates VM profile and sandbox snapshots. As a result, the Office Software Protection Platform Service has Solution: McAfee does not recommend the combination of Windows 10 and Office 2010 as a VM. The Office 2010 license is repeatedly lost and you are repeatedly prompted to activate Office. IMPORTANT: This recommendation is based on the Microsoft issue, documented here. |
||
| ATD-2110 | 4.6, 4.8 | KB92074 | Issue: Many email reports show attachments as unverified severity, and overall email verdict as Cause: Currently, the ATD Email Connector supports only one mail per SMTP session. When you configure more than one mail per session, it might result in mails being timed out. Workaround: Configure your sender MTA as shown below for delivering emails to the ATD Email Connector:
|
|
| TSNS-7587 | 4.x | N/A | KB91774 | Issue: ATD Email Connector intermittently fails to forward email to a relay host that is specified using a dynamic DNS host name. Solution: Either stop using dynamic DNS, or add dummy relay host rules. See the related article for more information. |
| 1269878 | 4.6 | 4.8 | Issue: Incorrect documentation in the "Prerequisites and considerations" section in Chapter 7 of the ATD product guide. The first bullet in the "Prerequisites and considerations" section was incorrect.
Original description:
You must use the eth-0 interfaces (management ports) of the Advanced Threat Defense Appliances for cluster communication. Also, for best performance, the eth-0 interfaces of all nodes must be in the same layer-2 network of the OSI reference model. Correct description: You must use the eth-0 interfaces (management ports) of the Advanced Threat Defense Appliances for cluster communication. NOTE: The eth-0 interfaces of all nodes must be in the same layer-2 network of the OSI reference model. This requirement is for better performance and to avoid network latency. Solution: The ATD 4.8 product guide provides the correct information. The ATD 4.6 product guide has also been updated on the Enterprise Product Documentation site. |
|
| 1267950 | 4.6 | 4.8 | Issue: Inconsistent scan results are observed across ATD nodes in the same cluster. Solution: ATD 4.8 resolves this issue. |
|
| 1266987 | 4.6 | 4.8 | Issue: Antivirus DAT update fails sporadically because of a corrupt configuration file in the back-end. Solution: ATD 4.8 resolves this issue. Workaround: Toggle (enable, and then disable) the GTI HTTP Proxy setting in the ATD manager. |
|
| 1274528 | 4.0 | 4.8 | Issue: ATD 4.x before version 4.6.x does not show GAM Engine 7001.2017.3140 as installed. It shows GAM Engine 7001.2015.2026 as installed. Solution: ATD before version 4.6 does not support 7001.2017.3140. ATD 4.8 and later supports 7001.2017.3140. |
|
| 1272814 | 4.6 | 4.8 | Issue: MAR timeout settings fail with HTML samples. Solution: ATD 4.8 resolves this issue. |
|
| 1274080 | vATD 4.x | N/A | KB91578 | Issue: Virtual ATD (vATD) is unreachable over a network after you change the MAC address of the virtual network adapter from hypervisor. Cause: vATD does not support changing the MAC address of its virtual network adapter. Solution: Revert the MAC address to the original address. See the related article for details. |
| 1269632 | vATD 4.x | N/A | KB91593 | Issue: Microsoft Windows sandbox VM shows a blue screen and crashes in vATD running on Hyper-V host. Cause: You enabled processor compatibility for the vATD instance in Hyper-V. Solution: Disable processor compatibility for the vATD instance in Hyper-V. See the related article for details. |
| 1267129 | 4.6.2 | Issue: After you upgrade to ATD 4.6.2, configured secure NTP stops working. Cause: ATD to Secure NTP communication breaks because the password is encrypted. Solution: Open and save the secure NTP settings. |
||
| 1257618 | 4.6.0 | Issue: The HTML report does not contain the Timeline section when you open it from a locally downloaded Complete Results .zip archive. Solution: This behavior is expected. Generate a PDF report and view the Timeline section. The resources for the images, including timeline images, reside in the ATD back-end system. So, they are inaccessible after the report is sent from ATD and is hosted on the user's computer. To access the proper results in locally downloaded Complete Results, open the PDF that is generated for this purpose. |
||
| 1261609 | 4.6.0 | 4.6.2 | Issue: ATD cluster status becomes unstable. The Active director role flaps between primary node and backup node. Solution:
|
|
| 1260957 | 4.4.0 | 4.6.2 | KB91100 | Issue: High memory use in SNMP subagent. Solution: Disable SNMP, and then enable it. See the related article. |
| 1260786 | 4.x | Issue: During boot, vATD reports the error: Solution: ATD shares code between physical appliances and vATD. The service that is noted as FAILED during the vATD boot loads a kernel module that is relevant only to the hardware appliance. So, it fails when vATD loads the kernel module. You can safely ignore this error message. |
||
| 1260533 | 4.6 | KB91070 | Issue: You migrate to ATD 4.6.0 and the automatic VM creation runs as part of the migration process. The VM creation status indicator reports as Failed after the automatic VM creation finishes. Issue: The ATD console screen reports that the DHCP service fails to start during operating system boot sequence. Solution: See the related article. |
|
| 1251840 | 4.6 | KB91018 | Issue: VMs in a hybrid cluster are not activated correctly. Solution: See the related article. |
|
| 1258604 | 4.6 | KB91019 | Issue: VM creation fails intermittently after you migrate to ATD 4.6.0. Solution: See the related article. |
|
| 1239214 | 4.2 | 4.4 | Issue: You are unable to set virtualized nesting Windows 2012R2 Solution: vATD does not support Windows 2012R2 |
|
| 4.0 | Issue: Incoming email is not delivered to the receiving server. Cause: The Cisco Possible Delivery feature is not compliant with SMTP RFC 5321. So, there is a loss of emails at the receiving end, which is blamed on ATD. Solution: When the ATD scan timeout is greater than 300 seconds, you must disable Possible Delivery on your Cisco Iron Port appliance. Otherwise, the connection times out and the result is a loss of mail. NOTE: McAfee recommends that you keep a copy of your emails at the email gateway or server. This action avoids loss of mails if there is a fail to receive condition on ATD. The scan timeout is located under: ATD Manager, Manage, Email Connector, Configuration, Scanning Emails, Maximum time per email to wait for all scans to complete |
|||
| 1234016 | 4.4.0 | Issue: vATD is not supported on Haswell, For example, Solution: Always deploy vATD on Sandy Bridge or on newer processor architecture |
||
| 1236946 | 4.2.2 | Detection Package 4.2.2.180301 | Issue: VMDK to IMG conversion does not respond and displays a Converting image status indefinitely. Cause: The conversion process fails in the back-end, but the ATD Manager is not updated. Solution: Close the stuck browser window, open the ATD Manager, and log on as administrator. Navigate to Content Update and install Detection Package 4.2.2.180301. |
|
| 1232715 | 4.2.2 | 4.4 | Issue: You can't apply the time zone GMT + N hours. Solution: ATD 4.4 resolves this issue. |
|
| 1229960 1226150 |
4.2.0 4.2.2 |
4.4 | Issue: There is a memory leak in an adapter tool for McAfee Active Response integration. Solution: ATD 4.4 resolves this issue. |
|
| 1232010 1232741 |
4.2.2 | 4.4.2 | Issue: An application crash is reported in sandbox VM, and internet access is impeded in the VM. Solution: ATD 4.4.2 resolves this issue. |
|
| 1222843 | 4.0 | 4.2.2 | Issue: Unrotated log file fills up a disk partition. Solution: Upgrade to ATD 4.2.2. |
|
| 1227022 | 4.2 | 4.4 | Issue: When you click List Files, the Remote backup file service tries to connect using FTP even though you selected SFTP. Solution: ATD 4.4 resolves this issue. Workaround: Configure ATD to use an FTP server to perform your remote backups. |
|
| 1222566 | 4.0 | 4.2.2 | Issue: Content Update does not list the latest available package when direct internet access is blocked and a proxy server needs to connect to the internet. Solution: Upgrade to ATD 4.2.2. |
|
| 4.2 | Issue: ATD 4.2 documentation no longer lists VMware Workstation as a supported method to create VM images. Solution: ATD 4.2 supports VMware Workstation with VMware ESXi and Microsoft Hyper-V to create analyzer VMs. NOTE: The VMDK preparation tool is not available in the ATD 4.2 manager. IMPORTANT: This known issues article previously stated that ATD 4.2 supports only VMware ESXi and Microsoft Hyper-V to create analyzer VMs. This statement was incorrect. ATD 4.2 also supports VMware Workstation to create analyzer VMs. |
|||
| 1221575 | 4.2 | Issue: You see that DXL status is DOWN after you migrate to ATD 4.2. Solution:
|
||
| 1221089 | 4.2.0.20 | 4.2.0.22 | Issue: Sample submission fails when your submission URL uses the ATD host name. For example: Solution: The ATD 4.2.0.22 content update package resolves this issue. The package is available from the ATD manager, under Manage, Image & Software, Content Update, Application Software. Future ATD releases include this content update package. Workaround: Use the ATD IP address in your URL. For example: |
|
| 1219011 | 4.0 | 4.2.2 | Issue: Microsoft Windows 2012 and 2016 servers do not support ePO operating system profiling. Solution: Upgrade to ATD 4.2.2. |
|
| 1216076 | 4.0 | Issue: Custom web certificates synchronized in secondary nodes are not used by web server and x-mode. | ||
| 4.2 | Issue: Configuration of ATD to use Primary and Backup nodes in Microsoft Azure is not supported. In the event the Primary Node stops functioning, the failover does not work and the Backup node does not start. Workaround: Configure ATD to use Primary and Secondary nodes in Microsoft Azure. If the Primary node fails, the Secondary node starts and takes over. |
|||
| 1213997 | 4.0 | 4.2 | Issue: Email Connector directs emails to wrong host instead of to the smart host specified in host name. Solution: ATD 4.2 resolves this issue. |
|
| 1211626 | 4.0.4 | 4.2 | Issue: After you upgrade from ATD 4.0.2 to 4.0.4, your Solution: ATD 4.2 resolves this issue. |
|
| 1187242 | 4.0 | 4.2 | Issue: A DNS query from the sandbox VM is incorrectly sent to the preferred DNS server instead of the configured malware DNS server. Solution: ATD 4.2 resolves this issue. |
|
| 4.0 | Issue: For previous versions of ATD, McAfee mandated that you enable the Allow Multiple Logins option for the admin user when you upgrade ATD. This option is on the User Management page. Solution: Although it is no longer mandatory, McAfee still recommends that you select |
|||
| 4.0 | Issue: You can't use the following IP subnet range addresses for ATD 4.0 network interfaces:
NOTE: ATD is shipped with internal subnets for VMs (192.168.55.0/24 and 191.168.122.0/24 networks). ATD is shipped with a static routing table for these internal subnets. So, when you add ATD to your network, you must also add those subnets to your network. If your network already has the same subnet, you see a routing issue between ATD and your existing 192.168.55.0/24 and 191.168.122.0/24 networks. |
|||
| 4.0.2 | Issue: After you upgrade to vATD 4.0.2.42, you see that some entries under System Health are listed as Degraded and the System Health(Overall) status listed as Uninitialized. Solution: Reapply your license. If you continue to experience issues, contact Technical Support and ask them to check and refresh your license. |
|||
| 4.0.2 | Issue: After you upgrade to vATD 4.0.2.42, you can no longer connect to DXL. Solution:
|
|||
| 1200244 | 4.0 | 4.0.4 | Issue: Web Server Certificate configuration is not retained after an upgrade. Workaround: Upload the web server certificate again. Solution: ATD 4.0.4 resolves this issue. |
Back to top
| Reference Number | Found in Version | Fixed in Version | Related Article | Issue Description |
| ATD-9285 | 4.12 | 4.12.2 | Issue: URLs in the email report that are generated for failure to deliver emails are split at ‘:’ and displayed as separate entries. For example: https://google.com is shown as https and google.com. |
|
| ATD-4416 | 4.6 | Issue: Files with Unicode characters in their name can't be added to the whitelist from the Analysis Result page Workaround: Go to the Global whitelist page and use the files hash instead of its file name. |
||
| ATD-8323 | 4.x | Issue: When network interfaces experience fluctuation, Malware Interface routes are deleted from the You are notified about the link fluctuation through Syslog messages that ATD generates. Solution: Restart the network service from the CLI using command |
||
| ATD-3955 | 4.x | Issue: You see different sandbox severity scan results against the same file over a period. You see different results when you scan the sample on different ATD nodes, or when you use a different VM profile. Solution:
|
||
| ATD-3565 | 4.8.0 | 4.8.2 | Issue: Support Bundle fails to run with Hardware Logs selected. Solution: ATD 4.8.2 resolves this issue. Workaround: Do not select the Hardware Logs option when you generate a Support Bundle. |
|
| 4.8.x 4.10.x |
Issue: ATD dashboard shows higher CPU utilization post migration to ATD 4.8.0 or later. Cause: Database record conversion for time-zone of the past analysis records takes a long time to run. Solution: This behavior is expected. It can take several hours to a couple of days, and depends on the number of analysis reports your ATD has. NOTE: Until the conversion process is complete, the Analysis results of samples submitted post upgrade might not display in strict chronological order. This issue stabilizes and normal function is restored within 24 hours of the conversion process completion. |
|||
| ATD-3518 | 4.8 | Issue: A standalone ATD with ePO enabled is placed into a load-balancing node. The ePO connection to ATD is lost and the ePO status at ATD shows Down. You also see this issue when you move a node from a load-balancing setup and set it to Standalone. Workaround: In the ATD manager, open the |
||
| ATD-3454 | 4.6, 4.8 | Issue: You access the ATD manager using only the host name. Sample submission using the REST channel or manager fails or times out with the error: 401 Workaround: Access the manager using either FQDN or IP address.
|
||
| ATD-2043 | 4.6, 4.8 | Issue: You send an email and it is not delivered. You then see that there is no conversation log for this email. Workaround: You must clear the cache from Troubleshooting page in the ATD manager and resubmit the mail. You can then see the conversation log.
|
||
| 4.6, 4.8 | Issue: ATD can't generate a conversation log for emails sent without an attachment. | |||
| ATD-3519 | 4.6, 4.8 | 4.8 | Issue: When you have multiple operating system profiles configured, and one of them fails to create a license, ATD does not show the VM Creation as failed. This behavior ensures that other operating system profiles continue to analyze files. Workaround: You must manually create a license for the failed operating system profile. Solution: This issue is resolved in ATD 4.8. |
|
| ATD-3448 | 4.6, 4.8 | 4.8 | Issue: When an ATD user disables and then enables the ePolicy Orchestrator (ePO) or Data Exchange Layer (DXL) settings (reprovision), ePO does not display TIE Reputation for samples analyzed in ATD. Workaround: Make sure that McAfee Agent and ePO complete the tagging process, and the DXL broker is updated through the policy to reflect the new tagging. Run WakeUp Agent on ePO to DXL Brokers and TIE Server. NOTE: If the regular ASCI process is configured in ePO, it can update the policies on DXL and TIE Server automatically. You can see the sample’s TIE Reputation in ePO. Solution: ATD 4.8 resolves this issue. |
|
| TSNS-7382 | 4.6 | 4.8 | Issue: You see different scan results when the Analyze archive contents individually option is enabled or disabled. Solution: ATD 4.8 resolves this issue. |
|
| ATD-2122 | 4.6 | 4.8 | Issue: McAfee Active Response does not time out when an HTML sample scan exceeds the Solution: ATD 4.8 resolves this issue. |
|
| 1272909 | 4.6 | 4.8 | Issue: You delete the Minimum file size setting value and save your changes. The ATD Manager displays 0 for this setting. But, when you run the Solution: This issue is cosmetic. ATD 4.8 resolves this issue. |
|
| 1269664 | 4.6.2 | 4.8 | Issue: Screenshots in analysis reports are distorted or corrupted. Solution: ATD 4.8 resolves this issue. |
|
| 1267213 | 4.6.2 | Issue: TAXII server authentication fails if password length is not 3*N+2 characters long. N is a number value, such as 1, 2, 3, or 4. Solution: Configure a password length that matches this equation, for example 5, 8, 11, 14, or 17 characters. |
||
| 1261031 | 4.6 | Issue: The Manager logon screen reports your user account is locked out after several failed logon attempts. You see this message even though the feature is disabled. Workaround: You can still log on to ATD if you provide the correct password, even after you see the error message. |
||
| 1247015 | 4.4.2 | Issue: After you upgrade to ATD 4.4.2, the CLI console logon screen says that its ATD version number is 4.2.2.16.64450. Solution: This issue is cosmetic. Disregard the banner. To verify your ATD system version number, log on to the CLI with |
||
| 1246618 | 4.4.2 | Issue: Incorrect file type for Workaround: There is no workaround. Although the file type is incorrectly reported, the |
||
| 1240369 | 4.4.0.26 | 4.4 | Issue: The Activation window does not load when you access the ATD Manager with a host name or FQDN. Your browser displays an HTTP 404 code. Solution: ATD 4.4 resolves this issue. |
|
| 1236191 | 4.2.0 | Issue: McAfee Email Gateway shows result as ATD scan failed for archive samples when you disable the Analyze archive contents individually option in the analyzer profile. Solution: Make sure that the option Analyze archive contents individually is enabled in the analyzer profile. |
||
| 1237764 | 4.4.0 | Issue: Test connection to backup or restore host fails when the target is an ATD appliance. Solution: Avoid using ATD as a backup or restore server. |
||
| 1238822 | 4.4.0 | 4.4.2 | Issue: SNMP traps are generated for DXL status up and down, in case MATD is heavily loaded. Solution: ATD 4.4.2 resolves this issue. |
|
| 1237789 | 4.4.0 | Issue: SFTP to ATD fails for Solution: Reboot ATD. |
||
| 1233887 | 4.0 | KB90509 | Issue: Screenshots in the HTML analysis report do not display. You see broken links instead. Solution: This behavior is based on a limitation of product design, which McAfee will not change. Workaround: Check the PDF report instead of the HTML report from the ATD Manager. If you need an HTML report, download the complete result, and obtain the HTML report with screenshots. See the related article for more information about this issue. |
|
| 1228930 | 4.2 | 4.4 | Issue: DXL communication status is always listed as UP (green) even though ePO integration is disabled. Solution: ATD 4.4 resolves this issue. |
|
| 1222190 | 4.2 | 4.2.2 | Issue: ATD uses fixed SAN fields when you generate a Certificate Signing Request from the manager. Solution: Upgrade to ATD 4.2.2. |
|
| 1223276 | 4.2.0.22 | Issue: When you update to version 4.2.0.22: Solution: This issue is not an update failure. It occurs because the manager connection times out. You are advised to log back on to the ATD manager after a short time of 2–3 minutes. You then see that the update is successfully applied.
|
||
| 1182383 | 4.2 | N/A | KB90022 | Issue: ATD 4.2 changed to prevent the management interface from being used for potentially malicious or dirty traffic. Solution: See the related article for details. |
| 1219002 | 4.2 | 4.4 | Issue: Multiple logon and logoff messages are written to the syslog and audit logs. Solution: ATD 4.4 resolves this issue. |
|
| 1217741 | 4.2 | Issue: The LB Blacklist synchronize feature is not supported under reverse proxy feature for REST submission. | ||
| 1208475 | 4.0 | 4.2 | Issue: After you change the appliance name in the CLI, the host name is not updated in ePO and the ATD shell. Solution: Upgrade to ATD 4.2.0. |
|
| 1206989 | 4.0 | 4.2.2 | Issue: A scheduled backup sometimes fails with an exception. Solution: Upgrade to ATD 4.2.2. |
|
| 1205376 | 4.0 | 4.2 | Issue: The serial console stops working after you upgrade to ATD 4.0.x. Solution: Upgrade to ATD 4.2.0. Workaround: Add the following line at the end of the file |
|
| 4.0.2 | Issue: The ATD 4.0.2 Dashboard shows McAfee AV Engine version as 5900, and the Content Update page (Manage, Image & software, Content Update) shows McAfee AV Engine version as 5800. Solution: This issue is cosmetic. There is no separate DAT available for the 5900 AV engine. The engine version is parsed from the DAT, which is why the Content Update page shows the AV engine version as 5800 instead of 5900. |
|||
| 1191242 | 4.0 | Issue: The Workaround: Configure and apply this setting again. |
||
| 1187832 | 4.0 | Issue: Validation fails for German operating systems. You see the following error: You then see the following error: Workaround: Ignore these error messages and continue with VM creation. You see the Host verification PASS report and creation work. |
||
| 1198393 | 4.0 | Issue: The profiling report does not reflect the mail entries submitted before upgrade. | ||
| 1198325 | 4.0 | Issue: Filtered files are displayed as ATD cache in the profiling report of email connector. |
Back to top
Related Information
Para obtener documentos de productos de McAfee, vaya al portal Documentación de producto empresarial en https://docs.mcafee.com.
Para ponerse en contacto con el Soporte técnico, inicie sesión en ServicePortal y vaya a Crear una solicitud de servicio en https://support.mcafee.com/ServicePortal/faces/serviceRequests/createSR:
- Si está registrado, introduzca su ID de usuario y contraseña y, a continuación, haga clic en Iniciar sesión.
- Si no está registrado, haga clic en Registrarse y rellene los campos obligatorios. Recibirá por correo electrónico la contraseña y las instrucciones para iniciar sesión.
NOTA: Todas las futuras funcionalidades o lanzamientos de productos mencionados en la Base de conocimiento pretenden brindar una idea general de la dirección de los productos, por lo que no debe confiar en ellas para tomar una decisión de compra ni entenderlas como un compromiso.
Affected Products
Languages:
This article is available in the following languages:
GermanEnglish United States
Spanish Spain
French
Italian
Japanese
Portuguese Brasileiro
Chinese Simplified
