Webroot has identified a Reaper update as a threat. The only way I can tell that this was what it identified as a threat is by looking in the online console, as it is not in quarantine. Webroot is red and angry about this Reaper update, but it's not a bad thing. I also went to system control, and I don't see it listed there either.
Copy pasted:
Sep 4, 2015 6:11REAPER501_X64-INSTALL.EXE Pua.Mypcbackup
Sep 4, 2015 6:10REAPER50_X64-INSTALL.EXE Pua.Mypcbackup
These are both Reaper updates that I downloaded, from the safe trusted source. The updates are already applied, and Webroot didn't think anything of them until days/weeks later (just today), so I don't really need them anymore, but I sure would like Webroot to not think I deleted them because they were bad, and there's going to be a problem if Webroot detects the next Reaper update as a threat, because Reaper updates quite frequently.
Website for Reaper:
http://www.reaper.fm/
Hello there, welcome to the Community!
As for why Webroot decided to identify the files well after they were downloaded and installed, quite simply there was most likely a change in the classification of the said files within the Cloud. This can happen. Since you no longer need those specific files, it is not really worth 'rescuing' them, but we do need to bring it to Webroot's attention to correct the definition of those specific files in the Cloud, and also try to make sure future updates are not affected.
Please submit a Trouble Ticket to have Webroot Support take a look at things, as they are the only way to have the classification in the Cloud changed. There is no charge for their services, it is provided as a part of your valid WSA license.
As for why Webroot decided to identify the files well after they were downloaded and installed, quite simply there was most likely a change in the classification of the said files within the Cloud. This can happen. Since you no longer need those specific files, it is not really worth 'rescuing' them, but we do need to bring it to Webroot's attention to correct the definition of those specific files in the Cloud, and also try to make sure future updates are not affected.
Please submit a Trouble Ticket to have Webroot Support take a look at things, as they are the only way to have the classification in the Cloud changed. There is no charge for their services, it is provided as a part of your valid WSA license.
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.