If I install the official last 220.127.116.11 wsasme.msi on Mac Book Pro Bootcamp with Windows 10 Version 1803 (Build 17134.48) all is fine till Webroot Secure anywhere goes to take the update to 18.104.22.168. Webroot disapears because Windows blocks the Application. Also in Processes you'll don't find anything about wrsa.
Same Problem since a long time and webroot doesn't make anything since a long time. And yes I've spent allready a long time with > support Ticket > online support on the Pc > some time .... with no result at the end.
I just wanted to comment that we also have this issue in our environment. When I saw your comment I remembered that we also had a MacBook Pro running Boot Camp with Windows 10 Version 1803, and wanted to see if the beta would work on it. Well, it didn't, and to make things worse, we couldn't go back to the previous version either, at least not the way we normally install it. We had to install the current version (22.214.171.124) from the command line using these switches '/silent /noupd'.
We've had this issue before on this machine, and it was a nightmare trying to work with Webroot Support. We had the case open for a little over a year and they couldn't get Webroot installed on this machine. After about 2-3 months of the case being open, we stopped getting any communication from Support and I had to keep checking in from time to time to see if they had a fix so we could get Webroot installed on this machine - nothing... until a little over a year later we get the Fall Creators Update installed on this machine and somehow magically we were able to get Webroot installed on there. Because of this experience, we were considering switching to another AV.
I'm also hesitant to write Support because of the nightmare we had with this issue last time. I wrote @JGiffard in the Beta group for the Business Community here - https://community.webroot.com/t5/WSA-Release-Candidate-PC-Group/Now-available-WSA-9-0-20-XX-BETA/gpm...
I'm hoping he can pass this info to the devs so that we don't have to go through another painful Support experience.
Thanks for your explanation of the same situation about Mac Book Pro and Webroot. Nearly the exact same situation than here.
I found out this weekend, that if you take the last wsasme.msi, you can make a right click on it and choose DEINSTALLATION and that is the easiest way.
The support team reopened my case. See what happens. Also be a member now for beta group. Let's see.
And by the way: we have much installations and often we have a win10 that has no webroot on it that it was there yesterday.
@Webgroot, we typically send the email out a couple of weeks in advance, and then post to the Community when the release starts.
I'm dissapointed to report that the majority of our users received this version (126.96.36.199), and we did not receive any prior email notification.
I hear you @Webgroot, and will share your feedback with the team.
Looks like we are about 60%-70% updated and I also did not get any email about the update. The only reason I knew about it was from being subscribed to the announcements in the forum.
I beleive that I am seeing the same thing. I do not recollect having rec'd an email alerting of the update to my client base specifially.
It has happened in this manner previously (no notification, auto updating to current release) which appears to be what I am experiencing now.
Thank you so much for raising this.
I'm a product marketing manager here at Webroot, and improving the capture rate for our Product Bulletins is one of my pet projects. I've made several changes to the process, including how we pull data for the email send, but there is clearly still some room for improvement.
You should be receiving an email a week or two prior to updates from ProductUpdates@webroot.com. We have seen issues in the past where spam filters catch the email and move it to a different folder (not always spam). Gmail-based email systems and those using Barracuda seem to have the most trouble receiving our updates.
If you haven't been receiving the emails, and feel like you should have, please DM me your email address, and I'll look into it further.
And, thank you for helping us improve our communication flow.