McAfee VIRUSSCAN ENTERPRISE 8.7I PATCH 4 - S Guía de instalación Pagina 13

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 19
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 12
1 Issue — The uninstall scripts do not detect the latest version of AV Kaspersky 6.0.4 when installing VirusScan Enterprise.
(Reference: 701815)
Resolution — When installing VirusScan Enterprise, the uninstall scripts now detects and removes AV Kaspersky 6.0.4.
2 Issue — The REBOOT=A option to SetupVSE.exe did not reboot the system if launched from a scheduled task. (Reference:
717989)
Resolution — SetupVSE.exe now enforces the REBOOT=A option, even if the user is not logged on interactively.
3 Issue — When upgrading from VirusScan Enterprise 8.5.0 to VirusScan Enterprise 8.8.0, an outdated driver was left
installed. In some instances, the old driver remained loaded in memory. (Reference: 741085)
Resolution — The installer now removes the outdated driver. A system reboot might be required to remove the driver
from memory and load the correct driver. The installer does not force a reboot.
Issues resolved in Patch 1
These issues were resolved in the VirusScan Enterprise Patch 1 release.
Patch
1 Issue — Installation fails with ERROR 1920, citing The McShield Service failed to start. This can occur when Microsoft
Windows is installed to a sub-folder rather than the root. (Reference: 638858)
Resolution — The system core installer has been revised to recognize all system paths.
2 Issue — A Bugcheck 5 error could occur if memory allocations are not checked for failure, resulting in an invalid memory
reference. (Reference: 643013, 651019, 673463, 676448)
Resolution — The memory allocation is now checked for success prior to referencing it.
3 Issue — Malicious software might change NTFS folder permissions on McAfee folders in order to disable the software.
(Reference: 643440)
Resolution — Self protection now protects McAfee folders, files and registry data from permission changes.
4 Issue — Process exclusion for Buffer Overflow was broken after introducing more granularity in Buffer Overflow
exclusions using Module Name and API Name. (Reference: 651569, 686711, 687670)
Resolution — Process exclusions for Buffer Overflow work as expected on standalone machines, ePolicy Orchestrator
managed systems and during ePolicy Orchestrator Policy Migration.
5 Issue — When multiple signatures are included in an EXTRA.DAT, the buffer used to store the description information for
the "About" window might not be large enough. (Reference: 651670)
Resolution — Buffer size for storing Extra.DAT signature information has been increased to 4 times its original size.
6 Issue — When the option “Show add-in user interface error” is enabled in Outlook, the following pop-up error appears
every time Outlook is started and the first e-mail is opened or created: “Custom UI Runtime Error in McAfee E-mail Scan
Add-in”. (Reference: 651887, 656365, 656366, 656644, 656674, 656678, 657131, 657398, 657409, 657411, 657413,
657414, 657433, 661628, 675246)
ResolutionMcAfee E-mail Scan Add-in has been fixed to return correct “success” error code to Outlook. The pop-up
error no longer appears.
7 Issue — Files on network locations might trigger an unhandled exception leading to a system crash if the network
experiences a failure or the object is unreadable. One report of this occurred when opening Outlook 2010 with PST files
Vista de pagina 12
1 2 ... 8 9 10 11 12 13 14 15 16 17 18 19

Comentarios a estos manuales

Sin comentarios