Troubleshooting: Unable to Exit S Mode on Windows 11
Exiting S Mode in Windows 11 is a straightforward process that involves accessing the Microsoft Store and following specific prompts.
Quick Read
- Symptom: Exiting S Mode in Windows 11 is a straightforward process that involves accessing the Microsoft Store and following specific prompts.
- Check first: Confirm OS build, domain or workgroup state, local admin rights, and whether the host is managed by GPO, Intune, or another baseline.
- Risk: Changes system state
Symptoms
Users are unable to switch out of S Mode in Windows 11, preventing the installation of non-Microsoft Store applications.
Environment
Windows 11 operating system running in S Mode.
Most Likely Causes
S Mode limits Windows 11 to Microsoft Store apps. Exit failures usually come from Store account state, licensing, policy restrictions, network access, or a stuck Microsoft service dependency.
What to Check First
- Confirm OS build, domain or workgroup state, local admin rights, and whether the host is managed by GPO, Intune, or another baseline.
- Collect the exact error code, Event Viewer entries, and the command or UI action that triggers the failure.
- Check whether the issue follows the user profile, machine, network, or application package.
Insight Cluster
Parent question: How do we approach Windows recovery so evidence, repair-path choice, validation, and rollback are stronger than the outage pressure?
- Planning Windows Recovery and Repair Without Making the Outage Worse (parent Insight)
- Windows Evidence-First Recovery Workflow Before Repair Commands (supporting Insight)
- Comparing Windows Repair Paths: SFC, DISM, Restore, Rollback, and Reinstall (supporting Insight)
- Troubleshooting Windows 11 Restore Recovery Failures (tactical leaf)
- Error 0x80070490 When Uninstalling Windows Update (tactical leaf)
- In-Depth Troubleshooting of Windows 11 Update Errors (tactical leaf)
- Troubleshooting RDP Disconnections on Windows Server 2025 due to Security Group Misconfigurations (tactical leaf)
- Troubleshooting RDS Broker Connection Issues on Windows Server (tactical leaf)
- This Windows parent Insight is meant to keep the site from treating every repair command page as a top-level strategy article.
- The supporting pages frame evidence collection and repair-path choice before operators drop into exact failure leaves.
Fix Steps
- Check Windows Version
Ensure that your Windows 11 is up-to-date and that you are indeed in S Mode.
Example pattern only. Adjust for your environment before running.
Press Windows + I to open Settings. Navigate to System > About. Check the 'Windows specifications' section for the edition.
- Open Microsoft Store
Access the Microsoft Store to initiate the process of exiting S Mode.
Example pattern only. Adjust for your environment before running.
Press Windows + S to open the search bar. Type 'Microsoft Store' and press Enter. In the Store, search for 'Switch out of S mode'.
- Locate the S Mode Switch Option
Find the option to switch out of S Mode within the Microsoft Store.
Example pattern only. Adjust for your environment before running.
In the search results, click on 'Switch out of S mode'. Read the information provided about leaving S Mode.
- Confirm the Switch
Follow the prompts to confirm your decision to exit S Mode.
Example pattern only. Adjust for your environment before running.
Click on the 'Get' button. If prompted, sign in with your Microsoft account. Follow any additional prompts to complete the process.
- Restart Your Device
After the process is complete, restart your device to ensure changes take effect.
Example pattern only. Adjust for your environment before running.
Press Ctrl + Alt + Delete and select 'Restart'.
- Verify Exit from S Mode
Check if you have successfully exited S Mode.
Example pattern only. Adjust for your environment before running.
Press Windows + I to open Settings. Navigate to System > About. Confirm that the edition is now Windows 11 Home or Pro (not S Mode).
Validation
- The failing Windows action completes after reboot or service restart if the remediation requires one.
- Event Viewer stops logging the same error ID for the same component during a retest.
- The fix works for the affected standard user context, not only for an elevated administrator session.
Logs to Check
- Event Viewer: System, Application, Setup, WindowsUpdateClient, TerminalServices, or PowerShell logs as relevant.
- CBS.log, DISM.log, or WindowsUpdate.log when servicing or feature installation is involved.
- Security, RDP, or application-specific logs for authentication and session failures.
Rollback and Escalation
- Record the original registry, service, feature, policy, or firewall value before changing it.
- Undo temporary local policy, firewall, or service changes after validation.
- Use a restore point, VM snapshot, or exported configuration when changing servicing, boot, or security settings.
Escalate When
- Escalate if the same error persists after rollback and a clean retry from the original failing path.
- Escalate if logs show authorization, data loss, certificate, replication, or production availability risk outside the local service owner scope.
Edge Cases
- If the 'Switch out of S mode' option is not available in the Microsoft Store, ensure that your device is connected to the internet and that you are logged in with a Microsoft account.
- If you encounter an error during the process, check for any pending Windows updates and install them before retrying.
Notes from the Field
- If the machine is domain-managed, local fixes can be overwritten. Check the winning GPO or MDM policy before repeating the same change.
- Prefer read-only collection first on Windows incidents because many repair commands change component store, services, or user profile state.