Recent updates to this article:
| Date |
Update |
| September 18, 2020 |
Updated KB article links. |
{GENSUB.EN_US}
{GENRN.EN_US}
Product release information:
| Product Version |
Released Date |
Release
Notes |
VSES 1.2.0 Hotfix 1243923
(HF1243923) (RTS) |
February 19, 2019 |
- |
VSES 1.2.0 Hotfix 1135217
(HF1135217) |
May 4, 2017 |
Release Notes |
| VSES 1.2.0 |
May 10, 2016 |
Release Notes |
NOTE: To view the article on VSES 1.3.0 Known Issues, see
KB90019.
{GENRLS.EN_US}
Known Issues
CRITICAL:
| Reference Number |
Related Article |
Found Version |
Resolved Version |
Issue Description |
| 1151959 |
- |
1.2.0 |
VSES 1.2.0
HF1135217
|
Issue: In C-Mode scanning, McAfee VirusScan Enterprise for Storage now returns appropriate error string when unable to scan an encrypted file. |
| 1135948 |
- |
1.2.0 |
VSES 1.2.0
HF1135217
|
Issues:
- McAfee VirusScan Enterprise for Storage now returns appropriate error code to the storage system when the scanner receives broken scan paths.
- When scanning files from the CDOT appliance, the scanning timeout now generates appropriate return code. This code indicates that the file was not scanned because of a scanning timeout.
|
| n/a |
n/a |
1.2.0 |
n/a |
IMPORTANT: VSES 1.2.0 only supports VSE 8.8 with Patch 7 or later. No previous versions of VSE are supported with VSES 1.2.0. |
| n/a |
KB86868 |
1.2.0 |
n/a |
See the related article for important prerequisites for installing VSES 1.2.0. |
Non-critical:
| Reference Number |
Related Article |
Found Version |
Resolved Version |
Issue Description |
| 1243923 |
- |
1.2.0 |
VSES 1.2.0
HF1243923 |
Issue: Threat Source Hostname field in Threat Event Log does not display incorrect information for Threat Source system. |
| 961095 |
- |
1.1.0 |
VSES 1.3.0 |
Issue: VSES reports in ePO do not provide details about VSES hotfixes.
Resolution: With VSES 1.3.0, ePO queries now allow you to intelligently manage compliance of your environment for a hotfix. |
| 1195988 |
- |
1.2.0 |
VSES 1.3.0 |
Issue: For VSES to be supported on Windows 2008 x86 and x64, it needs to be signed with the new McAfee SHA-1 and SHA-2 certificates.
Resolution: VSES 1.3.0 binaries are now dual-signed with McAfee SHA-1 and SHA-2 certificates. |
| 1112034 |
KB89789 |
1.2.0 |
Expected Behavior |
Issue: 0 (zero) KB files remain in the VSEIcapTempFiles directory for between 60–120 minutes after a file is scanned. Several logs record the following error:
"vscan engine status: 222200020, vscan engine result string: Error the file is locked and could not be scanned". |
n/a = not available
