Windows 11 Settings Opens and Closes Immediately: How to Repair SystemSettings.exe

Quick Answer

If Windows 11 Settings displays a blank window or gear icon and then closes, first restart the computer and install any pending Windows updates. If the problem continues, reset and re-register the windows.immersivecontrolpanel package, check Event Viewer for a SystemSettings.exe crash, register the required XAML dependency packages, and then run DISM followed by SFC.

In the real troubleshooting case on which this article is based, Settings eventually started working in the original user account after a Windows update completed and the computer restarted. This was the observed resolution, although the available evidence did not prove one definitive internal cause.

Complete Article

The Windows 11 Settings app may sometimes open to a white screen, display the Settings gear for a few seconds, and then close without showing an error message. The same behaviour may occur whether Settings is opened from the Start menu, by pressing Windows + I, or by running an ms-settings: command.

This problem does not automatically mean that Windows must be reset or reinstalled. It can be caused by damaged app registration, an unavailable XAML dependency, incomplete Windows update processing, corrupted system files, or a problem limited to one Windows user profile.

This guide explains how to diagnose and repair the issue using targeted Windows commands.

Important: Sign in with an administrator account and back up important data before changing system components. Do not download replacement DLL files from unofficial websites.

Symptoms

Affected computers may show one or more of the following symptoms:

• Settings displays the gear icon and then disappears.
• A blank Settings window opens briefly and closes.
• Pressing Windows + I produces the same result.
• Running ms-settings: does not keep Settings open.
• Windows Update, Display Settings, Network Settings or other pages cannot be accessed.
• Event Viewer records an Application Error for SystemSettings.exe.
• Settings works in another Windows account but not in the original account.
• Other XAML-based Windows components may also behave abnormally.

Why does the Windows 11 Settings app crash?

The Settings application is located at:

C:\Windows\ImmersiveControlPanel\SystemSettings.exe

Although it looks like a normal desktop application, it relies on Windows AppX registration and several Windows interface components. One important dependency is:

C:\Windows\System32\Windows.UI.Xaml.dll

Microsoft has documented situations in Windows 11 24H2 and 25H2 where XAML-dependent components can fail because required packages are not registered at the correct time after Windows updates. Affected components can include Settings, Start, Search, Taskbar and Explorer. Microsoft identifies packages such as MicrosoftWindows.Client.CBS, Microsoft.UI.Xaml.CBS and MicrosoftWindows.Client.Core as relevant dependencies. Microsoft XAML-dependent apps advisory

Possible causes include:

• Incomplete or pending Windows update processing
• Missing or damaged AppX package registration
• XAML dependencies not registered for the current user
• Corrupted Windows component-store files
• A problem in the current Windows user profile
• Security software or system policies interfering with modern Windows applications
• An interrupted restart or servicing operation

An error naming Windows.UI.Xaml.dll identifies where the crash occurred, but it does not by itself prove that the DLL file is physically damaged.

Step 1: Restart Windows and check for pending updates

Begin with a complete restart rather than Shut down followed by power-on. Windows can finish pending component registration and update operations during a restart.

If Windows Update is accessible, install all available cumulative and servicing updates and restart again.

If Settings cannot remain open, Windows may still download and install updates automatically. An administrator can also identify the current Windows version by pressing Windows + R and running:

winver

Only download a standalone update from the Microsoft Update Catalog when the correct Windows version, architecture and KB number have been confirmed.

Real-world result

In the incident used for this article, Settings initially continued crashing after policy changes, package re-registration and other repair attempts. A subsequent Windows update took approximately 30 minutes to install. After the update and restart, Settings and related pages worked normally in the original account.

This makes the update the confirmed observed resolution. However, it would be inaccurate to claim that a particular DLL, package or policy was definitively responsible without a crash dump or additional Microsoft diagnostic data.

Step 2: Confirm that Settings is crashing

Press Windows + R and run:

ms-settings:

If the gear appears and the window closes again, check Event Viewer.

1. Press Windows + R.
2. Enter:

eventvwr.msc

3. Open Windows Logs → Application.
4. Look for a recent Application Error with Event ID 1000.
5. Check the faulting application, module and exception code.

A relevant error may resemble:

Faulting application name: SystemSettings.exe
Faulting module name: Windows.UI.Xaml.dll
Exception code: 0xc000027b

Exception 0xc000027b is associated with a failure inside a Windows Runtime or XAML application. The complete event details are more useful than the exception code alone.

Administrators can also retrieve recent errors using PowerShell:

Get-WinEvent -FilterHashtable @{
    LogName='Application'
    Level=2
    StartTime=(Get-Date).AddMinutes(-10)
} |
Where-Object {
    $_.Message -match 'SystemSettings|immersivecontrolpanel'
} |
Select-Object TimeCreated, ProviderName, Id, Message |
Format-List

