1 2 3 Previous Next 26 Replies Latest reply on Nov 20, 2007 10:12 AM by gerryrigney

    Release Notes for VirusScan Enterprise 8.5i Patch 4

      Release Notes for McAfee(R) VirusScan(R) Enterprise Version 8.5i Patch 4


      Patch Release: October 16 2007

      This release was developed and tested with:

      - VirusScan Enterprise:8.5i
      - DAT Version: 5126, September 24 2007
      - Engine Version: 5.2.00

      Make sure you have installed these versions, or
      better, before using this release.


      Thank you for using VirusScan(R) Enterprise
      software. This file contains important information
      regarding this release. We strongly recommend that
      you read the entire document.

      The attached files are provided as is, and with no
      warranty either expressed or implied as to their
      suitability for any particular use or purpose.
      McAfee, Inc. assumes no liability for damages
      incurred either directly or indirectly as a result
      of the use of these files, including but not limited
      to the loss or damage of data or systems, loss of
      business or revenue, or incidental damages arising
      from their use. Patch files should be applied only
      on the advice of McAfee Technical Support, and only
      when you are actually experiencing the issue being
      addressed by the Patch. Patch files should not be
      proactively applied in order to prevent potential
      product issues. You are responsible for reading and
      following all instructions for preparation,
      configuration, and installation of Patch files.
      Patch files are not a substitute or replacement for
      product Service Packs which may be released by
      McAfee, Inc. It is a violation of your software
      license agreement to distribute or share these files
      with any other person or entity without written
      permission from McAfee, Inc. Further, posting of
      McAfee Patch files to publicly available Internet
      sites is prohibited. McAfee, Inc. reserves the right
      to refuse distribution of Patch files to any company
      or person guilty of unlawful distribution of McAfee
      software products. Questions or issues with McAfee
      Patch files should be directed to McAfee Technical


      - About This Release
      - Purpose
      - Patch 4 Resolved Issues
      - Patch 3 Resolved Issues
      - Patch 2 Resolved Issues
      - Patch 1 Resolved Issues
      - Known Issues
      - Files Included With This Release
      - Installation
      - Installation Requirements
      - Installation Steps
      - Installation Steps via ePolicy Orchestrator
      - HotFix/Patch Reporting
      - Verifying the Installation
      - Removing the Patch
      - Contact Information
      - Copyright & Trademark Attributions
      - License Information



      This release contains updated binaries in a single
      Microsoft Patch installer to address all items
      listed in "Resolved Issues" below.

      For the most update-to-date copy of this Readme
      information, refer to McAfee Support KnowledgeBase
      article 613984.


      The resolved issues are divided into subsections per
      patch, showing when each fix was added to the


      1. ISSUE:
      A crash can occur on some systems when the
      On-Demand Scan Task includes the "Memory for
      rootkits" scan item.

      The root kit detection driver has been updated
      to better handle different processor

      2. ISSUE:
      When a Quarantine Restore Task is run from
      ePolicy Orchestrator without specifying a
      restore item, the Scan32.exe process runs a full
      scan and does not exit properly, leaving the
      process orphaned.

      The VirusScan plug-in has been updated to check
      if a restore item is specified. If not, the
      restore task does not run.

      3. ISSUE:
      The VirusScan On-Demand Scanner has no option to
      disable cookie detection alerts in the user
      interface or registry.

      Alerts for On-Demand Scan cookie detections can
      now be disabled by setting the DWORD
      "bCookieAlerts" registry entry to 0.

      HKLM\SOFTWARE\McAfee\VSCore\Alert Client\VSE

      4. ISSUE:
      When a user is browsing the Internet, the
      On-Access Scanner sometimes logs entries "Not
      scanned (The file is encrypted)" on temporary
      files that are locked for use by the browser.

      The reporting for these types of detections can
      now be disabled by setting the registry DWORD
      value "DoNotReportSkippedFiles" to 1.

      HKLM\SOFTWARE\McAfee\VSCore\On Access

      If you previously installed VSE85HF328421, the
      registry entry "DoNotReportSkippedFiles" is
      already set to 1.

      5. ISSUE:
      In environments where the Lotus Notes data
      folder is in a non-standard location, the
      VirusScan Scanner for Lotus Notes installer
      might crash during installation of VirusScan.

      The VirusScan Scanner for Lotus Notes
      installation files have been updated so that the
      search behavior for notes.ini is more resilient
      to custom Lotus Notes client locations.

      6. ISSUE:
      A crash can occur, where the VirusScan Scanner
      for Lotus Notes failed to initialize properly if
      the first scanned attachment of a session was
      stored in a non-standard attachment format.

      The VirusScan Scanner for Lotus Notes library
      was changed so that the initialization code
      occurs before the attachment prefixed file name
      handling occurs.

      7. ISSUE:
      With Self Protection enabled, the ability to
      unblock a connection from a remote computer is
      grayed out, even though the logged-on user has
      administrator privileges.

      VirusScan Statistics has been updated to check
      the credentials of the logged-on user, rather
      then the access level of our services, to
      determine if the "Unblock All Connections Now"
      button should be available.

      8. ISSUE:
      Installation of this Patch enables the option
      "Enable on-access scanning at system startup" if
      it was previously disabled.

      The Patch installer has been corrected to
      properly preserve the setting.

      9. ISSUE:
      The Patch installer returns a success code, even
      if the Patch failed to install.

      The Patch installer has been corrected so that
      it only returns a success code if it is actually

      10. ISSUE:
      Installing the Patch on a system that had only
      one Unwanted Programs exclusion causes that
      exclusion to fail.

      The installer now corrects a problem where the
      DetectionExclusions registry value was being
      changed from REG_MULTI_SZ to REG_SZ if only one
      value existed.

      11. ISSUE:
      On Windows Vista, the administrator cannot
      disable the On-Access Scanner via the VirusScan
      system tray icon.

      VirusScan Statistics has been updated to check
      the user's logged on credentials, rather then
      the service handle that was used to determine
      access to the McShield service in older
      operating systems.

      12. ISSUE:
      A failed reinstallation of VirusScan or a failed
      Patch installation can delete the license,
      resulting in an inoperable product.

      The Patch installer has been updated to no
      longer cause this state in the event of a failed

      13. ISSUE:
      An incorrect rule file was packaged with the
      VirusScan NAP file included with Patch 3. This
      caused some of the Access Protection rule
      categories to not appear.

      A new VirusScan NAP file was created with a
      corrected rule file.

      14. ISSUE:
      When Host IPS is installed with VirusScan
      Enterprise, and IPS is disabled, the interface
      for VirusScan Buffer Overflow Protection remains
      grayed out, even though it is active.

      The Buffer Overflow console plug-in was updated
      to check for the registry flag that is set by
      Host IPS, to tell VirusScan Enterprise that IPS
      is disabled.

      15. ISSUE:
      When Self Protection is enabled on a remote
      machine and a user attempts open a remote
      console connection to that machine, the user
      receives an access denied message, and the
      remote console is not opened.

      The VirusScan Console was updated to make the
      connection to the remote console more robust.

        1 2 3 Previous Next