Use a Standard Account in Windows 11 for Daily Use

Most Windows tasks do not need administrator rights. Browsing, playing games, editing documents and using most apps can happen in a standard user session. The important difference appears when something asks to change the whole PC: an administrator can approve that request, while a standard user needs credentials for an administrator account.

Microsoft recommends using standard accounts for day-to-day work and keeping the number of administrators low. The safest way to make that change is to create and test a separate administrator account first, then change your usual account to Standard. Microsoft’s account guidance and User Account Control documentation explain the underlying settings.

This guide is for a personal Windows 11 PC. If your computer belongs to a workplace or school, ask its IT administrator before changing account types; organisation policy may control the options.

What “standard” and “administrator” actually change

A Windows account has a permission level as well as a sign-in identity. A Microsoft account or a local account can be assigned a Windows account type. The sign-in choice and the permission level answer different questions.

Windows account type	What happens with everyday apps	When a task needs administrator rights
Administrator	With User Account Control (UAC) enabled, ordinary apps usually start with a standard user token.	Windows normally asks the administrator to approve elevation.
Standard user	Apps run with the rights available to that user.	Windows normally asks for administrator credentials before the task can be elevated.

Microsoft explains that even a person in the Administrators group uses a standard user token for ordinary apps. UAC switches to the administrator token only when an elevated action is approved. A standard user instead sees a credential prompt for an administrator account. Those defaults can be changed by a work or school policy. Read how UAC works .

That difference adds a useful pause before software can make system-wide changes. It does not make the account a sandbox. A program running as you can still access files and settings your account can reach, and a deceptive prompt can ask for credentials. UAC is a permission control, not a verdict that an app is safe. Check the publisher and download source before approving an unexpected request. Microsoft’s UAC overview describes the boundary and its limits.

Keep one working administrator account

Do not change your only administrator account to Standard. If you do, Windows may ask for credentials you cannot provide when you need to install software or change a system setting.

If you already have a separate administrator account, sign in to it once and make sure you know its sign-in credentials. You can skip to “Change your everyday account to Standard.”

If your everyday account is the only administrator, create a separate one first:

While signed in to your current administrator account, open Start → Settings → Accounts → Other users.
Under Add other user, select Add account.
To use an existing Microsoft account, enter its email address. To create a local account, select I don’t have this person’s sign-in information, then Add a user without a Microsoft account. Follow the prompts to finish.
Under Other users, select the new account and choose Change account type.
Select Administrator, then OK.

These are Microsoft’s documented Windows account controls. A local account is optional; you can use a Microsoft account for the separate administrator instead. Use a unique, strong password for the new account and keep it somewhere you can retrieve it securely.

Now sign out and sign in to the new administrator account. Confirm that it opens successfully. If you cannot sign in or are unsure which account is an administrator, stop here and resolve that before changing your everyday account.

Change your everyday account to Standard

Stay signed in to the separate administrator account you just tested. Open Start → Settings → Accounts → Other users.

Select your usual account, choose Change account type, select Standard User, then choose OK. Windows changes that account’s permissions; it does not create a new profile or move your documents. Sign out of the administrator account and return to your usual account.

Open the apps and files you use regularly. Your desktop, documents and app settings should still be associated with the same Windows profile. Creating a brand-new standard account instead would create a separate profile, with its own settings and files; they do not automatically move over.

What to expect from an elevation prompt

Some installers, driver changes and system settings need administrator rights. When you start one from a standard account, Windows may ask for the administrator account’s credentials. This is expected for a task that changes the PC for all users. Some apps install only for your account and may not need elevation.

Before entering credentials, ask:

Did I start this action, or did the prompt appear unexpectedly?
Did I get the installer from the software maker or another source I trust?
Does the publisher and requested change make sense for the task?

If you cannot answer those questions, cancel and check first. A UAC prompt only signals that the action needs elevated rights; it does not certify the program. Older apps may also be designed around administrator access. Update them or check the developer’s guidance rather than giving your everyday account administrator rights just to avoid prompts.

If a work or school device blocks the change, do not try to work around its management settings. Ask the administrator who manages it.

If something stops working

Sign out of your everyday account and return to the administrator account. In Settings → Accounts → Other users, select your everyday account, choose Change account type, and set it back to Administrator if you need to reverse the change.

A standard account is a practical default for routine use when you can keep a separate administrator account available. The benefit is that an app needs an additional credential before it can elevate from your everyday session. Keep the administrator account protected and use it only when a change you understand requires those rights.

Sources and date boundary

The account-management steps and UAC behaviour in this guide reflect Microsoft documentation available by 2 July 2026. Windows labels can differ slightly across builds, and organisation policies can change account controls or prompts.