Discussion in 'other anti-virus software' started by Triple Helix, Jun 6, 2014.
New Beta now out to Beta testers v188.8.131.52
Thank you Triple Helix
Well TH, Webroot has been caught this time for resting a bit too long on their laurels concerning their support for Microsoft Cumulative Update KB4056892, which includes support for Meltdown ONLY IF the system is running an antivirus that has specific registry keys allowing the update to occur. I have successfully installed this latest update released today on systems running WD, Avira, and ESET, but sadly Webroot currently is NOT compatible with KB4056892 at the present time. I understand fully the whole situation, but my customers are NOT pleased at all.
According to Kevin Beaumont's list of anti-virus products that have been updated, the auto registry key setting is due next week.
And we are testing the Beta as we speak: https://www.wilderssecurity.com/thr...on-update-thread.364655/page-141#post-2729206
@kdcdq See this: https://answers.webroot.com/Webroot/ukp.aspx?pid=12&app=vw&vw=1&login=1&json=1&solutionid=2837
Much needed and even more appreciated TH. The documented process works like a charm!
I had seen a similar registry hack published by Bleeping Computer; IF you apply either of these two registry edits AND you don't have an AV compatible with KB4056892, the result is permanent BSODs at boot.
Hopefully what you mean is that if you don't have at least one AV compatible with KB4056892 then the result is permanent BSOD. Some WR users use other AV programs on demand (eg I use MB and WD), if someone uses an incompatible AV like F-Prot alongside WR and applies this patch, will they be in trouble?
By the way, the update process on my machine took an uncomfortably long time; after installing the update and rebooting, it sat with a black screen and the HD chugging away for far longer than I can recall with any other update. I was pretty close to getting out my recovery disks before the desktop reappeared. Just a warning for anyone who hasn't done this yet.
An excellent question d_r, and one to which I am not fully versed on. However, as I currently understand how KB40506892 works, the BSODs are a result on a resident active AV not compatible with running the MS patch but attempting to do so. An on-demand-only system is not actively scanning for malware, so it is my understanding this scenario is OK.
It is getting to the point that the time involved in installing one of these massive Microsoft cumulative updates justifies the cost of a SSD all by itself. I have 7 Windows 10-based systems currently and have replaced the primary hard drive in ALL of them with a SSD. Total install time of an update like KB40506892 is typically less than 5 minutes now.
I got this after booting up this morning, running beta and Win 7. I allowed.
Version 184.108.40.206 (Released January 9th, 201
Enables Registry key to allow Microsoft’s Jan 3rd Update.
Improvements to agent upgrade process.
Reduce occurrence of false positive detection of Windows 10 rootkits.
Multiple bug fixes.
Webroot now utilizes a gradual rollout method for releases. As such, not all users will receive this update at the same time.
Just resently got the latest version update which include the added reg-key - and suddently when I boot up my win 7 system some two hours ago, the system could not boot longer than to the welcom-window.
I tryed several times with same results, and after that I activaded safe mode and shot down and uninstalled wsa, and then when I boot up as usual in normal mode, the system was back to normal again - lucky me!
Now I am not sure if I dare to install my dear wsa again ?
I just unchecked auto update on WSA so i don't get the new reg key anytime soon.
I guess it`s to late for me to do that, as the latest update seems to include this new added reg-key
I have reported it to the Webroot Beta Group.
This also happened to me except with Windows 10. I had to reinstall my OS because I couldn't get Windows back even in Advanced boot up screen. It would only boot up to a plain black screen. I did reinstall Webroot after instalingl Windows because I didn't think it was all related until troubleshooting in my head and help from a friend @Triple Helix when conversing over all of this when this was happening..while doing a clean reinstall. All is great now.
I have reported it to the Webroot Beta Group. - Thank you Triple Helix
I have opened a ticket about the issue with the support team, and hopefully they have some advice.
Great and please share what they have to say!
Thanks for the info. I didn't know that was an option, but since I haven't received the update yet (on Windows 7), I unchecked it too & will monitor this thread.
I should have unchecked it days sooner, but thought it could do no harm so i let it go until another wsa user had a big problem after the new update. I don't plan on installing the ms update anyway, so i don't really need the reg key.
v220.127.116.11 is now out to Beta testers.
As always, a big THANK YOU for the heads-up TH!
Well as for me, the short story is, that for now I am back to the 18.104.22.168 build wich the support team kindly has provided me, until they find the cause and the solution to this boot issue.
Separate names with a comma.