Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Spybot 2 update issue

  1. #11
    Senior Member
    Join Date
    Oct 2005
    Location
    Germany
    Posts
    5,263

    Default

    Hello,

    "Check status" is working, but mostly misunderstood.
    See my post above.
    The "Update" is working either, but does not give a notification yet when the files have been updated.
    We are aware of this issue and will improve it.
    To see if the updates did take place please also check your update log.
    It should be stored here:
    C:\Users\All Users\Spybot - Search & Destroy\Logs\Updates

    Best regards
    Sandra
    Team Spybot

  2. #12
    Junior Member
    Join Date
    Nov 2012
    Posts
    7

    Default

    Or just click "show update log" button in the update window.

    @spybotsandra What should the check status button do then? In my understanding, it should check and show if some files need updating or if all files are up to date. At the moment it does nothing, except if the "updates.uid" file is erased.

  3. #13
    Senior Member
    Join Date
    Oct 2005
    Location
    Germany
    Posts
    5,263

    Default

    Hello,

    Quote Originally Posted by spybotsandra View Post
    Hello,

    "Check status" only tells you which files are up to date and if they have been downloaded correctly.
    Best regards
    Sandra
    Team Spybot

  4. #14
    Junior Member
    Join Date
    Nov 2012
    Posts
    7

    Default

    Quote Originally Posted by spybotsandra
    Hello,

    "Check status" only tells you which files are up to date and if they have been downloaded correctly.
    Yes but the problem is, that it doesn't do it. It always reports that all the files are up to date (even when they are not), unless I delete the "updates.uid" file.

  5. #15
    Junior Member
    Join Date
    Dec 2012
    Posts
    1

    Exclamation really annoying

    i have same issues :( ,,, no updates unless i delete "updates.uid"

    when does get this fixed? long time it takes ... and yes i m a donater!

  6. #16
    Senior Member
    Join Date
    Oct 2005
    Location
    Germany
    Posts
    5,263

    Default

    Hello,

    We are sorry for the inconvenience. This item has been reported to our development team. A fix will not be available in an update but in a next version upgrade. There is no release date yet, as we are still working on it.

    Best regards
    Sandra
    Team Spybot

  7. #17
    Junior Member
    Join Date
    Mar 2013
    Posts
    1

    Default update

    where is this update.uid located

  8. #18
    Senior Member
    Join Date
    Oct 2005
    Location
    Germany
    Posts
    5,263

    Default

    Hello,

    That would be:

    Windows XP: C:\Program Files\Spybot - Search & Destroy 2\Updates\Downloads
    Windows Vista or Windows 7 or Windows 8: C:\Programs (x86)\Spybot - Search & Destroy 2\Updates\Downloads

    Best regards
    Sandra
    Team Spybot

  9. #19
    Junior Member
    Join Date
    Feb 2010
    Posts
    4

    Exclamation concerned!

    I found this thread while trying to find an answer to why for the past few weeks Spybot keeps saying that it has been more than 8 days since last update, even though I check for updates - and believed they had been completed - every week, as well as run a complete system scan.

    I click the "Update" button, see a pop-up which SAYS that it is checking for updates, and it gives every impression that any available updates are then performed. When I click "Check Status", it informs me that files are up to date. Because I have been annoyed by the message still claiming that it had been more than 8 days since I updated, I would repeat the update multiple times through the various methods available (run as administrator from the Start Center, click the Update button from the update screen, and even right click the icon in the taskbar), but that message would not go away.

    I had no reason to check the Update Log as every single method clearly indicated that updates had been done.

    Now, thanks to this thread, I see my log shows this for the past three weeks, apparently the last update was done on May 1!:

    SDUpdSvc.exe [2013-05-01 12:01:36] [+] All files have been processed.
    SDUpdSvc.exe [2013-05-01 12:01:36] +++
    SDUpdSvc.exe [2013-05-01 12:01:36] Processed 9 updates
    SDUpdSvc.exe [2013-05-02 13:42:11] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-02 13:42:11] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-03 12:01:45] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-03 12:01:45] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-04 12:23:04] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-04 12:23:04] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-05 11:11:58] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-05 11:11:58] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-06 13:39:42] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-06 13:39:43] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-07 11:27:18] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-07 11:27:18] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-08 12:46:43] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-08 12:46:43] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-09 12:36:51] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-09 12:36:51] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-10 12:28:44] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-10 12:28:44] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-11 12:48:02] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-11 12:48:02] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-12 13:47:37] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-12 13:47:37] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-13 11:28:09] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-13 11:28:10] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-14 13:34:39] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-14 13:34:39] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-15 12:50:44] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-15 12:50:44] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-15 13:34:36] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-15 13:34:36] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-16 09:39:14] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-16 09:39:14] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-17 12:10:51] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-17 12:10:53] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-18 12:47:45] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-18 12:47:45] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-19 13:46:20] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-19 13:46:20] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-19 14:00:18] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-19 14:00:18] 0.0.0.0 Successfully started listening on port 21321.
    SDUpdSvc.exe [2013-05-20 13:11:54] [+] Background Updating Service got started...
    SDUpdSvc.exe [2013-05-20 13:11:54] 0.0.0.0 Successfully started listening on port 21321.

    I did not do ANYTHING different, yet after reading this thread, and viewing the log, I try to update one more time before posting here, and suddenly my log now shows:

    SDUpdSvc.exe [2013-05-20 16:08:31] Trying to retrieving news...
    SDUpdSvc.exe [2013-05-20 16:08:33] 10 news articles found.
    SDUpdSvc.exe [2013-05-20 16:08:33] Started looking for updates...
    SDUpdSvc.exe [2013-05-20 16:08:33] [+] Updating Service is active.
    SDUpdSvc.exe [2013-05-20 16:08:33] [.] Trying to retrieve update info file from http://updates2.safer-networking.org/spybotsd2.uid...
    SDUpdSvc.exe [2013-05-20 16:08:34] [+] Retrieved update info file.
    SDUpdSvc.exe [2013-05-20 16:08:34] [.] Info file part done.
    SDUpdSvc.exe [2013-05-20 16:08:34] [.] Testing which updates apply to this version...

    ....and then proceeds to show updates which are needed and now have been downloaded



    How is it possible that spybot could clearly be informing me that it is checking for updates, applying them, and that files are up to date, when they weren't? Should I really have to check the log every week in order for the updates to actually be done?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •