• Welcome Guest, to the Spybot Forums! It's 2025, and we just upgraded our forum software.

    Today is Safer Internet Day, and with our new forum, you can finally use passkeys to login. That was about time!

    Of course, you could ask if a forum is still useful, with so many social media networks out there where you might already have an account, and met a lot of users. You can now use your login from some of those networks to log in here. And by posting here, your question and data is stored on our servers and not automatically shared with a whole social media network.

    We'll also start using the forum for small bits of information, announcements and more again.

Scan completes too quickly

free2rhyme

New member
After I run "check for problems" and it starts scanning, the scan gets completed in no time...as less as 10 seconds and the result is
"Congratulations. No immediate threats were found".

Is this correct? I am not sure if it supposed to complete the scan this quickly. Is it even doing anything?:confused:

Please let me know!!

Thanks
free2rhyme
 
Exit Spybot, restart Spybot and try the scan again.

If that fails to help:

Did you update after installing and before attempting a scan?
  • Go into Spybot > Update.
    • Click "Search for Updates" .
    • Check everything found.
    • Click "Download Updates".
Did you exit and restart Spybot after the updates and before scanning?

If you have the latest updates, go into Spybot > Mode > Advanced mode (say "Yes" to the warning if necessary) > Settings > File Sets. Make sure that everything is checked except the possibly the last two items. The last two items are "Usage Tracks" and should only be checked if you want to check for them (I personally don't). The first of these two items (Usage Tracking) lists IE Cache (temporary internet files), Common Dialogs, Cookies and some Logs. The second is other "Usage Tracks".

If you still have a short scan time, download and install the updates manually as follows:
If all of the above fail to correct the problem:

Uninstall Spybot-S&D 1.4:
  • Go to Windows > Control panel > Add or Remove Programs > Locate "Spybot – Search & Destroy 1.4" > Remove.
  • Using Windows explorer, verified that the following folder has been delete. If not, delete it:
    • C:\Program Files\Spybot - Search & Destroy
  • Make sure that all the registry entries that Spybot-S&D added during installation are removed, there is a .reg file available on the safer-networking.org WEB site that can do that. See the following article:
  • Delete the Configuration.ini file
    • The Configuration.ini file is stored in one of the following folders:
      • Windows 95 or 98:
        C:\Windows\Application Data\Spybot - Search & Destroy
      • Windows ME:
        C:\Windows\All Users\Application Data\Spybot - Search & Destroy
      • Windows NT, 2000 or XP:
        C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy
Reinstall Spybot-S&D 1.4:
  • Execute the spybotsd14.exe installation program again.
  • Do not change the default installation path of:
    • C:\Program Files\Spybot - Search & Destroy
  • If you did not update during the installation, make sure that you update before running a scan, as follows:
    • Go into Spybot > Update
    • Click "Search for Updates"
    • Check everything found
    • Click "Download Updates"
 
Complete?

Hello!

First, I must congratulate you. Spybot is the best program!

Well, I have a doubt:
Settings > File Sets. Everything is checked except the last two items.
I Start the "check for problems" and everything goes ok. There is a number that grows up:

spybothi0.jpg


This number reach 362000 (perhaps a little more because it runs very fast), but after that it jumps to 41952. Scan gets completed and Spybot tells ther are not threats. Do you understand me? It jumps from 36200 to 41952 and I cant see the 37,38,39,40 thousand... . Is this normal?

Thanks.
 
Last edited:
Lupin:

Is this normal?
Yes.

The jump is the scan count that you observed is not really a problem and is not related to the actual problem that free2rhyme was describing when they started this thread (topic).

Although the following thread is over seven (7) months old, so the scan count numbers are different now, it should help explain the cause of the jump in the scan counts that you are observing:
 
Back
Top