How can I make sure OPSWAT Client is completely removed from my endpoint?

Once you have uninstalled OPSWAT Client using the instructions in How do I remove OPSWAT Client from my device?, you can validate that its completely uninstalled and all components have been removed. In rare cases, a component might still exist which you will need to remove manually, as described here:

For Windows 32-bit or 64-bit

  • Check task manager and make sure the processes related to OPSWAT Client do not appear. If any of them remain, right-click and select 'End Process'

    • waodwd.exe

    • wabpoes.exe

    • wabpmsn.exe

    • GearsHelper.exe

    • GearsAgentService.exe

    • wa_3rd_party_host_32.exe

    • GearsInstaller.exe

    • GearsSdkInstaller.exe


  • Check services.msc and make sure the three services related to OPSWAT Client do not appear.


    If any of them still show, open a command-prompt as Administrator, run the appropriate command:
    - sc delete opswatgearshelper
    - sc delete waondemand

  • Once you have confirmed there are no OPSWAT Client services running, go to "C:\Program Files (x86)\OPSWAT" ('Program Files' on 32-bit) and delete folders related to OPSWAT Client if they exist:
    - "GEARS Client"
    - "OnDemand"
    - "GEARS Client.bak"

  • Delete the following folder:
    - "C:\ProgramData\OPSWAT\Gears"

  • Delete the following registry keys (omit 'Wow6432Node' on 32-bit systems)

  • (Optional) Search the registry for other keys with the word OPSWAT and remove them

  • Restart the machine

For OS X/macOS

  • Check “Activity Monitor” and make sure processes related to OPSWAT Client (MetaAccess, opswat-gears-od, GearsCLI, GearsHelper) do not appear

  • If one of processes still remains, do the following:

    • Go to "/Library/Preferences/SystemConfiguration” and delete .plist file "com.opswat.gearsagent.plist" if it exists

    • Go to "/Library/LaunchDaemons" and delete any files related to OPSWAT Client (com.opswat.GearsCLI.plist; com.opswat.GearsHelper.plist; com.opswat.GearsUpdater.plist)

  • Restart the machine

This article was last updated on 2019-11-20