Quick fix: Re-register the Settings app with Get-AppxPackage *immersivecontrolpanel* | Reset-AppxPackage in elevated PowerShell, then sign out and back in. If that doesn’t help, run sfc /scannow — the Personalization page often crashes Settings when a corrupted system file makes the wallpaper render fail.

You open Settings, click Personalization, and the entire Settings window closes without an error. No dialog, no crash report, no entry in Event Viewer’s default view. Other Settings pages work fine; only Personalization (or sometimes Background, Colors, or Themes specifically) crashes the host. The behavior started after a Windows Update or after installing a third-party theme tool.

Symptom: Settings app closes silently when you open Personalization (or specific pages inside it).
Affects: Windows 11, any edition.
Fix time: 15 minutes.

What causes this

The Settings app is a UWP package called ImmersiveControlPanel. It loads each page on demand. Personalization specifically pulls in the current wallpaper, accent colors, and theme files. If any of those references a missing or corrupted file — a deleted wallpaper, a third-party .theme file with an invalid signature, a bad shell extension — the page handler throws an uncaught exception and the Settings host process exits.

The crash is silent because the Settings app uses ShellExperienceHost as its container, and when the inner page faults, the host closes without writing a user-visible error. Event Viewer logs it under Application Error if you know to look there.

Method 1: Re-register the Settings app

Open PowerShell as Administrator.
Run:

Get-AppxPackage *immersivecontrolpanel* | Reset-AppxPackage
Wait for the command to complete (~30 seconds).
Sign out of Windows and sign back in — this is required for the reset to take effect.
Open Settings and try Personalization again.

This wipes the Settings app’s per-user state and re-runs its first-launch setup. About 70% of silent-crash cases resolve at this step.

Method 2: Reset the current wallpaper and theme

If the crash is specifically on the Background or Themes page, the saved wallpaper file is the suspect.

Open File Explorer and navigate to %AppData%\Microsoft\Windows\Themes. (Paste this into the address bar.)
Move all files in that folder to your desktop as a backup.
Right-click the desktop, choose Personalize. If this opens the Settings page without crashing, choose any built-in wallpaper from the gallery.
If right-click Personalize also crashes, run reg delete “HKCU\Control Panel\Desktop” /v Wallpaper /f in an elevated terminal, then reboot.
Open Settings → Personalization. The page should load with the default wallpaper.

If Personalization works after wiping %AppData%\Microsoft\Windows\Themes, one of the files there was the trigger. You can re-add a saved wallpaper, but apply themes one at a time to find which one re-creates the crash.

Method 3: Repair system files with SFC and DISM

For crashes that survive the first two methods, the underlying issue is usually a corrupted system DLL that Personalization depends on.

Open elevated Command Prompt.
Run sfc /scannow. Wait for it to finish (~5 minutes).
If SFC reports it found and fixed corruption, reboot and test Settings.
If SFC reports it couldn’t fix some files, run dism /online /cleanup-image /restorehealth. This downloads fresh copies of corrupted files from Windows Update.
Reboot when DISM completes (10–20 minutes). Re-run sfc /scannow to confirm.

SFC + DISM is the canonical fix for “some Windows app crashes silently” problems. It’s slow but it’s the right tool when the cause is system-level rather than app-level.

How to verify the fix worked

Open Settings, click Personalization. The page loads with Background, Colors, Themes, Lock screen, Start, and Taskbar visible.
Click each subpage. None of them close Settings.
Right-click the desktop and choose Personalize. Settings opens to Personalization without issue.
Apply a different wallpaper, then apply a different theme. Each change applies without closing Settings.

If none of these work

If Settings still crashes after re-register, theme wipe, and SFC/DISM, the issue may be a third-party shell extension that hooks into Personalization. Run ShellExView (free, NirSoft) and disable any non-Microsoft extensions, then test. Common culprits are old wallpaper-changer utilities, RGB lighting software with Windows theme integration, and screensaver packages from outside Microsoft. If disabling all third-party extensions fixes it, re-enable them one at a time to find the bad one. As a final resort, an in-place repair upgrade (run setup.exe from a fresh Windows 11 install USB, choose Keep my files and apps) replaces all system files including the Settings app without losing data.

Bottom line: Silent Personalization crashes are almost always either app-state corruption (fixed by Reset-AppxPackage), a bad wallpaper/theme file (fixed by clearing %AppData% themes), or system file corruption (fixed by SFC/DISM). Work through the three in order — the right fix is usually one of them.