Start by fixing the issue: the Switch User option is missing or doesn’t work because User switching doesn’t work in Windows 10. This commonly happens when Fast User Switching is disabled by policy or registry, required services or shell components are broken, the system is in Assigned Access (kiosk) mode, or third-party software interferes. In this article you’ll learn the nine most common causes and step-by-step fixes to restore the Switch User feature safely.
Key Takeaway
The quickest reliable fix is to re-enable Fast User Switching (via Group Policy or the registry), ensure the User Profile Service and RPC are running, repair system files with SFC/DISM, and restart explorer.exe; if the profile is corrupted, create a clean local account and migrate data.
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| Fast User Switching disabled by Group Policy | Open gpedit.msc and set Hide entry points for Fast User Switching to Not Configured/Disabled. |
| Fast User Switching disabled in Registry | Delete or set HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\HideFastUserSwitching to 0. |
| Switch User hidden by Ctrl+Alt+Del policies | Re-enable relevant policies in gpedit.msc (Interactive Logon / Ctrl+Alt+Del settings). |
| Required services stopped (User Profile Service, RPC) | Start or restart User Profile Service and Remote Procedure Call (RPC) in services.msc. |
| Corrupted user profile | Create a new local account, copy user data from the old profile, then delete the broken profile. |
| Kiosk/Assigned Access mode active | Disable Assigned Access under Settings > Accounts > Family & other users or remove kiosk configuration. |
| Explorer or shell problems | Restart explorer.exe from Task Manager or restore Userinit/Shell registry values. |
| System file corruption | Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow. |
| Third-party software conflicts | Perform a Clean Boot (disable non-Microsoft services) and uninstall interfering utilities. |
Detailed Fixes for “User switching doesn’t work in Windows 10”
1. Fast User Switching disabled by Group Policy
Why it causes the problem
- Windows exposes Switch User via the Fast User Switching mechanism. Group Policy can hide entry points for Fast User Switching, removing the Switch User option.
Step-by-step solution
- Press Win + R, type gpedit.msc, and press Enter.
- Go to Computer Configuration > Administrative Templates > System > Logon.
- Find Hide entry points for Fast User Switching.
- Double-click it and set it to Disabled or Not Configured. Click OK.
- Run gpupdate /force in an elevated Command Prompt to apply changes immediately.
Notes
- Group Policy Editor is not available on Windows 10 Home. If you’re on Home, use the registry fix (next section).
2. Fast User Switching disabled in Registry
Why it causes the problem
- The same setting can be controlled by a registry value; when set to 1, Windows hides the Switch User option.
Step-by-step solution
- Press Win + R, type regedit, and press Enter.
- Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
- Look for HideFastUserSwitching (DWORD). If present and set to 1, double-click it and change to 0.
- If the value doesn’t exist, you don’t need to add it unless you suspect a policy previously created it — in which case delete it.
- Reboot the PC.
Commands (optional)
- To disable via command line (Admin):
reg add “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System” /v HideFastUserSwitching /t REG_DWORD /d 0 /f
Notes
- Back up the registry before editing: File > Export in Registry Editor.
Why it causes the problem
- Some policies that control interactive logon and Ctrl+Alt+Del options may hide elements from the sign-in UI, indirectly removing Switch User.
Step-by-step solution
- Open gpedit.msc.
- Check settings under Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options, especially Interactive logon: Do not display last user name and similar entries — these don’t normally hide Switch User but misconfiguration can cause related UI changes.
- Also verify in Computer Configuration > Administrative Templates > System > Logon that settings that remove sign-in options aren’t enabled.
- Set questionable policies to Not Configured, then run gpupdate /force and restart.
Notes
- Many corporate environments enforce interactive logon policies via domain GPO; contact IT if you’re on a domain.
4. Required services stopped (User Profile Service, RPC)
Why it causes the problem
- User switching relies on system services such as User Profile Service and Remote Procedure Call (RPC); if they’re stopped or failing, switching can fail.
Step-by-step solution
- Press Win + R, type services.msc, and press Enter.
- Locate User Profile Service. If it’s stopped, right-click and choose Start, or Restart if applicable.
- Locate Remote Procedure Call (RPC) and ensure the Startup type is Automatic and the service is running.
- If a service won’t start, note the error and check Event Viewer (run eventvwr.msc) for specific service errors.
Commands (optional)
- To check service status in elevated Command Prompt:
sc query “ProfSvc” (User Profile Service)
sc query “rpcss” (RPC)
Notes
- Don’t disable RPC — it’s critical to Windows operation.
5. Corrupted user profile
Why it causes the problem
- If a user profile is corrupt, Windows may be unable to create or resume sessions for that user. Switch User may appear to fail when attempting to load the corrupted profile.
Step-by-step solution
- Create a new local administrator account: Settings > Accounts > Family & other users > Add someone else to this PC > I don’t have this person’s sign-in information > Add a user without a Microsoft account.
- Sign in to the new account to verify switching works.
- If it does, copy files from the old profile: navigate to C:\Users\
and copy documents, desktop, downloads, and AppData\Local\Packages carefully (note: prefer application-specific export/import when possible). - If you must repair the old profile, open regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Look for the SID with a .bak entry — follow Microsoft guidance to rename keys carefully only if you know what you’re doing.
Notes
- Don’t copy NTUSER.DAT; it contains registry user settings and copying may transfer corruption.
- Always back up user data before deleting a profile.
6. Kiosk / Assigned Access mode active
Why it causes the problem
- Assigned Access (kiosk mode) locks the PC to a single app/account and removes user-switching and sign-in options.
Step-by-step solution
- Open Settings > Accounts > Family & other users.
- Under Set up assigned access (or Set up a kiosk in some builds), click it and Remove kiosk or change configuration to None.
- Reboot the system.
Notes
- If the device is managed by an organization and configured as kiosk, contact IT or the device admin to remove Assigned Access.
7. Explorer or shell problems prevent the UI from showing
Why it causes the problem
- The Switch User option is presented by the shell and the logon UI; corrupted or crashed explorer.exe or incorrect Userinit/Shell registry values can prevent the Switch User UI.
Step-by-step solution
- Restart explorer.exe:
- Press Ctrl + Shift + Esc to open Task Manager.
- Under Processes, select Windows Explorer, click Restart.
- If Windows Explorer is not present or frozen, go to File > Run new task, type explorer.exe, and press Enter.
- Check registry keys:
- Open regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon.
- Ensure Userinit is C:\Windows\system32\userinit.exe, (note the trailing comma) and Shell is explorer.exe.
- If values are incorrect, edit them and reboot.
Notes
- Incorrect edits to these values can prevent login; back up the key before changing.
8. System file corruption (SFC / DISM)
Why it causes the problem
- Missing or damaged system files involved in logon and the shell can break user switching; repairs often restore functionality.
Step-by-step solution
- Open an elevated Command Prompt (search cmd, right-click, Run as administrator).
- Run:
- DISM /Online /Cleanup-Image /RestoreHealth
- After DISM completes, run sfc /scannow
- Reboot and test Switch User.
Notes
- DISM may take 10–30 minutes depending on system health and network.
9. Third-party software conflicts (security tools, tweaks, shell replacements)
Why it causes the problem
- Antivirus, system tweakers, shell replacements, or login managers can remove or alter sign-in functionality, preventing switching.
Step-by-step solution
- Perform a Clean Boot to isolate the problem:
- Press Win + R, type msconfig, Enter.
- On Services tab, check Hide all Microsoft services, then click Disable all.
- On Startup tab, click Open Task Manager and disable all startup items.
- Click OK and restart.
- Test whether Switch User works. If it does, re-enable services/startup items one-at-a-time to find the culprit.
- Once identified, uninstall or update the conflicting software, or contact vendor support.
Notes
- Re-enable Microsoft services and startup items after testing.
Prevention and Best Practices
- Keep Windows updated and install quality antivirus software to prevent tampering but ensure compatibility with logon UI.
- Use local admin accounts only when needed; maintain a second administrative account to recover if primary is corrupted.
- Back up important user profiles and documents regularly using File History, OneDrive, or a disk image tool.
- Avoid registry tweaks or third-party shell customizers unless you have a restore point or full backup.
FAQ
Can I switch users from the command line?
Yes — on local desktop you can use tsdiscon to disconnect your session (this returns to the lock screen where other users can sign in). Run an elevated command prompt and type tsdiscon. Note: tsdiscon is not available in some Home editions. You can also press Win + L to lock the screen and then choose a different account.
Why can’t I switch users during a Remote Desktop session?
When using RDP, your session is remote and may be bound to the logged-in user. If you need multiple interactive sessions, enable multiple RDP sessions on server/Pro editions or use separate accounts on different devices; switching within the same session behaves differently than local console switching.
Will switching users close my running apps?
No—Fast User Switching keeps sessions active in the background so running apps remain open. However, some resources (e.g., exclusive device locks) might behave differently; also background apps still consume RAM and CPU.
Is enabling Fast User Switching safe from a security standpoint?
Yes, but be aware that leaving sessions logged in allows other physical users access to your unlocked apps if you don’t lock the screen. Use a password and set screen timeout/lock policies to mitigate risk.
What if none of these fixes work — should I reinstall Windows?
Reinstalling Windows is a last resort. Before reinstalling, try an in-place repair (Windows 10 recovery that keeps files and apps) via a Windows 10 installation media: run setup.exe from the ISO and choose Upgrade to repair system files. If that fails, a clean install will fix deep system issues but back up all data first.
Conclusion
Most cases of User switching doesn’t work in Windows 10 are resolved by re-enabling Fast User Switching (Group Policy or registry), restarting or repairing the shell and required services, or repairing system files with DISM and SFC. If the problem persists, create a fresh user profile or perform an in-place repair to restore normal switching behavior.
