Gordon said:
Firstly, read this:
It is NOT good practice to use just the built-in administrator account for
day-to-day use.
Good advice.
If that account becomes corrupted, there is NO WAY you can
access your machine without doing a repair install of XP. Create another
user account (give it Admin rights if you want) and use that one for
day-to-day use.
Bad advice. Giving your day to day user admin rights is just as stupid and
insecure as logging in as Administrator directly. Nobody should ever log
in with Administrator privileges unless there is no way to avoid doing so,
and then only long enough to complete said task. You can work around this
using the Run as... task when something has to be root/admin for some odd
reason (and that program should also be system maintenance related and not
some userspace program like email or Office[1]). Leave administrator
privileges for emergencies and system maintenance.
Leave the built-in administrator account for emergencies.
Good advice.
[1] Yes, I am aware this advice breaks some software (like MS Office). I
still say this is a Good Thing: You should not be using software that
insists on running only in the least secure possible configuration, even if
it's a "lone machine that only you use." What kind of machine do you think
malware writers are trying to target for botnets? The lone machines
that "nobody else uses" and thus "doesn't need to be secure." There is no
such thing as "doesn't need to be secure," there never has, and there never
will be.