Windows 11/10 Shows Only Other User? Restore Your Sign-In Tile and Check Account Access

Before changing accounts or sign-in policies​

Start with the sign-in checks, even if the problem appeared after an update. Do not delete the account, create a replacement profile, or reset Windows simply because its picture has disappeared.

Keep these boundaries in mind:

• You need working administrator access for account activation and policy changes. If no authorized administrator can sign in, use the recovery options at the end instead.
• The policy-editor procedure is for Windows Pro, Enterprise, and Education. Windows Home does not include Local Group Policy Editor. Do not install an unofficial “enable gpedit” package to follow this guide.
• On an employer- or school-managed computer, ask IT before changing policy. A hidden username may be an intentional privacy requirement, and centrally configured policies can override local changes.
• Save open work before signing out. Signing out closes your session; locking the computer does not.

Record each original setting before changing it. Change only one relevant setting at a time, then test. This makes it possible to identify the cause and undo an unsuccessful change without resetting unrelated security settings.

1. Try the existing account through Other user​

The first goal is to establish whether the account still works—not to make its tile reappear.

1. Select Other user if it is not already selected.
2. Enter the username for the account you normally use:

• Local account: Enter the local username, rather than assuming the display name is the username.
• Personal Microsoft account: Use the Microsoft account email address associated with your Windows sign-in.
• Work or school account: Use the sign-in name supplied by your organization. A traditional domain account may use a qualified name such as DOMAIN\username.

1. If Sign-in options is available, select the method you actually intend to use.
2. If the field requests a password, enter the account password—not your Windows Hello PIN.
3. Submit the credentials and note the exact result.

Before another attempt, check the keyboard language indicator, Caps Lock, and the characters you are entering. For an online sign-in problem, check the network connection using the network control on the sign-in screen. Avoid repeatedly guessing credentials. Microsoft’s Windows sign-in troubleshooting guidance specifically recommends checking password entry and connectivity before moving to recovery.

Use the outcome to choose your next step:

• Your usual desktop opens: Continue with the account and policy checks below.
• Windows rejects the password or says the account is disabled: Investigate account access before changing tile-display policies.
• Windows signs in but reports “We can’t sign in to your account,” or opens a temporary profile: Treat that as a profile-loading problem, not simply a missing sign-in tile.

2. Check the account and its sign-in methods​

Once you can enter Windows, inspect the account configuration without changing it.

1. Open Settings > Accounts > Your info to review the account you are currently using.
2. Review other configured users:

• Windows 11: Settings > Accounts > Other users.
• Windows 10: Settings > Accounts > Family & other users.

1. If the device has an organizational connection, inspect Settings > Accounts > Access work or school. Do not select Disconnect as a troubleshooting shortcut.
2. Open Settings > Accounts > Sign-in options on either Windows version and review the available authentication methods.

Two settings are easy to confuse with account visibility:

• Only allow Windows Hello sign-in for Microsoft accounts on this device controls whether password authentication is available for those accounts.
• Show account details on the sign-in screen controls display of details such as the account email address.

Neither should be treated as a general “restore all user tiles” switch. Do not remove your PIN or change passwordless settings merely to troubleshoot the text Other user.

Also distinguish a Windows sign-in account from an account used only by an application. An account added under Email & accounts is not evidence that a separate Windows user has been configured. Use the Windows user-account controls when checking who can sign in to the computer.

3. Check whether the local account exists and is active​

Use this check for a local account, from a working administrator session. It is not a directory-wide check of Microsoft Entra or Active Directory accounts.

1. Search for Command Prompt, then select Run as administrator.
2. List the computer’s local accounts:

net user

1. Inspect the intended account, replacing the placeholder with its exact name:

net user "AccountName"

1. Review Account active and any expiration or sign-in restrictions in the output. These commands inspect accounts; they do not reset passwords.

Warning: Enable an account only if you own or administer it and have confirmed it should be usable. Do not enable built-in or unfamiliar accounts simply because they appear in the list.

If the intended local account is disabled and reactivation is authorized, run:

net user "AccountName" /active:yes

Run the account-inspection command again, then test sign-in. To restore a previously disabled state, use the following command from another working administrator account, not from your only usable account:

net user "AccountName" /active:no

Microsoft documents /active:yes and /active:no as the enable/disable controls. Activation does not correct a forgotten password or remove other account restrictions.

If the expected local account is absent, stop this branch. Do not create a same-named replacement as a tile repair. First establish whether the original sign-in used a Microsoft account, an organizational account, or a local account, and preserve any existing user data.

