Hi Dolly — sorry you hit this after an update. That File system error (-2144927436) and the Start/Settings / Windows-key failures strongly point to servicing/component-store or Settings-package corruption — the usual repair order is DISM → SFC → re-register Settings, then try rollback/uninstall if repair doesn’t help. Below are concise, ordered steps to try (with exact commands). Please tell me which Windows (10 or 11) you’re on, whether Task Manager opens (Ctrl+Shift+Esc), and whether you have a System Restore point or backup before we proceed.
Important: back up your important files before uninstalling updates or doing a repair install.
1) Restart Explorer & open an elevated shell (quick test)
- Press Ctrl+Shift+Esc to open Task Manager.
- In Task Manager: File → Run new task → type cmd.exe (check “Create this task with administrative privileges”).
- In Task Manager you can also right‑click Windows Explorer → Restart.
(If taskbar becomes clickable again, test Settings / Windows key. Restarting Explorer often restores UI responsiveness temporarily.
2) Run DISM checks then SFC (do these first)
Open the elevated Command Prompt you created and run these, in order:
- DISM /Online /Cleanup-Image /CheckHealth
- DISM /Online /Cleanup-Image /ScanHealth
- DISM /Online /Cleanup-Image /RestoreHealth — this can take 10–30+ minutes.
- After DISM completes, run: sfc /scannow
If SFC still reports unfixable files, capture the SFC/CBS lines to a text file and attach it here:
- findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > C:\sfclogs.txt
Then paste or attach C:\sfclogs.txt. The DISM→SFC workflow and why it’s used are standard first‑line fixes.
3) Re-register Settings (if SFC/DISM helped but UI still broken)
Open PowerShell as Administrator and run:
- Get-AppxPackage windows.immersivecontrolpanel | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
If you want a broader re-register (may print benign errors):
- Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
4) If repair fails — identify & uninstall the offending update
A. List recent installed updates:
- wmic qfe list brief /format:table (shows KB numbers)
or to see package names:
- dism /online /get-packages
B. Try uninstalling a specific KB (replace ####### with the KB number):
- wusa /uninstall /kb:######
C. If the Settings app is unusable, use WinRE: Shift+Restart (from sign-in screen or hold Shift while choosing Restart) → Troubleshoot → Advanced options → Uninstall Updates → choose “Uninstall latest quality update” or “Uninstall latest feature update.” This WinRE uninstall flow is the fallback when UI is broken.
Note: not every KB is uninstallable; uninstalling security updates reduces protection, so treat as temporary mitigation.
5) Reset Windows Update components (if updates are stuck/corrupt)
From an elevated CMD run:
- net stop wuauserv
- net stop cryptSvc
- net stop bits
- net stop msiserver
- ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
- ren C:\Windows\System32\catroot2 catroot2.old
- net start wuauserv
- net start cryptSvc
- net start bits
- net start msiserver
This forces re-download of update metadata/packages and often helps when the component store is inconsistent.
6) If everything above fails — System Restore / In-place repair / Recovery USB
- Try System Restore from WinRE if you have a restore point (Troubleshoot → Advanced options → System Restore).
- If you don’t have a restore point or restore fails, do an in‑place repair (repair install) using Media Creation Tool / ISO: run setup.exe from mounted ISO and choose “Keep personal files and apps.” This often fixes deep servicing corruption while preserving apps/data.
- If you need offline repair tools or can’t boot, create a recovery USB on another PC and boot it to access WinRE/repair options.
7) Disk check & drivers
- Schedule chkdsk to rule out disk errors: chkdsk C: /f /r (reboot required).
- After repairs, check Device Manager for driver issues; roll back or update GPU / storage drivers if they look suspicious. Driver conflicts sometimes surface after updates.
What I need from you next
- Which Windows (10 or 11) and exact build (run winver and paste the result)?
- Can you open Task Manager (Ctrl+Shift+Esc) now?
- Run the DISM + SFC commands above and paste the final lines/summary of each (or attach C:\sfclogs.txt). If you hit errors while running any command, paste the error text exactly.
If you prefer, I can walk you step‑by‑step via the Task Manager method to open an elevated prompt and run the DISM commands. If SFC/DISM don’t fix it, I’ll give exact commands to find and uninstall the last installed update (or guide you through using WinRE to uninstall it and play
geometry dash 3d).
If you attach the sfclogs or paste the DISM output here I’ll review the important lines and give the next precise action.