Failed to update?

[bladerunner52]

This might be it:

Huh!That's the first time I've seen anything like 'Unable to store downloaded update information',to be honest.

I removed my own updates.uid and it was just replaced with a new one when I updated.
Follow this path,and see if yours is in the same location:C:\Program Files (x86)\Spybot - Search & Destroy 2\Updates\Downloads
If your path to the Downloads folder is different,please post it.
The updates.uid file should be in your Downloads folder.If it is there,rightclick it,select Cut,paste it on your Desktop.You'll get a prompt that you need to give Administrator Permission first,say yes.Leave it on the desktop,don't throw it out.
Then try checking for updates again,and see what happens.

Do you have any programs on your desktop computer that encrypts the files on your computer or anything like that?

I'm afraid I'm having the same issues, and no I'm not running any programs like that. The only things I have running are Symantec Endpoint Protection(which is also running on my laptop), my printer event manager, activclient agent and google chrome.

I do appreciate the help though!

[Zenobia]

Thanks for letting me know.Now could you let me know how the rest of what I posted went?

Follow this path,and see if yours is in the same location:C:\Program Files (x86)\Spybot - Search & Destroy 2\Updates\Downloads
If your path to the Downloads folder is different,please post it.
The updates.uid file should be in your Downloads folder.If it is there,rightclick it,select Cut,paste it on your Desktop.You'll get a prompt that you need to give Administrator Permission first,say yes.Leave it on the desktop,don't throw it out.
Then try checking for updates again,and see what happens.

[Hooter]

Excuse me for jumping into this thread, but I have the same problem in Spybot 2.4 that BladeRunner52 has - the updated files are stored in the update log, but go nowhere after that. Update hums along literally for hours, after you close Update and go to the download file (C:\Program Files (x86)\Spybot - Search & Destroy 2\Updates\Downloads) it's empty..... No updates.uid file.... Where is it going? Extracts folder is also empty.

Never had any updating problems with previous versions of Spybot. My desktop is essentially unchanged except I added TinyWall to the Windows Firewall but Spybot is whitelisted in TinyWall and WFW. I also uninstalled Skype shortly after I installed Spybot 2.4, but I can't see how that would mess up Spybot as I've uninstalled Spybot and reinstalled it shortly after experiencing the Spybot update problem thinking I might have had a bad download. Going to re-install Skype then run update to eliminate any conflict that the Skype dump may have created(?). Right now I'm stumped.

[Zenobia]

Let's see if you're getting the same thing in your logfile.
Open Spybot Start Center,click Advanced User Mode,click Report Creator,then click Show logs on the left,then open Updates.log,click Edit,Select All,then rightclick,select Copy,then Paste it here.

[Hooter]

Let's see if you're getting the same thing in your logfile.
Open Spybot Start Center,click Advanced User Mode,click Report Creator,then click Show logs on the left,then open Updates.log,click Edit,Select All,then rightclick,select Copy,then Paste it here.

Sorry it took me awhile to respond. I've found issues unrelated to Spybot with updates. Update within MSE works but Windows Updates doesn't work(???) - error code 0x8024402c that can't be resolved with the usual Microsoft Fix-it repairs. Microsoft tells me to "check connections to URLs(all Microsoft) used in SDP service". All points to something I did within the Tiny Wall program and NOT the Skype un-install. Perhaps when I get my firewall rules in order all my update programs will work(?). Will let you know once I figure out how to fix connection problems over the internet. The LAN works fine, going to try disabling MSE, clean up my firewall rules and then try all three updates......

BTW, my Spybot updates log goes back to 02-06-2014 and is ten miles long, don't want to bother you with it's length, unless I still have problems w/ updating Spybot after figuring out why my computer is not allowing communication with only certain URLs and the SDP service. Thanks for you time.

[Hooter]

Sorry it took me awhile to respond. I've found issues unrelated to Spybot with updates. Update within MSE works but Windows Updates doesn't work(???) - error code 0x8024402c that can't be resolved with the usual Microsoft Fix-it repairs. Microsoft tells me to "check connections to URLs(all Microsoft) used in SDP service". All points to something I did within the Tiny Wall program and NOT the Skype un-install. Perhaps when I get my firewall rules in order all my update programs will work(?). Will let you know once I figure out how to fix connection problems over the internet. The LAN works fine, going to try disabling MSE, clean up my firewall rules and then try all three updates......

BTW, my Spybot updates log goes back to 02-06-2014 and is ten miles long, don't want to bother you with it's length, unless I still have problems w/ updating Spybot after figuring out why my computer is not allowing communication with only certain URLs and the SDP service. Thanks for you time.

My problems solved - TinyWall was blocking the MS URLs that caused Windows Update not to work properly. Bottom line, I've tried Spybot update, MSE update and Windows update and they are all functional now that I cleaned up my firewall rules.... Lesson learned, don't mess with something new until you understand what it's doing for you. Then and only then should attempt to "tweak it" or fine tune it.

Sorry to have bothered you with problems I created here locally and thanks again for your offer to help with my Spybot update logs.

[Zenobia]

No bother at all.Glad you got it fixed.

[Beadbud5000]

I am having the exact same problem.
Thanks Bud[/QUOTE]

