5. Issue: Since VirusScan Enterprise 8.7i Patch 2 and later include the new interface for reporting status to
Windows Security Center, uninstalling the Patch removes this function -- without reintroducing the older
expired function. This means that Windows Security Center does not report VirusScan Enterprise 8.7i being
installed until Patch 2 or later is implemented.
6. Issue: When you remove the McAfee AntiSpyware Module, the status in Windows Security Center is not
updated.
7. Issue: In deployments of VirusScan Enterprise 8.7i Patch 2 and later with McAfee Agent 4.5, the VirusScan
tray plug-in does not appear until after a restart of the McAfee system tray icon. If VirusScan is uninstalled,
the VirusScan tray plug-in is still visible until a similar restart.
8. Issue: This Patch adds needed support for McAfee VirusScan Enterprise for Offline Virtual Images 2.0, and
should not be removed unless the VirusScan Module is removed first.
9. Issue: The Patch installer included an MSI deferred action to resolve an issue found when attempting to
uninstall the Patch on some newer operating systems. The deferred.mfe file updated the cached MSI of the
currently installed VirusScan 8.7i product. If the Patch is included in a McAfee Installation Designer
customized package, the deferred.mfe file was not included, and therefore the Patch might not be able to be
uninstalled in some newer operating systems.
10. Issue: If you installed this release interactively and cancelled the installation on a system where a previous
Patch was installed, after the rollback was complete, the previous Patch might no longer reported to ePolicy
Orchestrator or appeared in the About VirusScan Enterprise window.
11. Issue: Installing the Patch and specifying a log file path using the Microsoft Installer (MSI) switch “/L” did
not log to the specified path. A log file capturing full data was logged to the folder “McAfeeLogs” under the
Temp folder.
12. Issue: If Host Intrusion Prevention 6.x or later was installed and disabled prior to installing VirusScan
Enterprise, it was necessary to re-enable Host Intrusion Prevention and disable it again, in order for
VirusScan Buffer Overflow Protection to be properly enabled.
13. Issue: Uninstalling VirusScan Enterprise Patches is possible for computers running Windows Installer v3.x
or later. This technology is not fully integrated for Windows 2000 operating systems, so there is no option to
remove the Patch in Add/Remove programs. See instructions under Removing the Patch for removal via
command-line options.
14. Issue: Patches for VirusScan Enterprise 8.7i can only be uninstalled via Add/Remove programs, not via
ePolicy Orchestrator.
Resolved issues
The resolved issues are divided into subsections per Patch, showing when each fix was added to the compilation.
Patch 3 resolved issues:
1. Issue: Users would see Windows Security Center notification pop-ups at regular intervals, stating that
VirusScan was disabled. (Reference: 529651)
Resolution: The VirusScan Enterprise Windows Security Center reporting tool now only updates its status
when the state of VirusScan changes, rather than at regular intervals.
2. Issue: The On-Access Scanner service failed to start after running Chkdsk at startup. (Reference: 450357)
Resolution: The Anti-Virus Filter driver no longer treats the disks as having been dismounted after the
Chkdsk procedure is completed.
3. Issue: Some VBScript types were not being properly scanned on Windows 2008 R2. (Reference: 505001)
Resolution: The ScriptScan application has been updated to account for changes in the Windows 2008 R2
platform.
4. Issue: A 3B bugcheck (blue screen) could occur immediately after an unexpected device-removal.
(Reference: 519656)
