Clear, practical technology insights BSOD Code Lookup · Windows Error Code Lookup · Wi-Fi Troubleshooting · PC Troubleshooting Checklist

How to Enable or Disable the Built-In Administrator Account in Windows

Enable the built-in Windows Administrator account for recovery, set a password safely, sign in, and disable the account again when finished.

Table of Contents

Most people should use a normal administrator account and approve individual elevation prompts through User Account Control (UAC). Windows also includes a separate, disabled built-in Administrator account for recovery and advanced administration. Enable it only when a specific troubleshooting task requires it, then disable it again.

Signing in to this account is not a safe way to eliminate prompts during everyday use. It has unusually broad privileges, and software launched from it can make system-wide changes more easily.

Before you enable the built-in Administrator

  • You must already be signed in to an account that can approve administrator actions.
  • On a work or school PC, use the organization's support process instead of changing local accounts.
  • Set a strong password before signing in to the account.
  • Do not leave the account enabled after the recovery task is complete.

Enable the account with Command Prompt

Step 1: Open Start, type Command Prompt, and select Run as administrator. Approve the UAC prompt.

Opening Command Prompt as an administrator in Windows

Step 2: Enter the following command:

net user Administrator /active:yes

Windows should respond that the command completed successfully.

Enabling the built-in Administrator account with net user

If Windows uses a localized name for the built-in account, the English name may not work. An administrator can identify the local account with the well-known SID ending in -500 rather than guessing its name.

Enable the account with PowerShell or Windows Terminal

Step 1: Search for PowerShell or Terminal, then choose Run as administrator.

Opening PowerShell as an administrator

Step 2: You can run the same command:

net user Administrator /active:yes

Successful Administrator account activation in PowerShell

On systems with the LocalAccounts PowerShell module, this command is another option:

Enable-LocalUser -Name "Administrator"

It can still require the localized account name.

Set a password without exposing it in the command

Do not place the password directly after the account name, because it can remain visible on screen or in command history. From an elevated Command Prompt or Terminal window, enter:

net user Administrator *

Windows asks for the new password twice and does not display the characters while you type.

Setting a password for the Windows Administrator account

Use a unique password and store it securely. An enabled built-in Administrator account without a password creates unnecessary risk.

Sign in to the built-in Administrator account

  1. Save your work in the current account.
  2. Open Start, select your account picture, and choose Sign out or Switch user.
  3. Select Administrator on the sign-in screen.
  4. Enter the password you just set.

If the account does not appear, restart once and verify that the activation command succeeded. Do not use the account as your regular profile; settings, files, and browser data are separate from your normal user account.

Disable the account when finished

Return to your normal administrator account, open Command Prompt, PowerShell, or Terminal as an administrator, and run:

net user Administrator /active:no

A successful message confirms that the built-in account can no longer be used to sign in. Disabling it does not delete your ordinary administrator account.

Built-in Administrator vs. a normal administrator account

Account typeRecommended useUAC behavior
Standard accountEveryday work with limited rightsRequires administrator credentials for elevated actions
Normal administratorEveryday administrationUsually prompts before elevation
Built-in AdministratorShort-term recovery or advanced maintenanceHas different elevation behavior and broader default privileges

Keep UAC enabled on normal accounts; the endpoint security overview explains why account controls remain an important protection layer. When stepping away from an elevated session, lock the computer rather than leaving it accessible.

Discussion

Reader Comments 0

Sign in with email or Google to join the discussion.