[Zenobia]

I need an updates logfile to look at.Instructions posted above.

[Beadbud5000]

My Report
[i] 14-09-02 10:29:57 THttpUpdateDaemon Successfully started listening on port 21321.
SDUpdSvc.exe [2014-09-02 10:38:41] [+] Updating Service is active.
SDUpdSvc.exe [2014-09-02 10:38:41] [.] Trying to retrieve update info file from http://updates1.safer-networking.org/spybotsd2.uid...
SDUpdSvc.exe [2014-09-02 10:38:42] [+] Retrieved update info file.
SDUpdSvc.exe [2014-09-02 10:38:42] [.] Info file part done.
SDUpdSvc.exe [2014-09-02 10:38:42] [.] Testing which updates apply to this version...
SDUpdSvc.exe [2014-09-02 10:38:43] [+] No updates required.
SDUpdSvc.exe [2014-09-02 10:38:43] +++
SDUpdSvc.exe [2014-09-02 10:39:23] [+] Updating Service is active.
SDUpdSvc.exe [2014-09-02 10:39:23] [.] Trying to retrieve update info file from http://updates3.safer-networking.org/spybotsd2.uid...
SDUpdSvc.exe [2014-09-02 10:39:24] [+] Retrieved update info file.
SDUpdSvc.exe [2014-09-02 10:39:24] [.] Info file part done.
SDUpdSvc.exe [2014-09-02 10:39:24] [.] Testing which updates apply to this version...
SDUpdSvc.exe [2014-09-02 10:39:25] [+] No updates required.
SDUpdSvc.exe [2014-09-02 10:39:25] +++
[i] 14-09-02 10:40:49 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-02 10:44:16 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-02 10:44:16 THttpUpdateDaemon Listening on port 21321
[i] 14-09-02 10:44:16 THttpUpdateDaemon Successfully started listening on port 21321.
[+] 14-09-03 06:54:27 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-03 06:54:27 THttpUpdateDaemon Listening on port 21321
[i] 14-09-03 06:54:27 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-03 11:09:25 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-03 12:56:18 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-03 12:56:18 THttpUpdateDaemon Listening on port 21321
[i] 14-09-03 12:56:18 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-03 22:59:28 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-04 07:26:19 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-04 07:26:19 THttpUpdateDaemon Listening on port 21321
[i] 14-09-04 07:26:19 THttpUpdateDaemon Successfully started listening on port 21321.
[+] 14-09-04 07:57:35 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-04 07:57:36 THttpUpdateDaemon Listening on port 21321
[i] 14-09-04 07:57:36 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-05 00:15:08 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-05 06:21:20 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-05 06:21:20 THttpUpdateDaemon Listening on port 21321
[i] 14-09-05 06:21:20 THttpUpdateDaemon Successfully started listening on port 21321.
[+] 14-09-05 10:01:07 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-05 10:01:07 THttpUpdateDaemon Listening on port 21321
[i] 14-09-05 10:01:07 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-05 22:33:00 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-06 07:40:17 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-06 07:40:17 THttpUpdateDaemon Listening on port 21321
[i] 14-09-06 07:40:17 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-06 12:44:34 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-06 14:31:05 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-06 14:31:05 THttpUpdateDaemon Listening on port 21321
[i] 14-09-06 14:31:05 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-06 15:49:50 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-06 15:51:40 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-06 15:51:40 THttpUpdateDaemon Listening on port 21321
[i] 14-09-06 15:51:40 THttpUpdateDaemon Successfully started listening on port 21321.
[+] 14-09-06 17:11:17 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-06 17:11:17 THttpUpdateDaemon Listening on port 21321
[i] 14-09-06 17:11:17 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-07 00:55:47 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-07 07:58:46 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-07 07:58:46 THttpUpdateDaemon Listening on port 21321
[i] 14-09-07 07:58:46 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-07 10:03:47 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-07 11:52:05 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-07 11:52:05 THttpUpdateDaemon Listening on port 21321
[i] 14-09-07 11:52:05 THttpUpdateDaemon Successfully started listening on port 21321.
[+] 14-09-07 13:58:22 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-07 13:58:22 THttpUpdateDaemon Listening on port 21321
[i] 14-09-07 13:58:22 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-07 22:20:07 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-08 07:11:46 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-08 07:11:46 THttpUpdateDaemon Listening on port 21321
[i] 14-09-08 07:11:46 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-08 22:56:28 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-09 06:01:23 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-09 06:01:23 THttpUpdateDaemon Listening on port 21321
[i] 14-09-09 06:01:23 THttpUpdateDaemon Successfully started listening on port 21321.
[i] 14-09-09 06:30:33 THttpUpdateDaemon HTTP daemon on port 21321 closed.
[+] 14-09-09 06:31:59 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-09 06:31:59 THttpUpdateDaemon Listening on port 21321
[i] 14-09-09 06:31:59 THttpUpdateDaemon Successfully started listening on port 21321.
[+] 14-09-09 08:45:29 THttpUpdateDaemon Background Updating Service got started...
[i] 14-09-09 08:45:29 THttpUpdateDaemon Listening on port 21321
[i] 14-09-09 08:45:29 THttpUpdateDaemon Successfully started listening on port 21321.