4. Review the policy that hides the last signed-in user​

This is the most directly relevant policy when Windows presents a generic username-and-password prompt instead of the previous user’s tile.

Privacy warning: Disabling this setting exposes the last signed-in user’s identity on the sign-in screen. Leave it enabled if that is required on a shared, public-facing, or managed device.

On a computer you are authorized to administer:

1. Open Start, type secpol.msc, and press Enter.
2. In Local Security Policy, expand Local Policies, then select Security Options.
3. Open Interactive logon: Don’t display last signed-in.
4. Record its existing setting.
5. If it is Enabled, and showing the previous user is appropriate, select Disabled, then OK. If it is already disabled, leave it unchanged.

Microsoft documents the distinction clearly: enabled hides the last user’s name and tile; disabled allows them to appear. This controls presentation, not whether the account exists. Microsoft also states that this policy change does not require a restart. Save your work and sign out to test a fresh sign-in screen.

If you prefer Local Group Policy Editor, the equivalent location is:

Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

The policy is named Interactive logon: Don’t display last signed-in on Windows 10 version 1703 and later, including Windows 11. Older Windows 10 installations used Interactive logon: Do not display last user name.

Rollback: Reopen the same policy and restore its recorded value. If the setting is unavailable or centrally controlled, stop and contact the administrator rather than trying registry overrides.

5. Check local-user enumeration only on domain-joined PCs​

This is a separate setting. Showing the last signed-in user and listing local accounts on a domain-joined computer are not the same task.

Privacy warning: Listing local users makes those account names visible at sign-in. Change this only with approval on a domain-managed computer.

1. Press Windows + R, enter gpedit.msc, and press Enter.
2. Open Computer Configuration > Administrative Templates > System > Logon.
3. Open Enumerate local users on domain-joined computers.
4. Record its current value.
5. If local-account tiles are specifically required, select Enabled, then OK. Microsoft documents that Disabled or Not Configured does not enumerate local users on domain-joined computers.
6. Save your work and test after signing out.

Do not use this as a blanket fix for a personal PC, and do not assume it lists every organizational user. Its documented purpose is local users on domain-joined computers. Restore the original setting to roll back.

If the actual symptom is missing Switch user controls, inspect Hide entry points for Fast User Switching in the same policy folder. Enabled hides those controls; Disabled or Not Configured makes them accessible. This is not a substitute for the last-signed-in policy. Record and restore its original value if testing it does not help.

6. Verify access and tile behavior separately​

After the relevant change:

1. Save open documents.
2. Press Ctrl + Alt + Delete and select Sign out.
3. Inspect the sign-in screen.
4. Sign in to the intended account and confirm you reach the expected desktop.
5. Record whether the account works, whether its tile appears, and whether other required sign-in methods remain available.

Do not treat a remaining Other user option as a failure. It is also a legitimate way to enter credentials for another account. Your success criteria are reliable access and the intended display behavior—not eliminating that option altogether.

If the tile is still missing or the setting changes back​

The policy is already disabled: Do not repeatedly toggle it. Check account status, account type, and—only where applicable—the domain local-user enumeration policy. These settings address different conditions.

A local setting returns to its previous value: Ask IT to check effective policy. Microsoft notes that domain policy can override local security settings. An administrator can collect a Group Policy report from an elevated Command Prompt:

gpresult /h "%TEMP%\signin-policy.html"

Open the generated HTML file from the temporary folder. It reports resultant Group Policy; do not treat it as a complete inventory of every device-management setting. On ARM64 Windows, Microsoft specifies the gpresult executable under SysWOW64 for HTML output:

%windir%\SysWOW64\gpresult.exe /h "%TEMP%\signin-policy.html"

Share the report only through an approved support channel because it contains configuration information.

The policy editor is missing: On Windows Home, Local Group Policy Editor is not included. Continue with account verification or supported recovery; do not download replacement system tools.

No account can sign in: Stop trying to edit display policy. For a local account, use Reset password and the configured security questions when offered, or a previously created password-reset disk. For a Microsoft account, use Microsoft’s account recovery process. For a work or school account, contact the organization’s administrator.

Do not select Safe Mode as a way around forgotten credentials: Microsoft states that PIN and biometric sign-in are unavailable there, so you need the account password. When escalating, provide the Windows edition, account type, exact error text, whether manual sign-in succeeds, and the policy values you recorded—never your password, PIN, or recovery codes.