I think it odd to see comments still being added to the Patch 4 post () but it's time to start one for Patch 5 .
In the same spirit of giving everyone a Heads Up on what to expect with Patch 5, to preempt some questions where possible and help you prepare for what is to come...
Dates are firm but fluid; if they change it'll be in the interest of quality -
Limited availability*: Jan 29
General availability: Feb 26
* Select customers only; the managed release or RTS period, during which the SEO team are closely monitoring the patch's performance/acceptance, thus not open to all customers.
Some points from the prior posting about Patch 4 remain true for Patch 5, those are:
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.
Similar but different from Patch 4:
My recommendation:
Item iii. identifies key reasons why I would recommend Patch 5 for all environments (plus the carrying forward of improvements over older patches).
Item iv. touches on why I feel the patch should be tested thoroughly before wide distribution in any environment.
And as with any patch release, keep an eye out for updates being posted to our Known Issues article specific to the release. It's not posted yet but Patch 5's Known Issues article will be KB81381.
NOTE: Windows 10 is not supported with Patch 5 (that will be a goal of Patch 6).
Thanks, William.
I agree with D-Fens and hope that the development team is able to keep to the schedule. (I know that is not guaranteed or expected, but I can Hope.)
When the full Repost is posted, will McAfee Installation Designer be released at the same time?
Thanks,
Ron Metzger
MID is not changing in this release so will remain the same. You'll be able to use the current posted MID if you have need to customize the Patch 5 install package.
You are probably already aware but when choosing source files for MID to use, choose our latest full install package and not one that has been modified prior or is an older patch level and the plan was to add in the MSP. MID creates a new .msi file, and keeping that as simple as possible can avoid migration headaches in the future since that .msi file becomes the foundation for any future patches or version upgrades.
I like your optimism Ron. If we have to break the news of changing dates at all I'll try and be gentle. There is always hope .
wwarren wrote:
MID is not changing in this release so will remain the same. You'll be able to use the current posted MID if you have need to customize the Patch 5 install package.
You are probably already aware but when choosing source files for MID to use, choose our latest full install package and not one that has been modified prior or is an older patch level and the plan was to add in the MSP. MID creates a new .msi file, and keeping that as simple as possible can avoid migration headaches in the future since that .msi file becomes the foundation for any future patches or version upgrades.
I like your optimism Ron. If we have to break the news of changing dates at all I'll try and be gentle. There is always hope .
Thanks William,
Wow, no need for a new MID! Cool. I kind of expected with the significant changes that a new MID for VSE 8.8 would be needed. Great. Yes, I am aware of that using the Full Install Package (repost) is needed when creating a new release. I have been doing this, this way, for years.
Thanks,
Ron Metzger
Just a quick note to break the ice -
Patch 5 dates previously mentioned are changing. Our internal deployment of the patch exposed an issue meriting a fix, and the fix needs to be made in our core driver code (which unfortunately carries a large cost for retesting).
I'll update us with new dates once they've been confirmed.
Thank you William, as always..great info and well written.
Zeb
Hi, what will be the new release date? Thanks
We've been working toward these new dates:
Limited availability*: Mar 12
General availability: Apr 09
* Select customers only; the managed release or RTS period, during which the SEO team are closely monitoring the patch's performance/acceptance, thus not open to all customers.
But I share that knowing well the date may change depending on the outcome of an internal investigation for an odd behavior we're still seeking to understand. If anyone asks though, those are the dates to convey... until they're not .
A few additions worth noting since the original post -
Took a week off (still off today actually, back tomorrow) but noticed some new unofficial dates being discussed for our Patch 5 release. Unfortunately that means the March 12 and April 9 dates are no more. I'll catch up on the details later but wanted to give folks the heads up.
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA