We'll be releasing Patch 4 soon; by "soon" I mean our managed release will begin this month, and that means the general availability release - when you'll be able to download it - will be next month.
There are some items to be aware of with Patch 4 that I wanted to begin soaking "early" into the field's mindset...
i. Patch 4 will not install on top of the original "release to world" version of VSE 8.8
In other words, if you haven't patched the installation then you won't be able to patch it with Patch 4. Those using the unpatched 8.8 release may have to apply a patch (e.g. Patch 1) and then Patch 4, or, uninstall and reinstall the repost version that includes Patch 4.
ii. The full install package (when we repost the installation files so that they include Patch 4) will include the 5600 Engine.
iii. Patch 4 includes previous hotfixes that have been released, i.e. those that exist post Patch 2 (Patch 3 didn't have any hotfixes).
iv. Patch 4 addresses a number of business impacting issues. It'll be rated "High Priority" at least. These issue are varied, including BSODs, McShield crashes, resource leaks from unexpected scenarios, and system instability (tied to the McShield crashes actually).
Wherever business continuity is a concern, you'll want to install Patch 4.
v. Something not Patch 4 related but it's worth mentioning since Patch 4 contributes to the "problem"...
Environments that install VirusScan and then Patch VirusScan, and/or add Hotfixes to VirusScan, and who DO NOT REBOOT afterwards, are at a growing risk of encountering a BSOD from Stack Exhaustion. It's not our fault, not exactly - we simply didn't expect environments would make 3 or 5 upgrades to our kernel components and NEVER reboot. We allow for it to happen, so that's our fault. And it's technically feasible to do it - a feat not many vendors can claim, that we can update kernel level code without having to force an immediate reboot. However, the OS can only handle doing this so many times before a code execution path exhausts the the Stack of a thread. Therefore I implore you, after patching or hotfixing our kernel drivers, please plan a maintenance window to reboot the box. A reboot is not required, but if you do not, and you install 'x' number of Patch/Hotfix releases and STILL NO REBOOT, then you will eventually be FORCED to reboot because the system will crash! Then of course, you don't have to reboot , the BSOD satisfies any need for reboot - you might appreciate it better if it was planned.
vi. Patch 4's ePO extension adds the ability to query what Hotfixes are installed on clients. Be sure to set the conditions as "contains" rather than "equals", because the field we are querying might contain multiple Hotfix values and the "equals" does exact comparisons.
vii. Patch 4's ePO extension adds the ability to query the status of the On-Access Scanner. That means if it shows "bEnabled=0" or "disabled" then there's some kind of problem on the client.
viii. Oh yeah, Patch 4 is for ALL supported Windows platforms. HURRAH!
ix. Patch 4 is our officially supported release for Windows 8.1 or Server 2012 R2.
x. Just because I wanted to list 10 things... Patch 5 can be expected about 6 months after Patch 4 is released.
I'm sure there are questions.
This thread might get lengthy and wordy if I tried to respond to them all separately. So, I'll wait for some questions to accumulate then try to answer them here or I may use them as fodder for an FAQ elsewhere.