How to Fix ‘System Settings Broker Has Stopped Working’ in Windows 11

Opening the Windows 11 Settings application (Win + I), managing network adapters, or adjusting display settings suddenly causes the window to close abruptly with an Application Error alert in Reliability Monitor: ‘System Settings Broker has stopped working (Faulting application name: SystemSettingsBroker.exe, Exception code: 0xc0000005)’. In Windows 11’s modular architecture, SystemSettingsBroker.exe acts as the critical privilege mediator and runtime bridge between user-facing Universal Windows Platform (UWP) interfaces and deep Win32 operating system APIs. When this process crashes, modern system administration interfaces become inaccessible.

Why Does SystemSettingsBroker.exe Crash?

The crash is triggered by broken UWP manifest dependencies or permissions corruption:

  • Corrupted Windows Settings UWP App Package: Damaged manifest files or outdated local state inside Microsoft.Windows.ShellExperienceHost.
  • Memory Access Violation (0xc0000005): Corrupted registry keys under HKEY_CURRENT_USER\Software\Classes\Local Settings preventing the broker from allocating required security descriptors.
  • Corrupted Windows Subsystem DLLs: Damaged core dynamic libraries (such as twinapi.appcore.dll) resulting from incomplete Windows updates.
  • Third-Party Shell Customisation Utilities: UI enhancement utilities (such as ExplorerPatcher, StartAllBack, or TranslucentTB) hooking into legacy system broker calls.

Step 1: Re-Register Windows 11 Settings Application via PowerShell

Reinstall and re-register the native modern Settings package without losing user preferences.

  1. Press Win + S, type powershell, right-click Windows PowerShell, and select Run as administrator.
  2. Paste the following command to re-register the System Settings package and press Enter:
    Get-AppXPackage -AllUsers -Name windows.immersivecontrolpanel | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  3. Next, re-register the Shell Experience Host package:
    Get-AppXPackage -AllUsers -Name Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  4. Wait for the blue progress operations to finish, restart your PC, and open Settings.

Step 2: Run DISM and System File Checker

Repair underlying corrupted Win32 runtime dynamic libraries.

  1. In your elevated PowerShell or Command Prompt window, execute:
    DISM /Online /Cleanup-Image /RestoreHealth
  2. Once DISM verification completes, execute:
    sfc /scannow
  3. If corrupted components were repaired, reboot your PC to apply the clean system binaries.

Step 3: Reset Settings App via Windows Apps Settings

Purge local AppData configuration caches for the Settings app.

  1. Open the Start Menu, search for Settings, right-click the Settings icon, and choose App settings.
  2. Scroll down to the Reset section.
  3. Click Repair to verify package integrity.
  4. If the broker crash persists, click Reset to purge corrupted local application state.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.