Hi Gleam;
I really think you need expertise in CounterSpy to resolve this issue,
unfortunatly, I doubt we have it in this forum.
Please go here and read this Sticky note:
http://castlecops.com/f164-CounterSpy.html
Sticky: Necessry to uninstall Microsoft AS Beta?
Register on CastleCops, then post to their forum, CounterSpy is supported here
by Sunbelt Software's philow and Oldfrog.
I think they will be surprised to hear that issues are still around with 1.5.x
--
Regards, Dave
Gleam wrote:
> I have done a repair on Microsoft antispyware - no change.
> I want to be remove Counterspy, so I don' t think installing and removing
> will help. Please advise.
> I had upgraded to version 1.5.
> It has been suggested that I should go through the registry and delete every
> reference to Counterspy - I did this and there were over 400 of them - I got
> quite fast at delete, Enter, F3. This has changed the error message in non
> admin mode to Counterspy Internal Error 2718. MASW now runs - it just stops
> when the error message comes up, and resumes when I click on OK.
> While MASW was running as non-admin I tried a regedit looking for
> "counterspy" and found several which I could not delete. One was underneath
> HKEY_Local_Machine \ Software \ Microsoft \ Windows \ Current Version \
> Installer \ User data \ S-1-5-21- lots of numbers \ Components \ lots more
> numbers. I have tried again when MASW is not running and cannot find any.
>
> Looking in my downloads directory I think the file that I downloaded and
> which is causing all the bother is called cscreg.exe. I cannot see any way of
> removing ot via the control panel / add remove programs.
>
> Thanks
>
>
> "Dave M" wrote:
>
>> The problems that Bill refers to occurred with dual installations of MSAS and
>> Counterspy version 1.0.x, followed by an un-install of either product. Was
>> your version of Counterspy upgraded to version 1.5.x before you un-installed
>> it? That release supposedly would have fixed any conflicts between the two
>> products, because at the earlier level both were essentially the same
>> product. --
>> Regards, Dave
>>
>>
>> Bill Sanderson wrote:
>>> There have been, in the past, some interactions between CounterSpy and
>>> Microsoft Antispyware. Originally, they were very close cousins--both
>>> descended from the same original Giant software product.
>>>
>>> However, your issue sounds to me more like a generic issue with the Windows
>>> Installer which we've seen a number of times in this beta--usually with
>>> entirely unrelated products involved.
>>>
>>> In general, my usual advice is to do a reinstall or repair install of
>>> whatever is giving you this prompt when Microsoft Antispyware starts.
>>>
>>> For Microsoft Antispyware, one path to doing this is start, control panel,
>>> Microsoft Antispyware, change, update.
>>>
>>> If you are pretty sure it was the downloaded piece for Counterspy, you could
>>> try reinstalling that, or you could reinstall Counterspy over itself, or use
>>> whatever repair or reinstallation options it has.
>>>
>>> Whichever actions you try, be certain that you are an administrator on the
>>> machine before doing the reinstalls. This is solvable--but I can't give you
>>> an easy recipe, I'm afraid--you'll need to try out some things and let us
>>> know what doesn't work, I suspect.
>>>
>>>
>>> "Gleam" <(E-Mail Removed)> wrote in message
>>> news:EE6EE47B-8919-420A-8074-(E-Mail Removed)...
>>>> I uninstalled Counterspy and rebooted before installing Microsoft
>>>> AntiSpyware. MS ASW works fine in the Admin account, but as soon as I go
>>>> to
>>>> my non-admin account I keep getting messgaes as Counterspy tries to
>>>> install 3
>>>> times almost every time I start a program.
>>>> If I allow it to install I then get a message "Counterspy. Error 1406.
>>>> Could
>>>> not write value to key
>>>> \SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce."
>>>> If I try to start MS ASW I get a critical error 103.
>>>> I downloaded something from Counterspy which I had hoped would allow me to
>>>> run it from a non-admin account, and I suspect that it is this which is
>>>> lurking somewhere.
>>>> Any help welcome.
Similar Threads
