reenabling a disabled agent

  • Thread starter Thread starter toddkozi
  • Start date Start date
T

toddkozi

I was lazy so I tried disabling the script blocking while I worked with
some reg files so they would open with the program I wanted rather than
merging directly to registry (something to do with MAS stopping the
action awaiting my approval, then when I OK it, it hands over to the
default action for the reg file- that is a known bug AFAIK, so I tried
disabling the script blocking agent).

When I tried reenabling the script blocking agent, it wouldn't. And I saw
that process execution protection had also been disabled. I don't know if
that was a bug or how it got stopped, too, unless disabling one is
supposed to disable the other.

I'm ready to reinstall, but if there is another workaround for reenabling
a disabled agent, I'd like to try that first.
Thanks, Todd
 
Yep, it has been reported many times, its a buggy little fella.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

I was lazy so I tried disabling the script blocking while I worked with
some reg files so they would open with the program I wanted rather than
merging directly to registry (something to do with MAS stopping the
action awaiting my approval, then when I OK it, it hands over to the
default action for the reg file- that is a known bug AFAIK, so I tried
disabling the script blocking agent).

When I tried reenabling the script blocking agent, it wouldn't. And I saw
that process execution protection had also been disabled. I don't know if
that was a bug or how it got stopped, too, unless disabling one is
supposed to disable the other.

I'm ready to reinstall, but if there is another workaround for reenabling
a disabled agent, I'd like to try that first.
Thanks, Todd
 
As I recall the update install fixes this issue--control panel, add or
remove programs, Microsoft Antispyware, Change.

However, since there's a new build .614 available since June 24th, I'd
recommend going here:

http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

and getting that build. Try an upgrade and see if that fixes the agents--it
may well not, because it probably tries to leave the current settings in
place. If it doesn't try the remedy in the first paragraph, but with the
new build.

--

I was lazy so I tried disabling the script blocking while I worked with
some reg files so they would open with the program I wanted rather than
merging directly to registry (something to do with MAS stopping the
action awaiting my approval, then when I OK it, it hands over to the
default action for the reg file- that is a known bug AFAIK, so I tried
disabling the script blocking agent).

When I tried reenabling the script blocking agent, it wouldn't. And I saw
that process execution protection had also been disabled. I don't know if
that was a bug or how it got stopped, too, unless disabling one is
supposed to disable the other.

I'm ready to reinstall, but if there is another workaround for reenabling
a disabled agent, I'd like to try that first.
Thanks, Todd
 
I had the 614 build, but I went through add/remove programs and did the
upgrade install from there. I'd seen people instructed to do that, but if
I'd known it was so painless, I wouldn't have hesitated to do so myself.
I thought it was going to redownload the program, etc., but it just fixed
the program as if it had been newly installed and that worked fine for
me.
As I recall the update install fixes this issue--control panel, add or
remove programs, Microsoft Antispyware, Change.
Click to expand...
However, since there's a new build .614 available since June 24th, I'd
recommend going here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=321CD7A2-6A57-4C5
7-A8BD-DBF62EDA9671&displaylang=en

and getting that build. Try an upgrade and see if that fixes the agents--it
may well not, because it probably tries to leave the current settings in
place. If it doesn't try the remedy in the first paragraph, but with the
new build.

I was lazy so I tried disabling the script blocking while I worked with
some reg files so they would open with the program I wanted rather than
merging directly to registry (something to do with MAS stopping the
action awaiting my approval, then when I OK it, it hands over to the
default action for the reg file- that is a known bug AFAIK, so I tried
disabling the script blocking agent).
Click to expand...
 
BTW, replacing the gcUserData.gcd file with a copy from before the
change, either confused MSAS of caused it to reset so that I was facing
the post installation screen when I restarted Antispyware. (Where I was
asked whether to allow the Security Agents, Auto Updating, etc., but I
was doubtful of the program's integrity like that so I went to add/remove
programs and did the upgrade from there so I could feel confident that
all was as it should be.)
As I recall the update install fixes this issue--control panel, add or
remove programs, Microsoft Antispyware, Change.
Click to expand...
However, since there's a new build .614 available since June 24th, I'd
recommend going here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=321CD7A2-6A57-4C5
7-A8BD-DBF62EDA9671&displaylang=en

and getting that build. Try an upgrade and see if that fixes the agents--it
may well not, because it probably tries to leave the current settings in
place. If it doesn't try the remedy in the first paragraph, but with the
new build.

I was lazy so I tried disabling the script blocking while I worked with
some reg files so they would open with the program I wanted rather than
merging directly to registry (something to do with MAS stopping the
action awaiting my approval, then when I OK it, it hands over to the
default action for the reg file- that is a known bug AFAIK, so I tried
disabling the script blocking agent).
Click to expand...
 
And the Security Agents seemed to have been reset by that, but as I said
I wanted to have more faith that the program really was setup correctly.
 
The update install really does reset things that even an uninstall/reinstall
doesn't Your observations about replacing that particular .GCD file is
probably relevant--one thing I've observed with some of these files at
least--deleting them results in the file being reconstucted--I believe in
the default state for a fresh install--although with definition files, my
experience is that they get put back as the latest version--wish I knew how!
 
Back
Top