RESOLUTION:
The VirusScan Enterprise management plug-in has
been updated to only write to the registry if it
sees that it is different from the current
policy. This will prevent McShield from
generating events on policy enforcement, unless
that policy has changed.
This is an addendum to the original solution in
Patch 5, where the fix did not work when the
preferred language was set to something other
then automatic.
2. ISSUE:
A compatibility issue has been seen with
VirusScan抯 port blocking feature, and Veritas
backup applications. This was causing the
backup software services to stop running.
RESOLUTION:
The VirusScan Anti-Virus Mini-Firewall Driver
has been updated to correct the compatibility
issue.
3. ISSUE:
A race condition in the On-Access Scanner
service can cause high CPU utilization with high
performance systems.
RESOLUTION:
The On-Access Scanner service has been updated
to remedy multi-threading synchronization issues
and remove occurrences of runaway threads.
4. ISSUE:
The On-Access Scanner service sometimes crashes
during a system shutdown or during installation
of a Patch/HotFix.
RESOLUTION:
The On-Access Scanner service has been repaired
to correct a race condition in which a
critical-section synchronization object is
deleted before another thread has entered.
5. ISSUE:
A deadlock could occur on high end servers
caused by a race condition in VirusScan抯 link
driver.
RESOLUTION:
The link driver has been changed to properly
handle the release of system objects, while
holding a lock on resources.
6. ISSUE:
Port blocking fails on Microsoft Windows Vista
Service Pack 1.
RESOLUTION:
The McAfee Driver Installer has been update to
handle the changes in network stack load order.
7. ISSUE:
The On-Demand Scanner system utilization changes
that were put in patch 5 changed the memory
scanning function. This caused the process
scanning to only scan the first process ID.
RESOLUTION:
The change has been reversed so that all
processes are scanning irrespective of process
ID.
8. ISSUE:
When applied to a client installation that was
customized by McAfee Installation Designer
(MID), the patch installer deletes the
MidFileTime registry value. This caused MID
.CAB files to be re-applied to the system.
RESOLUTION:
The patch installer has been updated to no
longer delete the MidFileTime registry value.
9. ISSUE:
A newly created user defined Unwanted Program
Policy, does not take affect immediately if the
file has been scanned by the On-Access Scanner
before the change occurred.
RESOLUTION:
The On-Access Scanner service has been updated
to properly recognize changes to the user
defined detections and clear the cache of files
that have already been scanned so that the new
settings take effect immediately.
10. ISSUE:
A trust relationship exists in McAfee drivers
that can be leveraged by McAfee processes to
avoid triggering access protection rules and
other compatibility symptoms. When the link
driver was updated to newer releases this trust
relationship was lost until a reboot occurred.
RESOLUTION:
The link driver has been modified to better
handle the process of future upgrades to itself
without the need for a reboot.
PATCH 5 RESOLVED ISSUES
1. ISSUE:
Disabling the On-Access Scanner from the console
is not always possible when users with
sufficient privileges燽elonged to large numbers
of user groups.
RESOLUTION:
VirusScan Statistics has been updated so that
users with sufficient privileges can now燿isable
the On-Access Scanner from the console
regardless of how many user groups they belong
too.
2. ISSUE:
The VirusScan Enterprise management plug-in
writes all settings to the registry on every
policy enforcement. McShield service monitors
the registry and reloads whenever the settings
are written, generating frequent pause events in
the Windows System log.
RESOLUTION:
The VirusScan Enterprise management plug-in has
been updated to write to the registry only if it
sees that it is different from the current
policy. This prevents McShield from generating
events on policy enforcement, unless that policy
has changed.
NOTE:
If the symptom persists, refer to McAfee Support
KnowledgeBase article 614077.
3. ISSUE:
With the VirusScan Policy set to "Display
managed tasks in the client console," the tasks
sometimes disappear in the VirusScan Console.
RESOLUTION:
The On-Demand Scanner and Update console
plug-ins have been updated so that when policy
enforcement occurs, the console now updates the
list of tasks to ensure an accurate display.
4. ISSUE:
When using system variables in the folder path
for the Quarantine Manager Policy, the list of
quarantined items is empty, even though items
were quarantined to the correct directory.
RESOLUTION:
The Quarantine Manager console plug-in has been
corrected so that the path specified in the
folder input field is now properly expanded and
the system variables are replaced before the
list of Quarantined items is requested.
NOTE:
For further information about this fix, refer to
McAfee Support KnowledgeBase article 614549.
5. ISSUE:
When a VirusScan Patch installation failed, the
Help "About" dialog box no longer displayed the
previous Patch number.
RESOLUTION:
The patch installer has been updated to write
the new Patch registry value only if the Patch
succeeds. If it fails and a rollback occurs,
the old Patch registry value remains.
6. ISSUE:
A 4E bugcheck (blue screen) can occur when
VirusScan Enterprise 8.5i is installed along
side SafeBoot Content Encryption 3.
RESOLUTION:
The link driver was updated to add
supportability for SafeBoot.
7. ISSUE:
On Windows Vista and later, On-Demand Scan
function "Save as Default" does not correctly
save changes made for future scan tasks.
RESOLUTION:
The On-Demand Scanner has been corrected to
properly save the registry data for the default
task.
8. ISSUE:
Access Protection port blocking rules that
spanned a range of ports could block all
processes rather than only those processes
specified in the rule.
RESOLUTION:
The Access Protection driver has been updated to
better handle requests for process names.
9. ISSUE:
A 19 bugcheck (blue screen) occurred
intermittently when loading and unloading
content into Link Driver, for example, when
configuration changes were made or enforced.
RESOLUTION:
The link driver was corrected to resolve a race
condition that could lead to this issue.
PATCH 4 RESOLVED ISSUES
1. ISSUE:
A crash can occur on some systems when the
On-Demand Scan Task includes the "Memory for
rootkits" scan item.
RESOLUTION:
The root kit detection driver has been updated
to better handle different processor
architectures.
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.
RESOLUTION:
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.
RESOLUTION:
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.
RESOLUTION:
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
Scanner\McShield\Configuration
NOTE:
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.
RESOLUTION:
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.
RESOLUTION:
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.
RESOLUTION:
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.
RESOLUTION:
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.
RESOLUTION:
The Patch installer has been corrected so that
it only returns a success code if it is actually
successful.
10. ISSUE:
Installing the Patch on a system that had only
one Unwanted Programs exclusion causes that
exclusion to fail.
RESOLUTION:
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.
RESOLUTION:
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. |
发表于 2008-6-27 18:44:03
楼主