Step 3: Reset the Settings package

If Settings is crashing, open an elevated PowerShell window through Task Manager:

1. Press Ctrl + Shift + Esc.
2. Select Run new task.
3. Enter powershell.
4. Select Create this task with administrative privileges.
5. Select OK.

Stop any existing Settings process:

Stop-Process -Name SystemSettings -Force -ErrorAction SilentlyContinue

Reset the Settings package for the current account:

Get-AppxPackage windows.immersivecontrolpanel | Reset-AppxPackage

Re-register its manifest:

Add-AppxPackage -DisableDevelopmentMode -Register "$env:windir\ImmersiveControlPanel\AppXManifest.xml"

No PowerShell output normally means that the command completed successfully. Restart the computer and test Settings again.

Step 4: Check the State Repository Service

The State Repository Service supports application state and modern Windows components.

Check it with:

Get-Service StateRepository

If the status is Running, no action is required.

If it is stopped, try:

Start-Service StateRepository

Do not randomly change the startup types of protected Windows services. Some services use trigger-based startup and are not expected to remain running continuously.

Step 5: Register the XAML dependency packages

If Event Viewer identifies Windows.UI.Xaml.dll, register the dependency packages documented by Microsoft.

Run these commands separately in PowerShell:

Add-AppxPackage -Register -Path "C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode

Add-AppxPackage -Register -Path "C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe\AppxManifest.xml" -DisableDevelopmentMode

Add-AppxPackage -Register -Path "C:\Windows\SystemApps\MicrosoftWindows.Client.Core_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode

Restart Windows after registering these packages. The restart allows the Windows shell and related processes to reload the registered dependencies.

These commands are based on Microsoft’s documented workaround for XAML-dependent applications. The published issue mainly concerned certain enterprise, managed and virtualized environments, so similar crash details on another computer do not conclusively prove the same cause.

Step 6: Repair Windows components with DISM and SFC

If package registration does not solve the problem, repair the Windows component store.

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Allow the operation to finish. It may appear stuck at one percentage for an extended period. Do not close PowerShell, restart the computer, or press Ctrl + C.

After DISM finishes successfully, run:

sfc /scannow

Microsoft recommends running DISM before System File Checker because DISM repairs the component source that SFC may need. Microsoft DISM and SFC instructions

Restart Windows after both operations.

What does DISM error 1223 mean?

DISM may display:

Error: 1223
Operation was incomplete because of a cancel request.

Error 1223 means the servicing operation was cancelled before completion. It does not mean that DISM successfully checked or repaired Windows.

Restart the computer and run RestoreHealth again. Leave the elevated window open until DISM reports its final result.

If error 1223 repeatedly appears without any intentional cancellation, examine:

C:\Windows\Logs\DISM\dism.log

Also check for a pending restart, servicing failure, security software interference or an interrupted Windows Update operation.

Step 7: Test another Windows user account

A temporary account is a useful diagnostic test when Settings works inconsistently.

From elevated PowerShell, create a temporary standard account:

net user SettingsTest * /add

Enter a temporary password when prompted. Sign out from the affected account, sign in as SettingsTest, and try opening Settings.

How to interpret the result

• Settings works in the temporary account: The Windows installation and core Settings application can launch, but the original account may have damaged per-user package registration or profile data.
• Settings fails in both accounts: The problem is more likely system-wide, update-related or connected to shared Windows components.

A successful temporary-account test is evidence of a profile-specific symptom, but it does not identify the exact damaged file or registry entry. Windows Update can still repair shared packages or registrations that affect accounts differently.

Do not delete the original account while troubleshooting.

Should all Windows apps be re-registered?

Many online guides recommend this broad command:

Get-AppxPackage -AllUsers | ForEach-Object {
    Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"
}

This command attempts to register every AppX package and can produce many red error messages. It is generally better to repair the Settings and XAML packages first.

Common errors during broad registration include:

• 0x80073D02: Package resources are currently in use.
• 0x80073D06: A newer version of the package is already installed.
• 0x80070005: Access was denied.
• Package manifest or dependency errors.

Some of these messages may concern unrelated applications and do not necessarily mean the Settings repair failed.

What not to do

Avoid the following actions:

• Do not download Windows.UI.Xaml.dll from a DLL-download website.
• Do not manually replace protected Windows files unless their exact source and version are verified.
• Do not take ownership of the complete C:\Windows directory.
• Do not delete the entire AppX package database.
• Do not disable AppX, State Repository or Windows Update services as a permanent workaround.
• Do not immediately reset Windows when targeted repairs and updates have not been completed.
• Do not assume that differently numbered Windows components automatically prove file-version corruption.

Recommended troubleshooting order

Use this order to minimize unnecessary changes:

