Best answer by JGiffardView original
Does anyone have any idea when this version will be released? I know there was a question about how to perform the needed regsitry entry through Webroot but Webroot stated it will automatically add this registry key through this 19 release. Hoping this is going to occur prior to Microsoft's rollup release this week which includes the fix for Meltdown and Scepter.
This topic has been closed for comments
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Full release should be completed by end of January / first week of February.
Senior Product Manager
Within the next week we will also begin release of a new Webroot SecureAnywhere version 9.0.19.xx that,
along with a number of planned enhancements, will also set the registry key automatically.
I was completely relying on this and not us having to deploy commands to change registry entries. If this was not mentioned in that notification I would have planned for our own change deployment.
Ideally there'd be an initial or "RC" rollout that we could opt-in or -out of on a per-site basis, or at least be able to give our clients a solid date. Seems like a rudimentary site-level version-control setting shouldn't be too difficult to implement in the web console (if it's not, the next platform re-design definitely needs to be done with an eye towards greater agility).
I completely agree that this could be automated and it's something that is sitting on the backlog of stuff to do. I'll be looking again at it once we've got a couple of major deliverables done.,
1."Within the next week we will begin releasing a new Webroot SecureAnywhere version 9.0.19.xx that, along with a number of planned enhancements, will also set the REGKEY automatically." [from Jan3 community annoucement]
2. "We’ll be making a series of updates to endpoints under your management starting today. " [Product Updates email 2018-01-17.
3. As of today 2018-01-19 9:30 GMT, I can see no updates in management console, no release notes, no communication in the console apart from a Webthreat shield update alert from Nov 2016.
The community is a great resource, but these important product announcements should be communicated separately, direct from within the GSM, with authority and preferably (refererring/linking to) a single source.
Is there even any malware that takes advantage of the exploit yet? If not, maybe that's the reason why the delivery has been slow. Maybe the patch from MS is garbage and Webroot is waiting it out? It's just weird that it's taken this long.
I know us tech folks hate hearing complaints especially when we have a lot to do already. I'm hoping that the exploit is just rare, yet sensational-- that's why it was all over the news and we're all antsy to make sure our checkbox is checked. I hope that's the case and it's not that Webroot is behind the curve 😞
We've been balacing quality / stabilty / time and monitoring very closely for any signs of malware attempting to use the defects in Intel CPUs.
You'll be pleased to know that the wait is almost at an end. We've completed pre-release testing, fixed a couple of defects and the main rollouts should be commencing this week.