Currently available for download from
PrimeSupport
RESOLVED
ISSUES
1.
ISSUE:
Significant performance loss may be
experienced by processes that frequently write data to the same file, usually an
.INI or .LOG file, and usually multiple writes per second. The issue was only
noticed after applying VSE80HF256301.
RESOLUTION:
The file system filter driver
has been updated to resolve the issue.
2.
ISSUE:
McAfee Installation Designer (MID)
creates VirusScan Enterprise installation files that include a configuration
change file (VSECFG.CAB). If also managed by McAfee AutoUpdate Architect (MAA),
where a configuration change file is hosted in the repository, after a patch
update the original configuration change file is installed and applied. Updating
from the MAA repository again does not reapply the newer configuration change
file.
RESOLUTION:
After this Patch release is
installed, the most recent configuration change file (.CAB file) is
applied.
NOTE:
If VSECFG.CAB has been deleted,
it is created and the settings applied when a Patch is
installed.
3.
ISSUE:
Access Protection rules that
contain references to a drive letter may not work on Dynamic Disk
volumes.
RESOLUTION:
The file-system filter driver
has been updated to resolve this issue.
4.
ISSUE:
Installing Patch 12 to systems
where Patch 11 was installed could result in a successful patch installation,
although the product still shows Patch 11 is
installed.
RESOLUTION:
This release ensures that
updating systems with Patch 11 will show that Patch 13 is installed after
successful installation.
5.
ISSUE:
Where the ScriptScan module,
SCRIPTPROXY.DLL, was unregistered, or disabled after Hotfix 241572 was applied,
the patch installation would reregister
SCRIPTPROXY.DLL.
RESOLUTION:
This release does not register
the ScriptScan module.
6.
ISSUE:
Patch installations via ePolicy
Orchestrator or Protection Pilot, where the Patch failed to install on the end
node, would not make further attempts to install. The installation detection
script would write a registry value confirming the Patch was installed before
installation had completed.
RESOLUTION:
The installation detection
script used by ePolicy Orchestrator and Protection Pilot now writes a registry
value confirming the Patch is installed when the installation is
completed.
7.
ISSUE:
Detection alerts from the Cookie
Scan feature can be of sufficient number to cause
concern.
RESOLUTION:
Alerts for cookie detections can now
be disabled by adding a dword "bCookieAlerts" to the registry key
HKLM\Software\Network Associates\TVD\Shared Components\Alert Client\VSE, and
setting the value to "0" zero. This release does not add the
value.
8.
ISSUE:
Where the Anti-Spyware Module
was checked into an ePolicy Orchestrator or Protection Pilot repository, after a
current Patch was installed the module would attempt to install
repeatedly.
RESOLUTION:
This is resolved by HotFix
MASE80HF273746 included with this release. See also "Known Issues" number
1.
9.
ISSUE:
Local tasks would fail to run at
the scheduled time if created after Patch 12 or later was applied. The
corresponding task configuration file was being modified with incorrect
data.
RESOLUTION:
This release ensures the task
configuration files contain correct data.
NOTE:
If you already have Patch 13
installed and are experiencing this issue, contact McAfee Support for HotFix
280107.
I believe this is a complete set of
issues also resolved by Patch 12 (never released) and included in Patch 13,
although I compiled it myself, so it could be subject to
error:
42.
ISSUE:
The user interface option that
allows you to password-protect the "On-Access Scanner: Detection" page
mistakenly protects both the On-Access Scan "Detection" and On-Access Scan "Set
Exclusions" property pages. A user could not add
exclusions.
RESOLUTION:
Choosing to protect the
"On-Access Scanner: Detection" page from the "User Interface Options" now
protects only the On-Access Scan "Detection" page.
43.
ISSUE:
A delay in responsiveness of the
script engine would occur when executing scripts
sequentially.
RESOLUTION:
Scripts terminate correctly,
allowing the script engine to respond to subsequent script
commands.
44.
ISSUE:
An "Access denied" error
appeared in an application that used the "delete-on-close" flag when working
with temporary files. The file system filter driver would lose track of the
"delete-on-close" flag.
RESOLUTION:
The updated file system filter
driver resolves this issue, allowing temporary files to be utilized as
expected.
45.
ISSUE:
Null entries are seen in the
ePolicy Orchestrator database under the severity field due to the VirusScan
Enterprise 8.0i extended NAP file.
RESOLUTION:
The extended NAP file has been
modified to correctly handle the severity field.
46.
ISSUE:
When disabled, the ScriptScan
feature will remain registered and still handles VB Script and Jscript
operations, even though it is not scanning.
RESOLUTION:
When the ScriptScan feature is
disabled, the component is unregistered, and when enabled the feature is
registered.
47.
ISSUE:
The error "Access Denied" is seen
when accessing a remote share. This can occur when user profile information is
redirected by a Microsoft Windows group policy object, and the user tries to
save a file to their "My Documents" folder.
RESOLUTION:
The issue has been resolved in
the updated common scan components.
48.
ISSUE:
In environments using
Distributed File System shares, a noticeable increase in network traffic
activity may be experienced.
RESOLUTION:
The file system filter driver
has been updated to resolve the issue.
49.
ISSUE:
During shutdown the VSTSKMGR.EXE
process may crash with an error similar to "VSTSKMGR.EXE – the exception
privileged instruction 0x00000096 occurred in the application at location
0x0012e80d."
RESOLUTION:
An update to VSTSKMGR.EXE, the
McTaskManager Service, resolves the issue.
50.
ISSUE:
After applying VirusScan
Enterprise 8.0i Patch 11, when a system resumes from the hibernation power
saving state, the on-access scanner may be paused.
RESOLUTION:
The on-access scanner now
correctly is enabled when the system resumes from
hibernation.
51.
ISSUE:
A vulnerability exists in the
Common Management Agent (CMA) where an unexpected file can be run with system
privileges. Communication between the VirusScan Enterprise plug-in and CMA can
be utilized as a mechanism to exploit this
vulnerability.
RESOLUTION:
The VirusScan Enterprise
plug-in, VSPLUGIN.DLL, has been updated to prevent the potential
exploit.
52.
ISSUE:
When accessing some Japanese
named files with a long filename, the on-access scanner service, MCSHIELD.EXE,
could crash or cause the accessing application to stop
responding.
RESOLUTION:
MCSHIELD.EXE has been updated to
resolve this issue.
53.
ISSUE:
The memory scan feature of an
on-demand scan did not detect potentially unwanted programs that were resident
in memory.
The memory scan feature did not
use the exclusion list.
The memory scan feature failed
to record when a detection was successfully
cleaned.
RESOLUTION:
The issue has been resolved in
the updated on-demand scan components.
54.
ISSUE:
After applying VirusScan
Enterprise 8.0i Patch 11 where the Anti-Spyware Enterprise module is installed,
the Cookie Scan feature detects the same cookie
twice.
RESOLUTION:
The issue has been resolved in
the updated common scan components.
55.
ISSUE:
In ePolicy Orchestrator, the
"Top 10" virus report shows a "_" character as the virus
name.
RESOLUTION:
The issue has been resolved in
the updated common scan components.
56.
ISSUE:
If the ePolicy Orchestrator
Agent is installed, the on-access scanner could crash when resuming from the
hibernation power-saving state.
RESOLUTION:
The issue has been resolved in
the updated on-access scanner.