Re: How do I get rid of startup screen of User names? SP2 seems to ha

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ok, I am sort of confused. Here is what I did, just so I haven't left
anything out. I installed WinXP and SP2. I then installed a slew of
software while I was at it, when I rebooted, I of course got the START
UP screen (which I hate). I then followed instructions on here to get
rid of start-up screen. Then, I lost most of the programs I installed
(lost meaning, did not have access to for some reason). In the same
moment, I could not install any programs because I did not have admin.
privileges. I am guessing my main user "DAVID" - the one where I
installed everything - is the admin. And when I disabled the START UP
screen, it defaulted to a GUEST, right? IS there anyway I can get rid
of the START UP screen, and it will default to the admin without
passwords and the START UP screen? I am the only one that uses this
computer and after everything is installed, it will be SANS internet
being that it is my editing machine only. So, am I stuck reinstalling
XP (which would suck because of the time involved) or am I stuck with
the START UP screen? Thanks, I hope this is clear enough with enough
info on what I am doing and have done.



"David D" wrote:
Against my better judgement, I should have put SP2 on my machine, it
is really slow booting now, sucks to be me. PArt of it is the blasted
startup screen with user names, how can I get rid of this?

It's not good practice to use the built in Administrator account. That
should have a strong password assigned then set it aside to use only if
something damages the working account. Create at least one additional
account with admin privileges (it's a good idea to have two of these, one as
a backup), and then whatever number of limited user accounts you need. If
you can run most things from a limited user account it's best to do so, but
some programs don't want to work nicely.

If running from an account with admin privileges any malware running on that
account also runs with full admin privileges. Of course the best way to
prevent problems from malware is not get infected in the first place.

--
Rock [MS-MVP User/Shell]


.

Relevant Pages

  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)
  • Re: userName="machine" didnt work
    ... Juan, ... version) than the .42 dlls. ... Deleted the ASPNET account from "Local Users and Group – ... ASPNET user and allowed the ASP.NET install to re-create it. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Alerting - Malicious software removal tool
    ... >needed to install an application that she could not install from ... >"Administrator" account. ... You failed to analyze the root cause and correct it ... use their computers to have fun. ...
    (microsoft.public.security.virus)
  • Re: Alerting - Malicious software removal tool
    ... much of what the MSRT ... yet), used MS Works, had a single account, administrator level logon ... needed to install an application that she could not install from ... only reacting AFTER the compromise. ...
    (microsoft.public.security.virus)
  • SMS MP Problem
    ... I had to install a hotfix for OSDFP and, ... account is privileged and the provider may cause a security violation if it ... 1020 SMS Site Component Manager failed to reinstall this component on this ... information by running the net user command line for the IWAM account. ...
    (microsoft.public.sms.setup)