Resolved Issues - McAfee VIRUSSCAN ENTERPRISE 8.7I PATCH 4 - RELEASE NOTES Release Note

15. Issue: Due to changes made to the VirusScan Enterprise 8.7 Repost 3 MSI, VirsuScan Enterprise 8.7 patches will not install with
McAfee Installation Designer without an additional configuration step. See McAfee Installation Designer patch configuration under
Installation instructions for instructions on adding a patch to a custom installation package.

Resolved issues

The resolved issues are divided into subsections per Patch, showing when each fix was added to the compilation.
Patch 4 resolved issues
1. Issue: Applications were not being monitored by VirusScan Enterprise Buffer Overflow Protection, which could cause a
performance penalty when the Buffer Overflow Protection feature was enabled for other processes. (Reference: 508049)
Resolution: Changes were made in the way some APIs are monitored for the VirusScan Enterprise Buffer Overflow Protection
implementation, so that processes not being monitored by VirusScan Enterprise Buffer Overflow Protection can be excluded from
evaluation earlier and with less of a performance impact.
2. Issue: VirusScan Task Manager could encounter access violation and crash on exit. Threads were not properly synchronizing on
exit, resulting in access violation. (Reference: 530449)
Resolution: Threads are now being properly synchronized, providing serialized access to common data on exit.
3. Issue: Tasks created by ePolicy Orchestrator were not stopping when set to only run for a specified time. (Reference: 531674)
Resolution: The VirusScan Management Plug-in now uses the correct function call to terminate the task on 64-bit platforms. The
fix provided in this Patch improves the fix provided in Hotfix 537674, which was released 02-19-2010.
4. Issue: An issue can arise during an upgrade from VirusScan Enterprise 8.5i to VirusScan Enterprise 8.7i where the preserved
tasks are deleted after the first reboot. (Reference: 537579)
Resolution: The McAfee Task Manager service no longer attempts to index the tasks during shutdown, which caused the task to
be deleted.
5. Issue: The OutlookScan feature could fail to release an instance of the scan engine that was loaded via EngineServer.exe. This
could lead to symptoms of EngineServer.exe using large amounts of memory, until the service was restarted. (Reference:
539488)
Resolution: The Outlook UI library now properly releases the engine instance on exit of Outlook.
6. Issue: VirusScan events received by ePolicy Orchestrator may fail to be processed by the Event Parser. Unexpected characters in
the event caused an error to be logged by the Event Parser, and the event to remain in the events folder on the server.
(Reference: 539709)
Resolution: The CommonShell library has been updated to replace invalid characters to be changed to a question mark in order
to be successfully received by ePolicy Orchestrator.
7. Issue: Users were unable to save an Alert Policy change if all options were disabled. (Reference: 539933)
Resolution: User can now save policies after deselecting all components that generate alerts. Users also can use the
checkboxes and drop-down options on the Additional Alerting Options tab after deselecting all components that generate alerts.
8. Issue: Certain German cookies were causing on-demand scans to appear to hang during the Cookie Scan. (Reference: 542698)
Resolution: The commonshell library better handles reparse points that are being checked while walking through profiles folders
for cookies.
9. Issue: The On-Delivery Email Scan Policies Report tab was missing descriptive text for dialog boxes. (Reference: 544855)
Resolution: 'Maximum log file size:' and 'MB' descriptive text has been added to the On Delivery Email Scan Policies Report tab.
10. Issue: When using McAfee Installation Designer to configure the Artemis setting for email scanning, the value was being read
and written to the regular location under HKLM registry key. (Reference: 547056)
Resolution: The value is now correctly read and written to the temporary MID key under HKCU. This allows the value to be
correctly saved when McAfee Installation Designer generates the settings for custom packages.
11. Issue: No event XML files were being generated for event IDs 1087 and 1088. (Reference: 547867)
Resolution: XML files will now be created for event IDs 1087 and 1088 and will be seen in the AgentEvents folder.
12. Issue: In certain circumstances, the extra460575.rul that controls the Access Protection rule "Prevent Termination of McAfee
Processes" was incorrectly placed on 32-bit systems and improperly removed on 64-bit systems. (Reference: 549354)
Resolution: The MSP Patch installer now checks for the existence of the file and corrects any invalid states.
13. Issue: Invoking an on-demand scan on a folder that is a part of a Symbolic or Junction Link results in an indefinite on-demand
scan estimation/scanning time. (Reference: 551494)
Resolution: On-demand scan estimation function now handles Symbolic and Junction Links properly.
14. Issue: VirusScan Task Manager could leave runaway threads when exiting. The runaway threads created high CPU situations
that could make servers unresponsive. (Reference: 552611)
Resolution: This issue has been corrected by ensuring no runaway threads are left behind on exit.
15. Issue: Artemis sensitivity level pull-down menu for the default on-demand full scan was diabled (grayed out) periodically.
(Reference: 552834)
Resolution: Artemis sensitivity level pull-down menu is now always enabled and not grayed out in the On-Demand Full Scan