information. The installation was left in a state where some of the product information still showed as the
older version. (Reference: 443019)
Resolution: The McAfee Installation Designer configuration applicator has been changed to be more
comprehensive in backing up and in version check-ing during the upgrade, in order to prevent failures by
other McAfee product installations that require version 8.7i.
NOTE: For this fix to prevent the above issue, the files need to be placed on the system during the
installation of VirusScan Enterprise, before the services start. The repost of VirusScan Enterprise 8.7i with
Patch 1 will be needed to see the resolution.
9. Issue: On Microsoft Windows Vista SP1 or 2008 server, sharing violations could occur when working with
remote files while network drive scanning was enabled. This resulted in being denied access to files, or being
unable to modify or save a file. (Reference: 447282)
Resolution: The Anti-Virus Filter driver has been updated to better handle potential sharing violations that
could occur and avoid conflicts.
10. Issue: Prolonged use of the VirusScan Console was causing delays in loading subsequent loading of the
Console window. (Reference: 456831)
Resolution: The VirusScan Console plug-in was corrected to properly clean up the .tmp files it creates at
load time.
11. Issue: Access Protection rules were being triggered during creation of a VirusScan customized installation
package via McAfee Installation Designer. This could lead to a crash of the McAfee Installation Designer tool.
(Reference: 435728)
Resolution: The VirusScan Email Scan library appropriately handles the new Sensitivity level setting when
it is displayed in the McAfee Installation Designer window.
12. Issue: Certain detections with multiple infections or clean actions were logging the action two times. One
entry was made during the middle of the process, and the other during the final resolution. (Reference:
404787)
Resolution: The Common Shell scanner has been updated to report only the final resolution of the
detection.
13. Issue: A 8E bugcheck (blue screen) might occur during the “Memory for Rootkits” portion of an on-demand
scan. (Reference: 445490)
Resolution: The code analysis driver now uses a more robust method of querying the system for driver
object data.
14. Issue: Access Protection block rules that were created for USB devices sometimes did not handle removing
and reinserting the device multiple times. (Reference: 457415)
Resolution: The Access Protection, Anti-Virus Filter, and Link drivers have been updated to better handle
reinserting the device.
15. Issue: The on-access scanner was not properly utilizing the Scan files opened for Backup option.
(Reference: 457416)
Resolution: The Anti-Virus Filter driver has been rectified to properly interpret the flag being sent from the
on-access scanner.
16. Issue: In an ePolicy Orchestrator managed environment, the agent’s Collect and Send Properties function
could cause the McAfee Product Manager service to spike its CPU utilization for extended periods of time.
(Reference: 457421)
Resolution: The VirusScan Management Plug-in has been updated to call for the scan engine and DAT files
via a new API call, rather than initializing the engine to retrieve the information. This lessens the CPU time
involved during the agent Collect and Send Properties function.
17. Issue: With certain Access Protection rules enabled, VirusScan Enterprise was failing to return information
to the Checkpoint SecureClient software. (Reference: 444667)
Resolution: The binaries for Checkpoint integration have been updated to properly request information
from VirusScan Enterprise.
18. Issue: Attempting to start an on-demand scan via the VirusScan tray icon could result in an error on
Microsoft Windows Vista. (Reference: 446950)
Resolution: The VirusScan tray icon correctly calls the on-demand scanner on User Access Controlled
operating systems.
