The above answers work, but for a novice it might be a bit difficult to get:
First you have to run regedit;
go to HKEY_LOCAL_MACHINE\SOFTWARE\Classes registry key
Right Click and go to permissions
Remove "everyone"
Add "SYSTEM" and give full access rights
Close regedit.
Reboot the system
Remove MS Antispyware
run CCleaner
reboot
reinstall MS Antispyware
Now it should work for all users
Thanks to the hint of Kevan Brown
"Lappen" wrote:
> I only wanted to say that I tested this, I added System and gave it full
> access and all the normal permissions reappeared, after that I removed
> everyone restarted the computer and it works again on the other admin users
> that it wouldn't before! So a bit THANK YOU Kevan!
>
>
>
> //Lappen
>
>
>
> "Kevan Brown" <(E-Mail Removed)> wrote in message
> news:01e001c5a4db$7edb6df0$(E-Mail Removed)...
> > Apparently when the build 615 installer upgrades an
> > earlier build of Microsoft AntiSpyware, it is screwing
> > with the permissions setting on the
> > HKEY_LOCAL_MACHINE\SOFTWARE\Classes registry key and in
> > turn setting the permissions on all of the GIANT
> > AntiSpyware COM registry keys so that only the user who
> > installed the upgrade can access them. This causes the
> > program to generate the following error message when a
> > different user logs into the system: "Unexpected Error;
> > Quitting". Eventually this produces an "Error 101" when
> > you try to launch the program manually.
> >
> > The resolution is to go explicitly grant the built-in
> > SYSTEM account Full Control on the
> > HKEY_LOCAL_MACHINE\SOFTWARE\Classes registry key. This
> > somehow then resets it so that it picks up the permissions
> > it should already be inheriting, and also resets the GIANT
> > AntiSpyware COM registry keys to the permissions they
> > should already be inheriting.
> >
> > I haven't seen this problem on any machines where build
> > 615 was installed fresh; without upgrading from a previous
> > build.
> >
> > I found that this problem also affected another Microsoft
> > installer used by Microsoft Virtual Server 2005. The same
> > fix resolved that problem as well.
> >
> > Kevan Brown
> >
>
>
>
|