

Change to Administrator or Standard with netplwiz in Windows 10 Change to Administrator or Standard user using Computer Management Change an account to Administrator or Standard from the Control Panel Change an account type to Administrator or Standard from Settings in Windows 10 First things first: About Standard and Administrator accounts in Windows 10.Just make sure that YOU are prepared to handle all of the admin tasks on their behalf. well if you don't want them being able to fiddle and change stuff on the computer, you can give them a standard account. This means it's not really necessary to artificially limit yourself by running as a standard user.

Any time a program you are running needs admin rights it will elevate via UAC so you'll know about it. if you're reasonably tech savvy, you will be aware of what you're doing and you will be making concious decisions to perform admin actions on the computer. You could argue that THOSE areas of the operating system are "vulnerable" when you use an admin account since it doesn't prompt for permission, admin users can just do stuff that standard users can't without even realizing it.īut. Implicitly allowing elevation for certain parts of the OS came about because back in the Windows Vista days when UAC was invented, people freaked the fuck out about being constantly prompted for permission to perform any admin actions on the computer, and everyone universally hated UAC without realizing what it's real purpose was, resulting in idiotic parodies like this apple commercial. But these cases are few and far between and imho not really worth any extra concern in a home environment. There are also a few places also where the UAC dialog box is suppressed and admin privileges are implicitly granted (especially certain parts of control panel, system settings, file permissions etc.), and you could argue that a standard user account would be "more secure" because the user can't modify these parts of the OS. The only real merit to it that I see would be if you feel that having to type a separate username/password into the uac dialog box will somehow "remind" you that you are performing an admin action and you're the type of person to just "click okay" on everything without reading it. However, when the SAME person is both the admin and also the user (which is almost always the case in a home environment), running as a non-admin user really is just an annoyance. It is useful when you do NOT want the user who is logged in to be performing admin tasks, such as in a business environment where IT is responsible for computer administration, and the users are not supposed to be administering the computer. That's the main difference between the two types of accounts. A standard user will not be able to do this and will be prompted to enter the username/password of an admin who can. An admin user can just click "yes" and allow the program. When you (or any program you are running) need to do something that requires admin rights, the program needs to present the User Account Control (UAC) dialog box which asks for your permission to allow the process to "elevate" itself to admin level security context so that it can perform the action.

However - and this is important - all process that run under your user account will run in the security context of a 'standard' by default ANYWAYS, regardless of if you are logged in as an admin user or not. The point of a standard account is that it can't perform administrative tasks. It's a good practice in environments where the person who uses the computer is different from the person who administers the computer.
