New Bug Spybot 2.9 : Gets stuck when scanning for zoom player

Q

Question2

New member
Ive tried this multiple times, when i do a system scan, it gets stuck at 99.9% scanning for zoom player and the code it displays is 49804B54. It never progresses past this point to complete the scan even after 40 minutes. Clicking "stop" does nothing and i have to close the entire scan window to get it to stop. I can pause the scan, but once paused i am unable to resume it. No log file for the scan is created.

If i click "show details", i get an empty details screen but i keep getting spammed with a popup message saying that spybot has run out of resources, which does not make sense as it is only using 3+gb of memory and i have 32 GB of RAM on this system...and task manager shows that i have plenty of spare ram available. CPU usage averages about 15%.

Strangely, i cannot use print screen to take a screenshot of spybot either, it does not copy the screen to the clipboard when i use print screen.
 
Last edited:
PepiMK said:
What have you get set up as "Downloads directories" in settings?

Taking screenshots should be possible using the Windows Snipping Tool.
Click to expand...
No entries in download directories.

I went into "Categories", unticked "Cookies.sbi" and "Tracks.uti" and was able to finish the scan.
 
Just tried to run another system scan. Now it gets stuck on 4E2AF2A..."view details" just complains it has run out of resources...

Edit : Tried again, this time with "view details" opened from the beginning. This time i got a popup saying "runtime error 203 at 479070F3".
 
Last edited:
Do you have any other security programs running real time protection that could be interfering with the System Scan? If so, please disable them, then try to run another scan.
 
I reported this problem in April 2023 (see Ticket#2023040680000137).

I didn't get a solution, just the usual blather about needing to run as an administrator.

There seem to be similar problems reported in
and possibly other threads if you go back further.

Is that enough for Spybot to have a proper look at this?

I don't know if I still have an issue. I just stopped doing full scans with Spybot.
 
My apologies for the delay in responding to your forum post.

We are currently looking into this, and I am reviewing the previous support ticket you mentioned, and I will report back to you ASAP with more information and a possible solution to this.
 
You must log in or register to reply here.
Back
Top