PDA

View Full Version : Inadvertantly deleted the SUPERAntiSpyware folder ?


EASTER.2010
March 10th, 2007, 11:27 PM
Well in haste i inadvertantly deleted the SAS folder before realizing it needs the uninstall log to remove the program so i'm in a quagmire now. I tried to trace down every file possible including the drivers but now i still can't even install ANY vesion of SAS untill i find the files that have the installer in limbo.

PROBLEM SOLVED!

fcukdat
March 11th, 2007, 09:11 AM
Joe have you tried maunally deleting all files in safe mode then going through your registry with regseeker and delete all *SAS* stuff(search known SAS related values).Finally go looking for *installer/uninstall MSI info and locate the sas only values and delete.

This manual hacking has worked for me in the past when ripping out Beta software or corrupted installs but agread it is a time consuming PITA::)

screamer
March 11th, 2007, 10:20 AM
-{ Quote: "

I am a big proponant on registry cleaning programs and i lay odds one of those in "aggresive mode" likely wiped the uninstall log.

Thanks" }-

EASTER, can you peruse the logs from your registry cleaner? If not, and you are fairly certain when this occurred, would it pay to re-install the cleaned / deleted values. I had a simillar issue w/ MS Outlook while using RegCure. I re-installed the deleted values and Outlook rose from the dead.

I'm sure you've thought of this, but in case you didn't...

...screamer

EASTER.2010
March 11th, 2007, 11:02 AM
-{ Quote: "I'm sure you've thought of this, but in case you didn't..." }-

Thanks, yes i went back over all my reg cleaner backups but since i deleted the folder w/contents i suspect there was something there which is required for a clean uninstall.

I'll try to dig out some old uninstall programs that claim to pull all remnants from any software program and see how that fairs.

I done some blunders before but this one was a good one.

EASTER.2010
March 11th, 2007, 09:18 PM
SOLVED! :thumb:

Everything is restored as before now.

EASTER.2010
March 11th, 2007, 09:35 PM
Previous problem resolved. Thanks for suggestions.

Rilla927
March 12th, 2007, 06:45 AM
-{ Quote: "If i don't get to the bottom of this soon i'll never be able to install SAS again unless i resort to a brand new install :-[

Like i said before and continues to be true, i have more problems with authentic programs than i ever did with malware/rootkits. One misstep or change can make for incredible difficulty and loss of time." }-

This sounds like me to the tee:wacko: I thought I was a lone.

I'm sorry to hear about your dilemma and glad you got it straightend out.

fcukdat
March 12th, 2007, 02:32 PM
-{ Quote: "SOLVED! :thumb:

Everything is restored as before now." }-


:P Heh,happy to assist;D

EliteKiller
March 12th, 2007, 06:56 PM
Is it possible to share the "fix" in case others have a similar problem and use the Search feature?

pugmug
March 12th, 2007, 07:41 PM
You test without full backups?

jim28277
March 12th, 2007, 07:45 PM
Sorry to hear about your bad luck. Have you ever considered an imaging program. Acronis True Image has saved my bacon (and my hard drive) on a number of occasions. Cheers Jim

trjam
March 12th, 2007, 08:05 PM
I did this once and went to the SAS forum and stated my case. Within minutes Nick sent me the fix. I would suggest that approach first instead of trying to do it yourself. SAS has some deep roots and you want to get it right.

Antarctica
March 13th, 2007, 06:05 AM
-{ Quote: "SUPERAntiSpy issue is returned, please see PM, Thanks." }-

Easter.2010, what issue is that?
Thanks:)

EASTER.2010
March 13th, 2007, 07:04 AM
Previous SAS version requires the source
WISCDDCBBF1270346BC938BBCC81A1EEAAA_3_4_0_1000.MSI in order to uninstall and looks like either the reg cleaner or a virus i run (without PowerShadow) (My Bad) removed it right after i just got things sorted out.
I would be eternally grateful if you could forward what i assume would be a newer series of sets so i can finally uninstall the old without receiving the complaint for needing that source.

Usually it's a TypeLib/Enum or other several digit number code that makes it an issue.

Thanks

fcukdat
March 13th, 2007, 02:50 PM
-{ Quote: "Is it possible to share the "fix" in case others have a similar problem and use the Search feature?" }-

Hmm well its a case of manually hacking out the SAS MSI package with that its not something that can be easily explained unless someone has extensive knowledge of the registry and location of MSI installers.So with that i will have to refrain incase someone deletes the wrong key/value and then cries bad advice given:'(

Joe.....D'oh!!!:P

I wanna go bot hunting....PM will be with you shortly:thumb:

Ocky
March 13th, 2007, 03:11 PM
Maybe if you have Windows Support Tools installed, open cmd prompt, and type msicuu.exe. Then provided the SAS entry is still listed, remove it.

EASTER.2010
March 14th, 2007, 01:24 AM
PROBLEM REMOVED!

Spent too much time trying to uninstall so all i did was INSTALL to the alternate drive and transfer it all to the main XP and everything is returned to notmal again. wHEW!!

SUPERAntiSpy
March 14th, 2007, 11:29 AM
-{ Quote: "PROBLEM REMOVED!

Spent too much time trying to uninstall so all i did was INSTALL to the alternate drive and transfer it all to the main XP and everything is returned to notmal again. wHEW!!" }-

Glad to hear the problem was solved - I was going to have you run our diagnostic to see if I could spot the problem for you - in the future let the auto-updater do it's work, or uninstall via the Control Panel Add/Remove so our uninstaller can do it's work :) Glad you are back to running SAS :)

SUPERAntiSpy
March 14th, 2007, 11:30 AM
-{ Quote: "PROBLEM REMOVED!

Spent too much time trying to uninstall so all i did was INSTALL to the alternate drive and transfer it all to the main XP and everything is returned to notmal again. wHEW!!" }-

Are you going to remove the (Defective) from your sig? :)

EASTER.2010
March 15th, 2007, 06:02 AM
Ooops. Done. Yes the alternative method resolved the issue and thats the last time i jump the gun and remove things before giving the uninstall a chance to work first. Sometimes i get way ahead of myself.

Thanks for pointing that out Nick and also the assist.

EASTER.2010
March 15th, 2007, 06:38 AM
For future reference and to make clear what i was able to dig up to finally dismiss 360 from pointing to 340 as still installed. This is the key section i was manually able after deleting to free up the 360 installer finally.

For security purposes actual series lines are deliberately ommitted.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\etc.