Bug Report on MSASB

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The last five or six machines that I have been working on have given
me an error when attempting to start microsoft antispyware beta in
safe mode without networkings. The error given is X Unexpected error.
Beta will then hang on the loading screen and finally give a has
encountered an error and must shut down prompt several minuets later.
Unsure as to the cause.
 
What is the general sequence of operations on these machines--it sounds like
you are doing some specific set of steps--what are they? I could imagine
that there's a check for updates that is part of the startup, and that might
be hanging up somehow in safe mode with no network available--but I've run
Microsoft Antispyware in this mode a number of times and not had problems.
 
Bill Sanderson said:
What is the general sequence of operations on these machines--it sounds like
you are doing some specific set of steps--what are they? I could imagine
that there's a check for updates that is part of the startup, and that might
be hanging up somehow in safe mode with no network available--but I've run
Microsoft Antispyware in this mode a number of times and not had problems.

"Reclaimer" wrote:
Click to expand...

One each machine I first load our client Symmantec AV, update scan. I
then load microsoft antispyware and update it. I then boot the machine into
safe mode and run both symmantec and micro antispyware. I have tried just
starting antispyware by itself without symmantec but it gives the same error.
 
It'd be interesting if, after doing the Microsoft Antispyware update while
still online, you could check--go to Help, About, and hit the Diagnostics
button, and verify that the line ending in something like 148/148 has both
numbers equal--whatever they are.

I'm wondering if the definitions are really complete before you are
restarting in safe mode without networking. (Not saying you are doing
anything wrong, by any means--just trying to see if there's a way to spot
what is happening--or prevent it.)

(If you do see unequal numbers, repeat File check for update until they are
equal.)

--
 
All of the machines that I have been working with are winxp sp2 fully
updated. The error that eventually comes up after the "unexpected error;
quitting" is the critical error (error 101) which then prompts a
reinstall...which does nothing. IK checked uder the diagnostics and the
updates were 148/148. I did not notice anything else dif. from other working
version. Antispyware loads fine in standard mode but this safe mode thing is
persistant...just came across another today...an acer travel companion
laptop.
 
Are you logging in using the same user when in safe mode as you are in
regular mode?

--
 
Whoa....didn't think of that. I have been going in under admin usually. I
will try staying under user and see if that makes a diff.
 
This kind of error often seems to be the result of bugs in the product
relating to multiple users--some keys in the registry are apparently set
with overly-restrictive permissions--according to some who've investigated
the details.

There are problems even when all users are admins, in some cases--and
definitely at least spurious prompts when some users are admins and others
not.

I'd recommend installing and running under the same user as much as
possible. --and if your users are not local admins--this isn't gonna work
too well. One reason (of many) they don't recommend use on production
equipment.

Beta2 will definitely be VERY different in terms of these issues--there will
be a process running as a service, and a foreground gui--separate processes,
and sets of permissions.

--
 
Back
Top