View Full Version : Spybot Home crashed during system cleanup while "Fixing Selected Problems"
I did a full scan of my entire system. Spybot Home found quite a lot of stuff. However, when I attempted to "fix problems" it took an unusual amount of time and then crashed, forcing me to end the process. I attached a screenshot for reference.
Has anyone else had this problem?
Try not scanning for tracks,then fixing.
Open Spybot start center,checkmark Advanced User Mode.Click Settings(say yes to the UAC prompt,if applicable),then the categories tab.Somewhere within the window underneath Malware Detection,rightclick and select Spyware Scan Only,then click Apply and OK.
That's just to cut down on some of the stuff being found for now,to see if the scan will complete without getting 'Not Responding'.You can turn tracks back on afterwards,if you like. :)
Try not scanning for tracks,then fixing.
Open Spybot start center,checkmark Advanced User Mode.Click Settings(say yes to the UAC prompt,if applicable),then the categories tab.Somewhere within the window underneath Malware Detection,rightclick and select Spyware Scan Only,then click Apply and OK.
That's just to cut down on some of the stuff being found for now,to see if the scan will complete without getting 'Not Responding'.You can turn tracks back on afterwards,if you like. :)
The scanning completed just fine, it crashed while trying to delete the found items. Don't I want to continue check for malware?
That's just to cut down on some of the stuff being found for now,to see if the scan will complete without getting 'Not Responding'.You can turn tracks back on afterwards,if you like.
Sorry,I meant to say "see if the fixing would complete",not the scan. :)
Selecting "Spyware Scan Only" will let Spybot continue to search for malware.
Taking tracks off for the time being will cut down on the number of items being found after a scan,which will cut down on the number of items being fixed,which might allow the fixing to complete,since the "Not Responding" message might be happening if there is a lot of things to fix.Tracks aren't malware,so it's ok to not scan for them during one scan to see if it will complete,it will do no harm,and I can help you set Spybot to look for them again afterwards.This one scan is just a test,to kind of try to see what might be happening,as it were.
Sorry,I meant to say "see if the fixing would complete",not the scan. :)
Selecting "Spyware Scan Only" will let Spybot continue to search for malware.
Taking tracks off for the time being will cut down on the number of items being found after a scan,which will cut down on the number of items being fixed,which might allow the fixing to complete,since the "Not Responding" message might be happening if there is a lot of things to fix.Tracks aren't malware,so it's ok to not scan for them during one scan to see if it will complete,it will do no harm,and I can help you set Spybot to look for them again afterwards.This one scan is just a test,to kind of try to see what might be happening,as it were.
Okay cool. Sorry for the confusion. I tried it this morning and it seemed to work. It might just have been moody. I'll let you know if I have any other problems. Thanks!!
Hello Zenobia,
I was going through this thread since I´m having the same problem...I followe dthe steps you mentioned above, but nothing happened, my system still freezes when I try to clean the detections (26 in total high level of threat), and after a while I get the following error message
"Failed to set data for ´Spybot-S&D Cleaning´"
Hpe you can help me
Thanks in advance
When you open Spybot S&D Start Center,what version of Spybot is listed in brackets at the top? :)
Zenobia,
Besides having the latest version updated, I run it with administrator privileges.
Hope you can help me with this since everytime I get more threats detected
Thanks :)
I've never seen the "Failed to set data for ´Spybot-S&D Cleaning" error before,either here or anywhere else,and can find no information on it.So I'm not sure on the error.
But on sdcleaner itself,this is in the help file:
The Cleaner module can remove malware where other approaches sometimes fail. On reboot it can clean using previous scan results eliminating the need to scan again. It can also use other cleaning mechanisms like the new WinLogon and Native Mode cleaners
So from that and you saying that the 26 listed originally are high threat,I think it's possible that there might be some malware Spybot is stumbling on,and attempting to use the cleaner to remove it.
So,could you open Spybot start center,click Report Creator,then click Show Logs over to the right,scroll down and find a Checks.logfile with a date at the end of it where you know you got the error. :)
For an example,a checks logfile from yesterday would look like this:Checks.140725-1755.txt.
Double click the Checks logfile you've chosen,go to Edit,Select All,then right click somewhere in the document and select Copy,then paste it here.
I am having the same issue. Spybot goes into "not responding" mode when I try to :fix selected problems" I am only ding a quick scan lasting around 20mins.
This renders Spybot useless. Using Spybot Search & Destroy + AV2.3. I have unticked both the Fixed and Optical drives under the "scan with different options" box.
Suggestions will be appreciated.
Did you set up the quick scan through the categories tab?If so,which one did you select? :)
Under scan with different options,do you have two drives listed under Fixed?
Hi Zenobia and thanks for your response. You will realise I am a novice at this so I will appreciate your patience.
I do not see a categories tab.
I click on the System Scan icon, which starts a scan immediately. I have to stop that scan in order to get to "scan with different options" in the drop-down box attached to Stop Scan.
I then have two options, Fixed C drive or Optical D drive. I have selected neither of them.
thanks,
Sevenoh
You're welcome. :)
Ok,the categories tab is in Spybot's Settings,I was after seeing if you had set up anything for the Spybot scan to run quicker there.No need to look at it at the moment.
You probably should keep your C:\ drive selected when you scan since it's your main drive,but you could just leave the optical drive unchecked.
How about you post a Checks logfile?
Please open Spybot start center,click Report Creator,then click Show Logs over to the right,scroll down and find a Checks.logfile with a recent date roughly around the time the fixing has been freezing.
For an example,a checks logfile from a few days ago would look like this:Checks.140725-1755.txt.
Double click the Checks logfile you've chosen,go to Edit,Select All,then right click somewhere in the document and select Copy,then paste it here.
You're welcome. :)
Ok,the categories tab is in Spybot's Settings,I was after seeing if you had set up anything for the Spybot scan to run quicker there.No need to look at it at the moment.
You probably should keep your C:\ drive selected when you scan since it's your main drive,but you could just leave the optical drive unchecked.
How about you post a Checks logfile?
Please open Spybot start center,click Report Creator,then click Show Logs over to the right,scroll down and find a Checks.logfile with a recent date roughly around the time the fixing has been freezing.
For an example,a checks logfile from a few days ago would look like this:Checks.140725-1755.txt.
Double click the Checks logfile you've chosen,go to Edit,Select All,then right click somewhere in the document and select Copy,then paste it here.
Hi,
I've been having this freezing problem for a few weeks.
following the instructions you gave above this is the result from today:
Search results from Spybot - Search & Destroy
3/1/2015 1:15:47 PM
Scan took 00:30:15.
10 items found.
DoubleClick: [SBI $4E2AF2AC] Tracking cookie (Google Chrome: Default) (Browser: Cookie, nothing done)
MS Direct3D: [SBI $C2A44980] Most recent application (Registry Change, nothing done)
HKEY_USERS\.DEFAULT\Software\Microsoft\Direct3D\MostRecentApplication\Name
MS Direct3D: [SBI $C2A44980] Most recent application (Registry Change, nothing done)
HKEY_USERS\S-1-5-21-424430542-4288655023-261787936-1000\Software\Microsoft\Direct3D\MostRecentApplication\Name
MS Direct3D: [SBI $C2A44980] Most recent application (Registry Change, nothing done)
HKEY_USERS\S-1-5-18\Software\Microsoft\Direct3D\MostRecentApplication\Name
Windows: [SBI $1E4E2003] Drivers installation paths (Registry Change, nothing done)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Installation Sources
Windows: [SBI $1E4E2003] Drivers installation paths (Registry Change, nothing done)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Installation Sources
Windows Explorer: [SBI $D20DA0AD] Recent file global history (Registry Key, nothing done)
HKEY_USERS\S-1-5-21-424430542-4288655023-261787936-1000\Software\Microsoft\Windows\CurrentVersion\Explorer\RecentDocs
Cache: [SBI $49804B54] Browser: Cache (12) (Browser: Cache, nothing done)
Cookie: [SBI $49804B54] Browser: Cookie (3222) (Browser: Cookie, nothing done)
History: [SBI $49804B54] Browser: History (5297) (Browser: History, nothing done)
--- Spybot - Search & Destroy version: 2.4.40.131 DLL (build: 20140425) ---
2014-06-24 blindman.exe (2.4.40.151)
2014-06-24 explorer.exe (2.4.40.181)
2014-06-24 SDBootCD.exe (2.4.40.109)
2014-06-24 SDCleaner.exe (2.4.40.110)
2014-06-24 SDDelFile.exe (2.4.40.94)
2013-06-18 SDDisableProxy.exe
2014-06-24 SDFiles.exe (2.4.40.135)
2014-06-24 SDFileScanHelper.exe (2.4.40.1)
2014-06-24 SDFSSvc.exe (2.4.40.217)
2014-06-24 SDHelp.exe (2.4.40.1)
2014-04-25 SDHookHelper.exe (2.3.39.2)
2014-04-25 SDHookInst32.exe (2.3.39.2)
2014-04-25 SDHookInst64.exe (2.3.39.2)
2014-06-24 SDImmunize.exe (2.4.40.130)
2014-06-24 SDLogReport.exe (2.4.40.107)
2014-06-24 SDOnAccess.exe (2.4.40.11)
2014-06-24 SDPESetup.exe (2.4.40.3)
2014-06-24 SDPEStart.exe (2.4.40.86)
2014-06-24 SDPhoneScan.exe (2.4.40.28)
2014-06-24 SDPRE.exe (2.4.40.22)
2014-06-24 SDPrepPos.exe (2.4.40.15)
2014-06-24 SDQuarantine.exe (2.4.40.103)
2014-06-24 SDRootAlyzer.exe (2.4.40.116)
2014-06-24 SDSBIEdit.exe (2.4.40.39)
2014-06-24 SDScan.exe (2.4.40.181)
2014-06-24 SDScript.exe (2.4.40.54)
2014-06-24 SDSettings.exe (2.4.40.139)
2014-06-24 SDShell.exe (2.4.40.2)
2014-06-24 SDShred.exe (2.4.40.108)
2014-06-24 SDSysRepair.exe (2.4.40.102)
2014-06-24 SDTools.exe (2.4.40.157)
2014-06-24 SDTray.exe (2.4.40.129)
2014-06-27 SDUpdate.exe (2.4.40.94)
2014-06-27 SDUpdSvc.exe (2.4.40.77)
2014-06-24 SDWelcome.exe (2.4.40.130)
2014-04-25 SDWSCSvc.exe (2.3.39.2)
2014-05-20 spybotsd2-install-bdcore-update.exe (2.3.39.0)
2014-07-31 spybotsd2-translation-esx.exe
2013-06-19 spybotsd2-translation-frx.exe
2014-08-25 spybotsd2-translation-hux2.exe
2014-09-10 spybotsd2-translation-nlx.exe
2014-10-01 spybotsd2-translation-nlx2.exe
2014-11-05 spybotsd2-translation-ukx.exe
2014-08-17 unins000.exe (51.1052.0.0)
1999-12-02 xcacls.exe
2012-08-23 borlndmm.dll (10.0.2288.42451)
2012-09-05 DelZip190.dll (1.9.0.107)
2012-09-10 libeay32.dll (1.0.0.4)
2012-09-10 libssl32.dll (1.0.0.4)
2014-04-25 NotificationSpreader.dll
2014-06-24 SDAdvancedCheckLibrary.dll (2.4.40.98)
2014-04-25 SDAV.dll
2014-06-24 SDECon32.dll (2.4.40.114)
2014-06-24 SDECon64.dll (2.3.39.113)
2014-06-24 SDEvents.dll (2.4.40.2)
2014-06-24 SDFileScanLibrary.dll (2.4.40.14)
2014-04-25 SDHook32.dll (2.3.39.2)
2014-04-25 SDHook64.dll (2.3.39.2)
2014-06-24 SDImmunizeLibrary.dll (2.4.40.2)
2014-06-24 SDLicense.dll (2.4.40.0)
2014-06-24 SDLists.dll (2.4.40.4)
2014-06-24 SDResources.dll (2.4.40.7)
2014-06-24 SDScanLibrary.dll (2.4.40.131)
2014-06-24 SDTasks.dll (2.4.40.15)
2014-06-24 SDWinLogon.dll (2.4.40.0)
2012-08-23 sqlite3.dll
2012-09-10 ssleay32.dll (1.0.0.4)
2014-06-24 Tools.dll (2.4.40.36)
2014-03-05 Includes\Adware-000.sbi (*)
2014-01-08 Includes\Adware-001.sbi (*)
2015-02-25 Includes\Adware-C.sbi (*)
2014-01-13 Includes\Adware.sbi (*)
2014-01-13 Includes\AdwareC.sbi (*)
2010-08-13 Includes\Cookies.sbi (*)
2014-11-14 Includes\Dialer-000.sbi (*)
2014-11-14 Includes\Dialer-001.sbi (*)
2014-01-08 Includes\Dialer-C.sbi (*)
2014-01-13 Includes\Dialer.sbi (*)
2014-01-13 Includes\DialerC.sbi (*)
2014-01-09 Includes\Fraud-000.sbi (*)
2014-01-09 Includes\Fraud-001.sbi (*)
2014-03-31 Includes\Fraud-002.sbi (*)
2014-01-09 Includes\Fraud-003.sbi (*)
2012-11-14 Includes\HeavyDuty.sbi (*)
2014-11-14 Includes\Hijackers-000.sbi (*)
2014-11-14 Includes\Hijackers-001.sbi (*)
2014-01-08 Includes\Hijackers-C.sbi (*)
2014-01-13 Includes\Hijackers.sbi (*)
2014-01-13 Includes\HijackersC.sbi (*)
2014-01-08 Includes\iPhone-000.sbi (*)
2014-01-08 Includes\iPhone.sbi (*)
2014-11-14 Includes\Keyloggers-000.sbi (*)
2014-09-24 Includes\Keyloggers-C.sbi (*)
2014-01-13 Includes\Keyloggers.sbi (*)
2014-01-13 Includes\KeyloggersC.sbi (*)
2014-11-14 Includes\Malware-000.sbi (*)
2014-11-14 Includes\Malware-001.sbi (*)
2014-11-14 Includes\Malware-002.sbi (*)
2014-11-14 Includes\Malware-003.sbi (*)
2014-11-14 Includes\Malware-004.sbi (*)
2014-11-14 Includes\Malware-005.sbi (*)
2014-02-26 Includes\Malware-006.sbi (*)
2014-01-09 Includes\Malware-007.sbi (*)
2015-02-25 Includes\Malware-C.sbi (*)
2014-01-13 Includes\Malware.sbi (*)
2013-12-23 Includes\MalwareC.sbi (*)
2014-11-14 Includes\PUPS-000.sbi (*)
2014-01-15 Includes\PUPS-001.sbi (*)
2014-01-15 Includes\PUPS-002.sbi (*)
2015-02-25 Includes\PUPS-C.sbi (*)
2012-11-14 Includes\PUPS.sbi (*)
2014-01-07 Includes\PUPSC.sbi (*)
2014-01-08 Includes\Security-000.sbi (*)
2014-01-08 Includes\Security-C.sbi (*)
2014-01-21 Includes\Security.sbi (*)
2014-01-21 Includes\SecurityC.sbi (*)
2014-11-14 Includes\Spyware-000.sbi (*)
2014-12-10 Includes\Spyware-001.sbi (*)
2015-01-14 Includes\Spyware-C.sbi (*)
2014-01-21 Includes\Spyware.sbi (*)
2014-01-21 Includes\SpywareC.sbi (*)
2011-06-07 Includes\Tracks.sbi (*)
2012-11-19 Includes\Tracks.uti (*)
2014-01-15 Includes\Trojans-000.sbi (*)
2014-01-15 Includes\Trojans-001.sbi (*)
2014-11-14 Includes\Trojans-002.sbi (*)
2014-01-15 Includes\Trojans-003.sbi (*)
2014-01-15 Includes\Trojans-004.sbi (*)
2014-03-19 Includes\Trojans-005.sbi (*)
2014-07-09 Includes\Trojans-006.sbi (*)
2014-01-15 Includes\Trojans-007.sbi (*)
2014-07-09 Includes\Trojans-008.sbi (*)
2014-07-09 Includes\Trojans-009.sbi (*)
2015-02-17 Includes\Trojans-C.sbi (*)
2014-01-15 Includes\Trojans-OG-000.sbi (*)
2014-01-15 Includes\Trojans-TD-000.sbi (*)
2014-01-15 Includes\Trojans-VM-000.sbi (*)
2014-01-15 Includes\Trojans-VM-001.sbi (*)
2014-01-15 Includes\Trojans-VM-002.sbi (*)
2014-01-15 Includes\Trojans-VM-003.sbi (*)
2014-01-15 Includes\Trojans-VM-004.sbi (*)
2014-01-15 Includes\Trojans-VM-005.sbi (*)
2014-01-15 Includes\Trojans-VM-006.sbi (*)
2014-01-15 Includes\Trojans-VM-007.sbi (*)
2014-01-15 Includes\Trojans-VM-008.sbi (*)
2014-01-15 Includes\Trojans-VM-009.sbi (*)
2014-01-15 Includes\Trojans-VM-010.sbi (*)
2014-01-15 Includes\Trojans-VM-011.sbi (*)
2014-01-15 Includes\Trojans-VM-012.sbi (*)
2014-01-15 Includes\Trojans-VM-013.sbi (*)
2014-01-15 Includes\Trojans-VM-014.sbi (*)
2014-01-15 Includes\Trojans-VM-015.sbi (*)
2014-01-15 Includes\Trojans-VM-016.sbi (*)
2014-01-15 Includes\Trojans-VM-017.sbi (*)
2014-01-15 Includes\Trojans-VM-018.sbi (*)
2014-01-15 Includes\Trojans-VM-019.sbi (*)
2014-01-15 Includes\Trojans-VM-020.sbi (*)
2014-01-15 Includes\Trojans-VM-021.sbi (*)
2014-01-15 Includes\Trojans-VM-022.sbi (*)
2014-01-15 Includes\Trojans-VM-023.sbi (*)
2014-01-15 Includes\Trojans-VM-024.sbi (*)
2014-01-15 Includes\Trojans-ZB-000.sbi (*)
2014-01-15 Includes\Trojans-ZL-000.sbi (*)
2014-01-09 Includes\Trojans.sbi (*)
2014-01-16 Includes\TrojansC-01.sbi (*)
2014-01-16 Includes\TrojansC-02.sbi (*)
2014-01-16 Includes\TrojansC-03.sbi (*)
2014-01-16 Includes\TrojansC-04.sbi (*)
2014-01-16 Includes\TrojansC-05.sbi (*)
2014-01-09 Includes\TrojansC.sbi (*)
Hope you can tell me what is happening?!
Thanks.
Hello. :)
Try a Spybot scan while you are in safe mode.There are instructions for rebooting into safe mode in this post:
http://forums.spybot.info/showthread.php?3922-Spybot-Search-amp-Destroy-FAQs-and-Information&p=23629&viewfull=1#post23629
Once the scan is complete,try fixing everything found.Post back and let me know if Spybot still freezes when fixing problems.
Thanks for your reply.
I've been off line while moving house and have just done my first Spybot check since that last one I posted, and still the same problem.
Just logged in here to find if there was a reply so I'll try your suggestion this week and see what happens then let you know.
Im having the same issue, the "not responding" crash even when i scan one file and find a malware as son as i click fix the spybot freezes :(
Im having the same issue, the "not responding" crash even when i scan one file and find a malware as son as i click fix the spybot freezes :(
You could contact support,and see what they say. :)
http://www.safer-networking.org/support/
Thanks for your reply.
I've been off line while moving house and have just done my first Spybot check since that last one I posted, and still the same problem.
Just logged in here to find if there was a reply so I'll try your suggestion this week and see what happens then let you know.
Just to let you know this has made no difference and Spybot still won't 'fix selected' without freezing.
I'm going to uninstall Spybot now and will live without it.
Okay.
Or you could also contact support,they might be able to help you with something I'm not able to,if it's something happening within the progam. :)
http://www.safer-networking.org/support/
Prescotian
2015-04-01, 20:14
Just wanted to register that I have been having the same problem as described by others - trying to follow the posts searching for simple answer.
Are you getting a "Not responding" window that says "Spybot is not responding.Windows can check online for a solution...."etc when the program crashes?
hookahbookah
2015-05-29, 14:14
I have found a solution, insofar as my situation, regarding this issue.
The problem appears to be google chrome:
If you use google chrome as your browser, and the scan detects some problematic files associated with chrome, you must do the following to prevent spybot from locking up during an attempted fix -
Either:
A. After the scan is completed, DE-select any files associated directly with google chrome (refer to the problem files list that is created after the scan), THEN you should be able to fix the remaining files, if any, without spybot locking up.
OR
B. After the scan is completed, but before you attempt to fix any selected files, google chrome must be closed COMPLETELY. Therefore, any windows of google chrome must be X'd out and closed, then go to the task manager (In Windows, press 'Ctrl+Alt+Del' then select 'Start Task Manager), then to the 'Processes' tab. Close ALL instances of 'chrome.exe' or any variant (such as 'chrome.exe*32'). The fastest way to do this is to look for the instance of chrome.exe which is using the largest amount of memory -- closing those instances will usually close the rest as well. Otherwise you will simply be closing individual chrome extensions. Once you have close all instances of chrome, then run the 'Fix selected issues' in spybot.
More than likely, a chrome extension is hanging spybot. I have not taken the time to try to figure out which instance of chrome.exe is the problem, but needless to say, this does work reliably for me, on 2 separate machines that had the same problem.
Good luck.
twofeathers
2015-06-15, 05:22
Sorry,I meant to say "see if the fixing would complete",not the scan. :)
Selecting "Spyware Scan Only" will let Spybot continue to search for malware.
Taking tracks off for the time being will cut down on the number of items being found after a scan,which will cut down on the number of items being fixed,which might allow the fixing to complete,since the "Not Responding" message might be happening if there is a lot of things to fix.Tracks aren't malware,so it's ok to not scan for them during one scan to see if it will complete,it will do no harm,and I can help you set Spybot to look for them again afterwards.This one scan is just a test,to kind of try to see what might be happening,as it were.
i tried that myself and even over night would not delete just 5 things found. this only started when i updated to 2.4 on windows 8.1. left it on all night to see if time would help, no joy. looked at task manage and spybot was sitting idle.
I've reviewed the full thread on this problem and tried the recommended solutions, including deselecting problems associated with Chrome. I crash every time I try to Fix Selected Problems. I'm using Spybot + Antivirus, Home edition, v2.4, and Google Chrome. I clean up the temp files prior to running Scan, and have tried running it with nothing else open as well as with Chrome, Gmail, Calendar, etc. open. It hangs up regardless. This has been going on for many months and at this point, rather than continue using Spybot and expecting a different outcome (definition of insanity!), I plan to find another software that works. It's a shame... I used to be a huge Spybot fan and recommended it to many others over the years.