Recent updates to this article
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.
| Date |
Update |
| June 17, 2019 |
Updated resolution for 1257771 about HIPS 8.0 Patch 13 GA release. |
| May 31, 2019 |
Updated 1257771 information about HIPS 8.0 Patch 13 release and workaround using RTS package HIPS 8.0 Patch 12 HF20190418. |
| May 6, 2019 |
Updated the resolution for reference number 1257771. |
| October 31, 2018 |
Initial publication. |
Known Issues
CRITICAL: Currently, there are no critical issues.
Non-critical:
| Reference Number |
Related Article |
Found in
Host IPS Version
|
Resolved in
Host IPS Version |
Issue Description |
| 1257771 |
|
8.0 Patch 11 |
8.0 Patch 13 |
Issue: A cumulative upgrade to Host IPS 8.0 Patch 11 or Patch 12 fails for Host IPS clients when Host IPS 8.0 Patch 4 is installed in the upgrade chain. If you encounter this issue, the error 1636 appears in the client installation log.
Workaround:
1. Customers can contact Technical Support for RTS package HIPS 8.0 Patch 12 HF20190418. See PD28330.
2. If you encounter this issue, to update to the latest version Host IPS 8.0 Patch 11 or Patch 12, you need to uninstall the existing version of the Host IPS 8.0 client. Then, after a successful uninstall, push a Host IPS 8.0 Patch 11 or Patch 12 full install or deployment task to the system. If there any files to be updated that are in use, a restart might be needed after you uninstall the earlier version.
Resolution: This issue is resolved in the Host IPS 8.0 Patch 13 release (General Availability). |
| 1257380 |
|
8.0 Patch 10 |
|
Issue: Custom signatures intended to protect registry values do not work unless you use expert rules to create the rule. |
| 1213517 |
|
8.0 Patch 10 |
|
Issue: Communication is blocked for Microsoft Edge with Application Guard when you use Host IPS Firewall.
Workaround: Create a firewall rule with the following criteria: Allow Inbound TCP/IPv4 and TCP/IPv6; Local Ports 80 and 443, or just the proxy port, when appropriate; Remote Ports 49700–65535; Virtual Media. McAfee is investigating whether further qualifying criteria can be set for this rule to avoid the issue.
NOTE: This rule also matches for VPN adapters. VPN traffic matching will be disrupted. |
