Fix for recent Spybot AV update error (updated 2nd Feb 2017)

Some users have reported that they are unable to download the most recent antivirus updates for licensed versions of Spybot. Instructions to fix this issue can be found below.

For users experiencing issues installing malware signatures or updating the Free Edition of Spybot; a list of more common updating issues can be found here.

Download and install our new updater:

Our technicians have created a new Update Test Tool that should be able to diagnose any AV update issues that may occur.

You can download it from here, or using the link below:

https://download.spybot.info/Spybot2/special-purpose-test-versions/sd2-4022-updater-error-2005/SpybotAVUpdateTestTool-v0.8.exe

Please run the installer by right-clicking the file and choosing the option to “Run as administrator”.

The Test Tool will then proceed to download and install the AV updates, or report any errors if it is unable to do so. Please allow the Test Tool run until the very end, which may take a couple of minutes.

Once the tool has finished running, you can then try to update Spybot again.

  • Open Spybot by right clicking on the Spybot icon and click “Run as Administrator”.
  • Tick the checkbox next to “Advanced User Mode”, if this is unticked.
  • Click on “Update”.
  • In the update window that appears, click “Update” to install the latest updates.

We apologise for the inconvenience, and we thank you for your patience in resolving this issue.

If you are still experiencing issues with updates or receive an error message from the tool, please take a screenshot of this window and attach it to an email to our support team.

See the following links for more information on how to take a screenshot:

http://www.take-a-screenshot.org
http://windows.microsoft.com/en-ie/windows/use-snipping-tool-capture-screen-shots#1TC=windows-8

This will allow us to better understand the issue that is causing the update failure which will enable us to come up with a permanent solution, if the initial fix does not solve the issue.

We apologise for any inconvenience, and we thank you for your patience in resolving this issue.