| Focus Area | Specific Issues Addressed (from Patch 17) | | :--- | :--- | | | - Resolved bug checks (blue screens) in certain virtualization products using the Microsoft Filter Manager framework (Bugcheck 0x24). - Fixed bug checks in the mfehidk.sys driver, a core component responsible for system hooking and file system filtering. | | Performance | - Removed a network bottleneck in the mfewfpk.sys driver that unnecessarily throttled network traffic. - Fixed an issue where On-Demand Scans would quit prematurely on systems with large amounts of RAM and multiple cores. | | Memory | - Fixed a memory leak in the On-Demand Scan process, which prevented memory usage from increasing for entire scan read activities. - Addressed an issue where systems with multiple network adapters and Receive Side Scaling (RSS) could accumulate an unlimited backlog of UDP I/O, potentially exhausting system memory. | | Management & Reporting | - Ensured that the VirusScan Console accurately reflects the On-Access Scan status for ePolicy Orchestrator (ePO) administrators. - Fixed a deadlock condition between the "pause for update" process and trust validation that caused McShield to time out after a DAT update. | | Scanning & Exclusions | - Corrected an issue where On-Demand Scan exclusions were not properly respected during scans. - Fixed path comparison when exclusion lists contained a combination of file names with no extensions, path names, and wildcards. - Fixed an issue where the Outlook On-Demand scanner skipped items in PST files larger than 1GB when new mail activity was received. | | Installation | - Resolved a failure to install VSE 8.8 on some Windows XP and Windows 2003 systems by adjusting non-critical installation requirements. - Increased text box sizes (from a limit of 200 characters) to allow over 5,000 characters for Access Protection policies in the ePO console. |
Patch 17 is not a new product. It is a cumulative rollup of all previous patches (1 through 16), plus specific hotfixes. It is the final "fully supported" build for Windows 7, Windows 8.1, and Windows Server 2012 R2 (legacy support only for Server 2016/2019).
: Identify any air-gapped or specialized industrial systems that must stay on VSE and ensure they are at least running Patch 17 to minimize known software flaws. --- Mcafee Virusscan Enterprise 8.8 Patch 17
Patch 17 introduced a persistent system tray balloon tip warning administrators that VSE is deprecated. This is non-intrusive but serves as a legal notice for support expiration.
Perhaps the most critical information for any organization still using VSE 8.8 is its end-of-life (EOL) status. . This means that after this date: | Focus Area | Specific Issues Addressed (from
Deploying Patch 17 requires specific ordering to avoid corrupting the local engine or breaking communication with the centralized management agent. McAfee VirusScan Enterprise - Veterans Affairs
What (e.g., Windows Server 2008, Windows 10) are currently running this patch? - Fixed an issue where On-Demand Scans would
Understanding the mechanics, security context, and deployment constraints of Patch 17 is vital for organizations managing specialized long-term support environments. 🛡️ Core Features of VirusScan Enterprise 8.8
McAfee VirusScan Enterprise (VSE) 8.8 Patch 17 represents the released for the VSE 8.8 product line. Following Patch 16, this update continued to address critical vulnerability exposures, resolved specific engine-to-dataset compatibility issues, and extended support for certain Windows operating systems before the product’s final End-of-Life (EoL) declaration on December 31, 2022 (for standard support) and December 31, 2023 (for extended support).
Ensure you have on the target computer.