1. Restart Windows.
2. Install pending Windows updates.
3. Confirm the crash using Event Viewer.
4. Reset and re-register windows.immersivecontrolpanel.
5. Verify the State Repository Service.
6. Register the three documented XAML dependency packages.
7. Run DISM and allow it to finish.
8. Run SFC.
9. Test Settings from a temporary user account.
10. Review Windows Update, AppX and Application event logs if the problem remains.

References

• Microsoft: XAML-dependent Windows applications might not start or may close unexpectedly
• Microsoft: Use DISM and System File Checker to repair Windows
• Microsoft: Troubleshoot problems updating Windows
• Microsoft Update Catalog

Frequently Asked Questions

1. Why does Windows 11 Settings show the gear and then close?

The application may be failing while loading its AppX registration, XAML interface components or per-user state. Event Viewer can identify the faulting executable and module.

2. What is SystemSettings.exe?

SystemSettings.exe is the legitimate Windows executable used by the Windows Settings application. Its standard location is C:\Windows\ImmersiveControlPanel.

3. Is Windows.UI.Xaml.dll a virus?

The file in C:\Windows\System32 is a legitimate Microsoft Windows interface component. Do not replace it with a DLL downloaded from an unofficial website.

4. What does exception code 0xc000027b mean?

It indicates that a Windows Runtime or XAML application encountered a fatal internal exception. The code alone does not identify the root cause; the faulting module and related event logs must also be reviewed.

5. Will resetting the Settings package delete personal files?

No. Resetting windows.immersivecontrolpanel does not delete documents, photographs or installed desktop programs. It resets the Settings app’s per-user data and registration.

6. Why did re-registering Settings not fix the problem?

Settings may be correctly registered while one of its underlying XAML dependencies remains unavailable or incorrectly registered. That is why the targeted dependency commands may also be required.

7. Why must the computer be restarted after package registration?

The Windows shell and related processes may continue using their previously loaded package state. Restarting allows those components to load the repaired registrations.

8. Should DISM or SFC be run first?

Run DISM first and SFC second. This is the order recommended by Microsoft.

9. Does DISM error 1223 mean Windows is corrupted?

Not necessarily. Error 1223 means the operation was cancelled before it finished. The scan must be run again and allowed to complete.

10. Why does Settings work in another account?

That result suggests that the problem may involve per-user package registration, permissions or profile state. It does not necessarily mean that the entire Windows installation is damaged.

11. Can Windows Update repair the Settings app?

Yes. A cumulative update can replace Windows components, complete servicing operations and refresh package registrations. In the case described here, Settings worked again after a Windows update completed.

12. Does that prove the previous update caused the crash?

No. The timing strongly suggests that update processing was involved, but the final update resolving the issue does not prove one exact root cause.

13. What does AppX error 0x80073D02 mean?

It usually means a package cannot be modified because files or resources belonging to it are currently in use. Close the affected applications or restart Windows before trying again.

14. What does AppX error 0x80073D06 mean?

It generally means Windows already has a newer version of the package. The error may relate to an unrelated package during broad re-registration.

15. Can Control Panel be used while Settings is broken?

Traditional Control Panel tools may still work, but many Windows 11 options redirect to Settings. Run specific tools such as appwiz.cpl, services.msc, eventvwr.msc or sysdm.cpl when required.

16. Is a Windows reset normally required for this problem?

No. Restarting, completing Windows updates, repairing package registration, registering XAML dependencies, and running DISM and SFC should be attempted first.

Final Recommendation

When Windows 11 Settings opens briefly and closes, diagnose the failure before making broad system changes. An Event Viewer entry naming SystemSettings.exe, Windows.UI.Xaml.dll and exception 0xc000027b points toward a XAML startup failure, but it does not by itself establish why the failure occurred.

Use targeted package registration, complete DISM and SFC without interruption, test a temporary account, and install pending Windows updates. In the documented real-world case, the original account recovered after a Windows update completed and the computer restarted. Because the precise internal cause was not conclusively established, the update should be reported as the observed resolution rather than a guaranteed universal fix.

 

#Windows11 #WindowsSettings #SettingsApp #SystemSettings #SystemSettingsExe #WindowsUIXaml #XAML #WindowsRepair #WindowsTroubleshooting #SettingsNotOpening #SettingsAppCrash #BlankSettingsScreen #WindowsUpdate #DISM #SFC #SystemFileChecker #RestoreHealth #AppX #AppXPackage #ResetAppxPackage #ImmersiveControlPanel #EventViewer #Error1000 #Error0xc000027b #DISMError1223 #StateRepository #MicrosoftWindowsClientCBS #MicrosoftUIXamlCBS #WindowsClientCore #Windows11Fix #Windows11Support #WindowsAdministrator #PowerShell #PowerShellCommands #WindowsProfile #UserProfileRepair #MicrosoftUpdate #WindowsComponents #Windows25H2 #TechnicalSupport