McAfee VirusScan Enterprise 8.5i Patch 3 is officially released. This is a cumulative patch that includes all previously released fixes.

PATCH 3 RESOLVED ISSUES 

1. ISSUE:
A D1 bugcheck (blue screen) can occur with irusScan Enterprise 8.5i when installed on heavily loaded servers.

RESOLUTION:
This is resolved by HotFix VSE85HF352786 included with this release. See also issue 1 under "Known Issues."

2. ISSUE:
A D1 bugcheck (blue screen) can occur with VirusScan Enterprise 8.5i when installed on a Microsoft Exchange server.

RESOLUTION:
The Access Protection driver has been updated to resolve the issue.

3. ISSUE:
An 8E bugcheck (blue screen) was reported by customers and in Microsoft’s Online Crash Analysis (OCA), showing a crash in an instruction that could not ordinarily fail.

RESOLUTION:
The Link Driver was revised to bring it into compliance with guidelines specified in Intel’s Core2 Errata AI33, to prevent such unusual behavior on affected processors.

4. ISSUE:
A 7E bugcheck (blue screen) can occur with certain low resource conditions.

RESOLUTION:
The Link Driver has been updated to better handle scenarios where the system is low on resources.

5. ISSUE:
On 64-bit systems, VirusScan Statistics causes an issue where the user cannot open more then one Microsoft Virtual PC image. Virtual PC reports insufficient memory.

RESOLUTION:
VirusScan Statistics has been updated to resolve a memory utilization problem on 64-bit systems.

6. ISSUE:
When integrated with the Checkpoint SecureClient software, VirusScan Enterprise uses incorrect registry values for DAT and Engine version information.

RESOLUTION:
The binaries for Checkpoint integration have been updated to use appropriate registry data.

7. ISSUE:
With Access Protections rules set to Maximum Security, during the installation, VirusScan Enterprise Checkpoint integration fails to query the On-Access Scanner service state.

RESOLUTION:
The binaries for Checkpoint integration have been updated to no longer request a certain level of access to the service, which would be denied by the higher level of Access Protection security.

8. ISSUE:
Custom VirusScan Enterprise 8.5i policies are lost after upgrading from ePolicy Orchestrator 3.5 to 3.6.x.

RESOLUTION:
The VirusScan NAP file has been updated to include additional xml code for mapping policies between ePolicy Orchestrator 3.5 and 3.6.x.

NOTE: To migrate the policies correctly, follow the instructions under "Installation Steps."