Notice of Bug Fix – Web Threat Shield

  • 15 December 2016
  • 3 replies

Userlevel 7
  • Retired Webrooter
  • 1460 replies
From Thursday, December 15, 2016, Webroot will roll out a new WSA Web Threat Shield plugin, version to address a known defect.
This release addresses a sporadically occurring defect in which Webroot Enhanced Web Threat Shield binaries were repeatedly marked to be deleted with the next Operating System restart. In some cases, this caused installers/uninstallers to function incorrectly.

  • The Installation will occur silently if automatic updates are enforced for your Webroot deployment.
  • A restart of the machine is required to complete deployment.
Note: Webroot SecureAnywhere agents will receive the updated plugin on their defined poll interval.  Agents can be forced to obtain the plugin immediately by:
  • Right-clicking the agent in the system tray and selecting "Refresh Configuration" OR
  • Running the command line “<path to executable>wrsa.exe –poll”. For example: "c:program fileswebrootwrsa.exe" -poll
Webroot apologizes for any inconvenience caused by this defect. Please contact Support if you continue to see installer/uninstaller errors following successful deployment of this plugin. 

3 replies

Userlevel 7
Badge +30
Hey @
How do we verify we have this latest version? Does this fix any issues with webpages not loading properly with Google Chrome?? This is still an ongoing issue.
Nerds On Site
Userlevel 4
Badge +9
Hi @,
You can view the latest version and release notes either via the Community at, or from your GSM Console, if you drill down to the site level, and select the Status tab, there is a link at the bottom right of the screen that reads Release Notes under News and Updates. If you click there you will be taken to, which will show you the current versions of our different products, including the WSAB agent.
Regarding your issue with Google Chrome not loading pages properly, I would like to reach out to you through our ticketing system to get some further insight as to what is going on, and get you a solution.
Best regards,
Joseph R.
This new update fix is great, thanks a lot! 🙂