What do your SB' files show?
- Thread starter urrguru
- Start date
That seems to be a problem. Did you install Spybot 1.5 over the previous version?
Or B: Did you see an update for v.1.5 in Spybot's integrated default updater?
My best suggestion is to uninstall both entries and then install a fresh copy:
md spybot usa fan's post should clear your doubts about uninstalling:
http://forums.spybot.info/showpost.php?p=199444&postcount=5
Remember to disable SDHelper and TeaTimer. Undo the immunization.
Download a fresh copy of Spybot 1.5.2.20 at:
http://www.safer-networking.org/en/mirrors/index.html
During the installation wizard, do NOT install updates immediately. After the setup you should download the latest updates. This includes the F/P fixes.
Or B: Did you see an update for v.1.5 in Spybot's integrated default updater?
My best suggestion is to uninstall both entries and then install a fresh copy:
md spybot usa fan's post should clear your doubts about uninstalling:
http://forums.spybot.info/showpost.php?p=199444&postcount=5
Remember to disable SDHelper and TeaTimer. Undo the immunization.
Download a fresh copy of Spybot 1.5.2.20 at:
http://www.safer-networking.org/en/mirrors/index.html
During the installation wizard, do NOT install updates immediately. After the setup you should download the latest updates. This includes the F/P fixes.
T-h-a-n-k y-o-u
I can't answer those questions as unlike my usual routine of noting everything about install and upgrades, I had been lax when it came to trusted progs. Now I've come to realize that few app's are designed so user friendly to prevent improper installs.
As for what to do, while your kind reply leads me to article(s), none of them seem to address my situation (two SB's).
Could you re-iterate just a bit so what I end up doing actually helps things (more than just getting one SB to appear, ie; assuredly un-does the duplicate reg entries as well)?
I can't answer those questions as unlike my usual routine of noting everything about install and upgrades, I had been lax when it came to trusted progs. Now I've come to realize that few app's are designed so user friendly to prevent improper installs.
As for what to do, while your kind reply leads me to article(s), none of them seem to address my situation (two SB's).
Could you re-iterate just a bit so what I end up doing actually helps things (more than just getting one SB to appear, ie; assuredly un-does the duplicate reg entries as well)?
Last edited:
Basically you want me to make it sound simpler? :cowboy:
You have two Spybot entries in your Add/Remove Programs window. This is not normal. So, I'm suggesting you uninstall both entries and then reinstall a fresh copy in the link I provided above.
You have two Spybot entries in your Add/Remove Programs window. This is not normal. So, I'm suggesting you uninstall both entries and then reinstall a fresh copy in the link I provided above.
As for simply how best to "uninstall" in my circumstances, have I read and correctly summerized as follows:
Open SB, where/if enabled, disable TeaTimer and SDHelper (not necessarily in that order, any order wll do), un-do immunization (assumedly one 'un-do' is good for all immunizations users have previously applied), run the SB uninstaller, close things, re-boot, check to assure add-remove lists no SB's, run ccleaner or other trusted registry cleaner, re-boot and then proceed with re-installing SB?
Open SB, where/if enabled, disable TeaTimer and SDHelper (not necessarily in that order, any order wll do), un-do immunization (assumedly one 'un-do' is good for all immunizations users have previously applied), run the SB uninstaller, close things, re-boot, check to assure add-remove lists no SB's, run ccleaner or other trusted registry cleaner, re-boot and then proceed with re-installing SB?
Last edited:
The registry cleaner I would hold off for now. Your summurization is fine. Disable Spybot's real-time protection, which is SDHELPER and TEATIMER. It is not necessary to reboot. Undo the IMMUNIZATION. Uninstall both Spybot entries in the ADD/REMOVE PROGRAMS window.
Run the registry fix. Download it directly to the desktop and run it. Reboot if necessary and install a fresh copy at:
http://www.safer-networking.org/en/mirrors/index.html
That is "simplest" way to uninstall it. It couldn't get any simpler :laugh:.
Run the registry fix. Download it directly to the desktop and run it. Reboot if necessary and install a fresh copy at:
http://www.safer-networking.org/en/mirrors/index.html
That is "simplest" way to uninstall it. It couldn't get any simpler :laugh:.
Seems all BUT resolved?
Your title said it's not resolved yet. Do you plan to uninstall it :cowboy:?
As for the sticky, contact one of the moderators if you wish.
Your title said it's not resolved yet. Do you plan to uninstall it :cowboy:?
As for the sticky, contact one of the moderators if you wish.
md usa spybot fan
Spybot Advisor Team [Retired]
urrguru:
I tried answering the same question that with post #2 in this thread:
I do not believe that the advice given about uninstalling both versions you see in Add/Remove programs is advisable.
See if can accept this explanation:
There most likely are not two versions of Spybot installed. More that likely it is just a case were there are two uninstall entries. If you uninstall either via add and remove programs you will more than likely uninstall Spybot.
Go into Spybot > Mode > Advanced mode > Tools > Uninstall Info. Select the two entries one at a time. The new entry contains a GLID "({B4092C6D-E886-4CB2-BA68-FE5A88D31DE6}_is1)" and the "uninstall cmd" should point to the unins000.exe were you installed the software.
Mine looks like this:
If one of the entries does not have the GLID or the "uninstall cmd" does not point to the right place, just delete it.
If you are not sure which entry to delete, right click on the listing and "Copy to clipboard". Then paste (Ctrl+V) those results to a new post in this thread editing out all entries except the two Spybot entries.
_______________
See:
I tried answering the same question that with post #2 in this thread:
- Updated and find two S&D's in Add-Remove
http://forums.spybot.info/showthread.php?t=24064
I do not believe that the advice given about uninstalling both versions you see in Add/Remove programs is advisable.
See if can accept this explanation:
There most likely are not two versions of Spybot installed. More that likely it is just a case were there are two uninstall entries. If you uninstall either via add and remove programs you will more than likely uninstall Spybot.
Go into Spybot > Mode > Advanced mode > Tools > Uninstall Info. Select the two entries one at a time. The new entry contains a GLID "({B4092C6D-E886-4CB2-BA68-FE5A88D31DE6}_is1)" and the "uninstall cmd" should point to the unins000.exe were you installed the software.
Mine looks like this:
Code:
Spybot - Search & Destroy 1.5.2 ({B4092C6D-E886-4CB2-BA68-FE5A88D31DE6}_is1)
install date: 20080131
install location: C:\Program Files\Spybot - Search & Destroy\
uninstall cmd: "C:\Program Files\Spybot - Search & Destroy\unins000.exe"
publisher: Safer Networking Limited
help link: http://www.safer-networking.org/index.php?page=supportIf you are not sure which entry to delete, right click on the listing and "Copy to clipboard". Then paste (Ctrl+V) those results to a new post in this thread editing out all entries except the two Spybot entries.
_______________
See:
- S&D 1.5.2 to 1.5.2.20
http://forums.spybot.info/showthread.php?t=24579 - Spybot 1.52 install over version 1.4??
http://forums.spybot.info/showthread.php?t=24696
Almost home.
Thank you for replying.
May I say that all replies are appreciated and in every instance I always off er thanks.
Also, I respect everyone's contributions on a forum, and until personality needs to enter into issues, unless entertaining, otherwise I expect we all appreciate it when it doesn't.
While I do understand those tasked and/or choosing to deal with people, sometimes involves difficulty, but surely those having the best luck at helping others, keep in mind that people are more easily dealt with when they're made to feel that communication is more than a one way affair (hense either answering a question or if impossible, then only ask questions).
As such, when people make known what it is they don't know, generally it's customary to respond with if not at least a rudementary answer, then courtesy might well deserve an explanation as to why the question isn't being answered.
If not, that could be seen as a lack of attentitiveness or something worse with respect to the relationship.
That's what people feel when a question's answer seems as if it's unecessarily being skirted.
So please forgive me if somehow inflected anything negative. I simply find tunnel vision works best in many environments. No disrect intended.
As for what should be already posted in a prominently titled and posted stickey, is this:
Uninstall before installing tips -
Note that 'upgrading' can well be a misleading term as it's commonly misused by software hawkers and users alike.
Since upgrading and reinstalling aren't always made clear, software designers who properly finish their products always provide the software with a last second opt out at the installation step, that by providing either a precautionary or prohibitive prompt where users attempt to improperly install over-the-top.
In doubly installing software, especially such that can be so potentially irreversibly damaging to a computer's registry, I find it a bit reprehensible that not only SB-S&D's designers have failed, but also the forum moderators might accept some responsibility for not yet having taken the initiative to have posted a clearly titled forum sticky and to have provided it the importance it desrves by placing it first in the list stickeys).
But here's what I did to, as best as I could, determine was most prudent to do. All I can say is that it worked for me and if others also do what I did, I don't guaranty it work out for too, but it did for me.
My paragraphs (below) are simplifying what I did as much as possible, but may not chronologically include the precautions I took before and while performing those 'simple' things.
So I suggest before 'doing the deed', first read. Also I recommend doing your own double-checking in case things have changed with SB-S&D or I've maybe overlooked any mistake(s).
Consider whether or not you run EHD's as program slaves (programs installed and run on/off EHD's and wheteher or not you include SB-S&D scans for any EHD, as if SB-S&D changed things on them, only things needing connected to the computer during these steps, needs connected.
If you use it, set a system restore point for all drives you're going to be using.
Also make a complete registry backup and do not store your reg' backups in a SpyBot folders, even though they 'may not' be deleted or overwritten during
uninstalls/reinstalls.
Open SB, where/if enabled, disable TeaTimer and SDHelper (any disable order will do), un-do immunization. Assumedly only one 'un-do' is good for all immunizations previously applied. I used the 'check again' and I 'un-did' again anyway.
Run another reg backup.
Backup all SB-S&D program files, look for them everywhere, hidden and protected folders too. That's painstaking and likely not needed, but be safe and give yourself the best chances of getting the uninstalled version back as close as possible as like it was before the uninstall if you find issues with the uninstall.
Run you most current version's uninstaller, re-boot (twice each time checking your system), go to add-remove programs list and then click that versions 'remove', it'll prompt it could't do that, but it then still removes the version's entry from the A-R list.
At your option, run ccleaner and/or another trusted registry cleaner, re-boot and then proceed with use of the next most current SB-S&D version's uninstaller.
Note that after uninstalling each most current SB-S&D, follow the same regiment of uninstall steps, including a complete registry backup before proceeding with the next most current SB-S&D uninstall.
Again after each version's uninstall and repeated re-booting and system checks, once again run a complete reg' backup, then I ran RegistryBooster before uninstalling the next most current SB-S&D.
After all SB-S&D's are uninstalled, their entries are removed from Add- Remove Prgos list, and you delete all other instances of SB-S&D folders, run a final reg' backup, set of re-boots and systems checks, tun a registry fixer if you choose, only then download a fresh SB-S&D executable.
Now that the system had it's pant's down and was verified as running properly, while I still am saving all backups (until I get SB-S&D reinstalled and things running right).
I chose to clear the browser cache, temp files, run disk cleanup, and then I unticked my system restore and cleared it too of any possible malware.
I recommed you somehow determine that download's integrity in as much as the download sites aren't disclosing any means of verifying the executable (ie; file size, creation/modified dates, MD5 hash, nothing), so be aware that installing a malformed SB-S&D could cause a lot of your work to be repeated.
Some not readily disclosed, how to do those things -
Disabling TeaTimer and/or SDHelper:
Expand SB's Tools, click Resident and untick where necessary.
Un-doing Immunizations:
In the "SpyBot S&D" column, click "Immunize" (do not click then one that has the green 'plus' icon) and then click the "Undo" (just left of the "Help" option).
Added notes -
Copying and saving any existing SB Backups and Log folders, ie; reg backups (add a text doc to the backup folder to identify nature of each backup file's *.reg files, ref. the info/dates listed in SB's "Recovery" window). Also copy-save useage history for added info.
After creating your system restore point, as a precaution, check and confirm your RP actually listed in system restore.
Where to's:
Default SB' logs are at...
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Backups <*.reg files to restore registry, these might be the undo immunization .reg files>
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Recovery <*.zip files to restore registry, these may be the malware and other 'fixes' run>
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Logs <assorted *.txt docs of scan reports, etc.>
Of interest, the following leftover/uncleaned up SB-S&D files were (on my system) default located as follows:
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Recovery
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Logsand Settings\All Users\Application
Data\Spybot - Search & Destroy\Logs
Best of luck, and hopefully hap-e-trails,
urrguru
Thank you for replying.
May I say that all replies are appreciated and in every instance I always off er thanks.
Also, I respect everyone's contributions on a forum, and until personality needs to enter into issues, unless entertaining, otherwise I expect we all appreciate it when it doesn't.
While I do understand those tasked and/or choosing to deal with people, sometimes involves difficulty, but surely those having the best luck at helping others, keep in mind that people are more easily dealt with when they're made to feel that communication is more than a one way affair (hense either answering a question or if impossible, then only ask questions).
As such, when people make known what it is they don't know, generally it's customary to respond with if not at least a rudementary answer, then courtesy might well deserve an explanation as to why the question isn't being answered.
If not, that could be seen as a lack of attentitiveness or something worse with respect to the relationship.
That's what people feel when a question's answer seems as if it's unecessarily being skirted.
So please forgive me if somehow inflected anything negative. I simply find tunnel vision works best in many environments. No disrect intended.
As for what should be already posted in a prominently titled and posted stickey, is this:
Uninstall before installing tips -
Note that 'upgrading' can well be a misleading term as it's commonly misused by software hawkers and users alike.
Since upgrading and reinstalling aren't always made clear, software designers who properly finish their products always provide the software with a last second opt out at the installation step, that by providing either a precautionary or prohibitive prompt where users attempt to improperly install over-the-top.
In doubly installing software, especially such that can be so potentially irreversibly damaging to a computer's registry, I find it a bit reprehensible that not only SB-S&D's designers have failed, but also the forum moderators might accept some responsibility for not yet having taken the initiative to have posted a clearly titled forum sticky and to have provided it the importance it desrves by placing it first in the list stickeys).
But here's what I did to, as best as I could, determine was most prudent to do. All I can say is that it worked for me and if others also do what I did, I don't guaranty it work out for too, but it did for me.
My paragraphs (below) are simplifying what I did as much as possible, but may not chronologically include the precautions I took before and while performing those 'simple' things.
So I suggest before 'doing the deed', first read. Also I recommend doing your own double-checking in case things have changed with SB-S&D or I've maybe overlooked any mistake(s).
Consider whether or not you run EHD's as program slaves (programs installed and run on/off EHD's and wheteher or not you include SB-S&D scans for any EHD, as if SB-S&D changed things on them, only things needing connected to the computer during these steps, needs connected.
If you use it, set a system restore point for all drives you're going to be using.
Also make a complete registry backup and do not store your reg' backups in a SpyBot folders, even though they 'may not' be deleted or overwritten during
uninstalls/reinstalls.
Open SB, where/if enabled, disable TeaTimer and SDHelper (any disable order will do), un-do immunization. Assumedly only one 'un-do' is good for all immunizations previously applied. I used the 'check again' and I 'un-did' again anyway.
Run another reg backup.
Backup all SB-S&D program files, look for them everywhere, hidden and protected folders too. That's painstaking and likely not needed, but be safe and give yourself the best chances of getting the uninstalled version back as close as possible as like it was before the uninstall if you find issues with the uninstall.
Run you most current version's uninstaller, re-boot (twice each time checking your system), go to add-remove programs list and then click that versions 'remove', it'll prompt it could't do that, but it then still removes the version's entry from the A-R list.
At your option, run ccleaner and/or another trusted registry cleaner, re-boot and then proceed with use of the next most current SB-S&D version's uninstaller.
Note that after uninstalling each most current SB-S&D, follow the same regiment of uninstall steps, including a complete registry backup before proceeding with the next most current SB-S&D uninstall.
Again after each version's uninstall and repeated re-booting and system checks, once again run a complete reg' backup, then I ran RegistryBooster before uninstalling the next most current SB-S&D.
After all SB-S&D's are uninstalled, their entries are removed from Add- Remove Prgos list, and you delete all other instances of SB-S&D folders, run a final reg' backup, set of re-boots and systems checks, tun a registry fixer if you choose, only then download a fresh SB-S&D executable.
Now that the system had it's pant's down and was verified as running properly, while I still am saving all backups (until I get SB-S&D reinstalled and things running right).
I chose to clear the browser cache, temp files, run disk cleanup, and then I unticked my system restore and cleared it too of any possible malware.
I recommed you somehow determine that download's integrity in as much as the download sites aren't disclosing any means of verifying the executable (ie; file size, creation/modified dates, MD5 hash, nothing), so be aware that installing a malformed SB-S&D could cause a lot of your work to be repeated.
Some not readily disclosed, how to do those things -
Disabling TeaTimer and/or SDHelper:
Expand SB's Tools, click Resident and untick where necessary.
Un-doing Immunizations:
In the "SpyBot S&D" column, click "Immunize" (do not click then one that has the green 'plus' icon) and then click the "Undo" (just left of the "Help" option).
Added notes -
Copying and saving any existing SB Backups and Log folders, ie; reg backups (add a text doc to the backup folder to identify nature of each backup file's *.reg files, ref. the info/dates listed in SB's "Recovery" window). Also copy-save useage history for added info.
After creating your system restore point, as a precaution, check and confirm your RP actually listed in system restore.
Where to's:
Default SB' logs are at...
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Backups <*.reg files to restore registry, these might be the undo immunization .reg files>
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Recovery <*.zip files to restore registry, these may be the malware and other 'fixes' run>
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Logs <assorted *.txt docs of scan reports, etc.>
Of interest, the following leftover/uncleaned up SB-S&D files were (on my system) default located as follows:
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Recovery
C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Logsand Settings\All Users\Application
Data\Spybot - Search & Destroy\Logs
Best of luck, and hopefully hap-e-trails,
urrguru
Somewhat a long explaination...
I just find your meticulous "task" tedious. As for trusted registry cleaners I would certainly not recommend Uniblue products. As the product pressures users to purchase the product before removing.
And I would certainly not recommend erasing "good" known Restore Points. If you know what you were doing, there wouldn't be malware on your computer.
I just find your meticulous "task" tedious. As for trusted registry cleaners I would certainly not recommend Uniblue products. As the product pressures users to purchase the product before removing.
And I would certainly not recommend erasing "good" known Restore Points. If you know what you were doing, there wouldn't be malware on your computer.
md usa spybot fan
Spybot Advisor Team [Retired]
urrguru:
Please note: It is not necessary to backup the information (log, excludes, recovery, snapshots, etc.) in the following directory and sub-directories because the information is not deleted during an uninstall:
Please note: It is not necessary to backup the information (log, excludes, recovery, snapshots, etc.) in the following directory and sub-directories because the information is not deleted during an uninstall:
- 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 - Windows Vista:
C:\ProgramData\Spybot - Search & Destroy
- How to uninstall
http://www.safer-networking.org/en/howto/uninstall.html
Resolving uninstall & re-install issues
After nearly a week of waiting and several e-mails with respect to my questioning SB-S&D's laxness in recognizing security by offering SB-S&D products (w/o disclosing file validity and/or integrity details), I just received a SB-S&D e-mail back (disclosing the security details as follows).
I also see now their website at least lists an md5 for all their products, tools and updates. Maybe they're going to also begin disclosing file sizes so users also know the files are being completely downloaded and are not otherwise indicated as corrupted.
"spybotsd152.exe, md5: CC91B89CE4EBA400BAED4F626487D579, file size is 9,3 MB (9722720 Bytes)"
My display details for the 'exe is...
file size is as 9.27 MB (9722720 Bytes)
file version 1.5.2.0, yet the properties
'other version info' lists it as 1.5.2
Best regards and hep-e-trails to all,
urrguru
After nearly a week of waiting and several e-mails with respect to my questioning SB-S&D's laxness in recognizing security by offering SB-S&D products (w/o disclosing file validity and/or integrity details), I just received a SB-S&D e-mail back (disclosing the security details as follows).
I also see now their website at least lists an md5 for all their products, tools and updates. Maybe they're going to also begin disclosing file sizes so users also know the files are being completely downloaded and are not otherwise indicated as corrupted.
"spybotsd152.exe, md5: CC91B89CE4EBA400BAED4F626487D579, file size is 9,3 MB (9722720 Bytes)"
My display details for the 'exe is...
file size is as 9.27 MB (9722720 Bytes)
file version 1.5.2.0, yet the properties
'other version info' lists it as 1.5.2
Best regards and hep-e-trails to all,
urrguru
Last edited: