We are aware of the frustrations and Threat, QA and Engineering are all working diligently to fix this ASAP.

We do sincerely apologize for the delay, and absolutely understand the impact this has on our customers

I’ll leave it to @ChadL to update once we have finished testing and released the fix for this - as soon as it’s ready. 

Not sure what to do about this! Reading all the updates above on this thread and don't see an end in sight on the resolution and ETA for the updated fix or new protection file to avoid what apparently Webroot is blaming Apple on. Apparently NO way of clearing this and this is a paid subscription that was to be a better model to protect our data. Not sure why the latest definitions aren't being matched or loaded .. scan, scan scan and nothing different! 

Good news everyone,

There was an issue with our definitions being published properly, but that has been resolved. The latest definitions of 1623 contains the exclusions for MRT v3 and your agents should receive the updates automatically. On the next scan you should not see the MRT v3 being shown as a threat so long as you didn’t take action to quarantine the item. Let me know if you see any other issues.

We apologize for the delay in getting this out and we’re actively having conversations on how to improve this pipeline to minimize delays. As with all things, improvements take time, but we are doing our best to meet and exceed your expectations and I appreciate your feedback in helping us improve our product for you. 

The problem with 1000s of end users reporting same problem is it take resources away from solving the problems.  Reporting this method  is more efficient, but it is sad that a little time couldn’t be taken to: develop and proactively publish an intermediate fix to all users; provide status update here and to all users at Noon and COB each day. 

Not really support takes the info in and they share with Development and then QA and in this case @ChadL said they pushed out a new definition set “1623 contains the exclusions for MRT v3” that will solve this issue. 

Thanks Chad

Setting aside Webroot Mac team should have been on top of this before 12.3 was released, Webroot needs an experienced Lean Six Sigma process person who is empowered to makes changes that improve customer experience.  So often Webroot is slow to respond when prior planing would have proactively fixed the problem

I wonder where one could see what version definitions set they have?
I see 1623 is the up-to-date version, but where can I tell I have it?
 

I suppose simply by restarting the computer and/or Webroot SecureAnywhere program, that should load the update. Also, if I’m not getting the false positive, that, too, would let me know.
I just want to be 100% sure. 

Hello @WaltDittrich 

I don’t use the Mac version but if you look at the product version then the last 4 digits would show the definition update version under my account in the UI! Something like this: 9.5.0.139:1623 or a higher number.

https://docs.webroot.com/us/en/home/wsa_mac_userguide/wsa_mac_userguide.htm#ManagingYourAccount/ViewingYourAccountDetails.htm

HTH,

Thank you, TripleHelix,

It simply shows the version number:
 

However, as of today, the false positive error is no longer appearing, so I guess I’m good.

Thank you!

Thank you, TripleHelix,

It simply shows the version number:
 

However, as of today, the false positive error is no longer appearing, so I guess I’m good.

 

Thank you!

I don’t know the Mac client very well maybe @ChadL can explain. Can you also tell us which version of the Mac OS you are using?

Thanks,

@WaltDittrich 
If you go here 

Then here: 
 

You should see a window like this: 

This is also a reliable way of viewing the version number and subsequent definitions number. Are you by any chance on a managed computer? 

Thanks Chad!