My XP-Home-SP3 system recently developed the habit of giving an error
pane during Start Up. I click to close it but I'd like to avoid it. I
don't think I did anything to cause it, and suspect that some 'automatic
update' may have caused it. Here it is:

http://bellsouthpwp.net/b/i/billurie/accdenyerror.jpg

Any clues?

William Lurie wrote:

> My XP-Home-SP3 system recently developed the habit of giving an error
> pane during Start Up. I click to close it but I'd like to avoid it. I
> don't think I did anything to cause it, and suspect that some 'automatic
> update' may have caused it. Here it is:
>
> http://bellsouthpwp.net/b/i/billurie/accdenyerror.jpg
>
> Any clues?

You used msconfig to disable an NT service (you disabled some items in
msconfig to have it do a diagnostic startup). You aren't logging on
under an admin-level account to have msconfig disable that service when
you next reload Windows. So have you tried logging on under an
admin-level account?

When you install Windows XP, you get one default Administrator account.
That account should only be used in dire emergencies. You should
immediately create a 2nd admin-level account (i.e., it is assigned to
the Administrators group) and use that alternate admin account for all
your admin tasks. If the profile for an account gets corrupted, you
can't log onto it. So don't use the Administrator account as your
normal admin account; otherwise, if you only have the Administrator
account and its profile gets corrupted, you won't be able to login under
it to do any admin tasks.

XP Home requires you to reboot into Safe Mode to get into the
Administrator account. If you had the Pro version, you could just
logoff your current account and login under the admin account (or use
Fast User Switching). If you created an alternate normal-usage
admin-level account, logoff and logon using that alternate admin
account.

Rather than use msconfig to disable NT services, just run services.msc
and disable the service yourself. Of course, you must be logged in as
an admin to alter state of NT services.

VanguardLH wrote:
> William Lurie wrote:
>
>> My XP-Home-SP3 system recently developed the habit of giving an error
>> pane during Start Up. I click to close it but I'd like to avoid it. I
>> don't think I did anything to cause it, and suspect that some 'automatic
>> update' may have caused it. Here it is:
>>
>> http://bellsouthpwp.net/b/i/billurie/accdenyerror.jpg
>>
>> Any clues?
>
> You used msconfig to disable an NT service (you disabled some items in
> msconfig to have it do a diagnostic startup). You aren't logging on
> under an admin-level account to have msconfig disable that service when
> you next reload Windows. So have you tried logging on under an
> admin-level account?
>
> When you install Windows XP, you get one default Administrator account.
> That account should only be used in dire emergencies. You should
> immediately create a 2nd admin-level account (i.e., it is assigned to
> the Administrators group) and use that alternate admin account for all
> your admin tasks. If the profile for an account gets corrupted, you
> can't log onto it. So don't use the Administrator account as your
> normal admin account; otherwise, if you only have the Administrator
> account and its profile gets corrupted, you won't be able to login under
> it to do any admin tasks.
>
> XP Home requires you to reboot into Safe Mode to get into the
> Administrator account. If you had the Pro version, you could just
> logoff your current account and login under the admin account (or use
> Fast User Switching). If you created an alternate normal-usage
> admin-level account, logoff and logon using that alternate admin
> account.
>
> Rather than use msconfig to disable NT services, just run services.msc
> and disable the service yourself. Of course, you must be logged in as
> an admin to alter state of NT services.

Thanks for all the info, but none of that should be necessary. This
change occurred after almost four years, and only after uninstalling
NAV2009 and installing 360. As for what if something gets corrupted, I
always have many full system clones to switch in.

Apparently (see previous response) Norton knew of their boo-boo and
provided a fix. But thanks again for the info.