Version 615 / Version 614

  • Thread starter Thread starter Daniel Thomas
  • Start date Start date
D

Daniel Thomas

i am having a similar problem as a lot of people with version 615 is there
any chance i could get a link/email me the version 614 installer so i can
use it untill the error is fixed
 
Better specify what the problem is. The older version isn't available from
Microsoft, and I know of no insurmountable issue with the new one.
 
Bill Sanderson,

If you are truly unaware of any insurmountable issues with
the latest build, please read the thread "Version 615"
from July 22, 2005. Or perhaps you have a resolution to
this issue?

Kevan Brown
 
The beta has never been specified to work correctly for multiple profiles on
the same machine, even if they are all administrators.

I don't have an explanation for why the experience with build .615 is
different from previous builds, but since this usage isn't within the spec
for the beta product, I don't think a lot of resources are going to be
expended digging into it.

I'm sorry that folks who have found this to work previously are now finding
that it fails, but I'm not at all sure whether this is due to changes in the
beta code, or simply the underlying issue catching up with your install.

I realize that this sounds pretty weak, but the nature of this beta--where
there are constraints on fixing issues with beta1 in favor of work on beta2,
makes this kind of response necesssary more often than I'd like.
--
 
I've found a fix to the multiple user profile problem with
build 615.

Apparently someone (I'm guessing the Microsoft AntiSpyware
installer) is screwing with the permissions on the
HKEY_LOCAL_MACHINE\SOFTWARE\Classes key. Once you
explicitly grant the SYSTEM account Full Control on this
key, the key's permissions are reset to their default
inheritable settings.

When the Microsoft AntiSpyware build 615 installer creates
its own COM registry entires, it is setting their
permissions so that only the profile who installed the
software can access them. Resetting the permissions on
the previously mentioned key resolves this.

Kevan Brown
 
Thanks, Kevan. I'm checking into this a little. I've seen similar info
posted by others, so you may be quite correct.

I really don't expect to see further changes to the beta1 code--I expect the
next new code we see will be beta2, but I've been wrong before. I'll make
sure this information is passed to folks who can make sure that beta2 is
operating as designed.

--
 
Back
Top