Introduction: When Win11 Settings Crashes Meet SFC Errors
Recently, I was troubleshooting a Windows 11 machine suffering from a classic case of system component corruption. It started with a simple, frustrating issue: the Windows 11 Settings app (ImmersiveControlPanel) wouldn’t open and would simply crash immediately upon clicking.
Following standard procedure, I ran the classic system file repair command sfc /scannow in an elevated PowerShell. The progress bar hung at exactly 16% and failed with the following error:
“Windows Resource Protection could not perform the requested operation.”
Assuming the local component store was corrupted, I proceeded to use DISM /Online /Cleanup-Image /RestoreHealth to repair the image via Windows Update. The process reached 54.5% (or similar arbitrary progress) and aborted with a fatal error:
“Error: 1392. The file or directory is corrupted and unreadable.”
If you’re facing these exact symptoms, don’t panic. This guide will help you untangle these underlying filesystem issues and provide a logical, battle-tested recovery workflow.
Why do DISM 1392 and SFC Hangs Happen?
Many online tutorials will just tell you to spam SFC and DISM commands, but that is futile when you hit Error Code 1392.
Error 1392 essentially means: The NTFS filesystem has structural corruption, or the drive has logical/physical bad sectors. When system repair tools (DISM or SFC) attempt to read a component file located on one of these damaged sectors, the underlying filesystem denies access, causing the process to abort.
The correct approach is: First, fix the underlying disk logic errors -> Then, repair the system image -> Finally, reset the problematic UWP app.
The Complete Workflow to Fix Win11 Core Files and Settings Crashes
Right-click your Start button and select “Terminal (Admin)” or “Windows PowerShell (Admin)”, and execute the following four steps in order.
Step 1: Run CHKDSK for Deep Disk and Filesystem Repair (Critical)
Since the base files are unreadable, we need Windows to take exclusive control of the disk before booting to perform a thorough scan.
Enter the following command in the terminal and press Enter:
PowerShell
chkdsk c: /f /rThe system will prompt you that the volume is in use and ask if you want to perform the check on the next restart. Type Y and press Enter.
Restart your PC. It will boot into a black screen with text during the scanning process. This step can take a while (from tens of minutes to hours, depending on your drive’s speed and the extent of the damage). Be patient and let it finish booting into the desktop; do not force a shutdown.
Step 2: Use DISM to Repair the Windows System Image
Once the disk repair finishes and you are back in Windows, the underlying 1392 read errors should be cleared. Now, we pull healthy system files from Microsoft’s servers.
Open PowerShell as Administrator again and run:
PowerShell
DISM /Online /Cleanup-Image /RestoreHealthNote: The progress bar may stall for a long time at certain points (like 20% or 62.3%). It might look like it’s frozen, but the background process (TiWorker.exe) is actively comparing and downloading files. As long as there are no error messages, just let it run until it says “The operation completed successfully.”
Step 3: Rerun SFC to Validate and Repair Local Files
With the DISM repair successful, the local repository is stable, and we can finally call upon SFC again.
Run the scan:
PowerShell
sfc /scannowThe progress bar should now successfully bypass the previous 16% mark and hit 100%. If it states, “Windows Resource Protection found corrupt files and successfully repaired them,” your base system is back to full health.
Step 4: Force Reset the Win11 Settings App
After the system repairs, the Settings app might still be in an inconsistent state. We need one final command to re-register the component:
Run this in PowerShell:
PowerShell
Get-AppxPackage *windows.immersivecontrolpanel* | Reset-AppxPackageAfter that, restart your computer once more. Your frustrating Settings crash should now be a thing of the past!
Frequently Asked Questions (FAQ)
Q1: The DISM command has been stuck at 62.3% for an hour. Is it frozen? Can I stop it?
A: Absolutely do not stop it! This is normal behavior. DISM is communicating with Microsoft servers to download and repackage corrupted files. Open “Task Manager” and check if the
Windows Modules Installer Workerprocess shows network or CPU activity. As long as it hasn’t crashed with a red error, have patience.
Q2: Will running chkdsk c: /f /r delete my personal files and photos?
A: No. CHKDSK is a standard Windows tool used to repair structural directory errors and identify bad sectors, attempting to recover data to healthy sectors. It is designed to preserve, not delete, your data. That said, keeping regular backups of important files is always a best practice.
Q3: What if I run all these commands and Settings still won’t open?
A: If the system corruption is too severe, the fastest and most effective solution is an In-place Upgrade. Download the Windows 11 ISO from the official Microsoft website, mount it, and run
setup.exe. Ensure you select the option to “Keep personal files and apps.” This will overwrite the OS core with fresh, healthy files while keeping all your software, configuration, and data 100% intact.