Not one of my better "Thinking" days I'm afraid, but that may have helped to
narrow a few possibilities down.

I suppose it is possible that this is connected with a registry entry not
being "Read' properly, your saving the registry by closing regedit may have
triggered something to be read that wasn't being read before...

Do post again if anything changes or changes back please.

Charlie

"BCG" <BCG@discussions.microsoft.com> wrote in message
news:508CEDA6-F450-4B81-AE48-E5C3E5833E8B@microsoft.com...
> Here's A thought...
>
> My Dad was looking at some knowledge base articles, and came across this
> one:
>
> http://support.microsoft.com/Default.aspx?id=883256
>
> He looked at a few of the suggestions and solutions listed on that page,
> and
> on a couple others. He started looking at ActiveX controls, and tried to
> look
> at the settings in start/run/gpedit.msc. This computer would not open it
> up,
> saying it could not be found. Then he went to the registry keys listed in
> the
> above KB article, and even though there was nothing different, something
> in
> what he did changed something, because when he logged into another
> account,
> Microsoft Anti-Spyware popped up a window asking for approval of a browser
> modification, and all of a sudden problem's solved.
>
> We haven't the slightest idea of how our looking at registry keys and
> trying
> to open gpedit.msc, when he changed nothing, caused the browser to be
> "modified" and thereby fixed.
>
> Can you guys think of anything??!