A file system error on Windows 10 or 11 rarely signals a catastrophic failure—most stem from corrupted system files, wonky updates, or minor drive glitches. What trips users up is not the severity but the cryptic codes: “The parameter is incorrect,” -2147219196, 0xC000009C. The fix, in almost every case, follows a predictable, low-risk sequence that saves your data and your sanity.

File system errors are symptoms, not a singular disease. They occur when Windows cannot correctly read, write, or validate the structures that keep files organized on NTFS, exFAT, FAT32, or ReFS volumes. Typical triggers include sudden power loss, interrupted updates, software conflicts, malware, and physical disk damage like bad sectors. A reboot sometimes cures a fleeting glitch, but persistent errors demand targeted repairs. Microsoft and veteran troubleshooters recommend an escalation path that starts with the least intrusive actions and moves to disk checks, image repairs, and—only as a last resort—a full reset or clean install.

Why file system errors happen

  • Corrupted system files. Protected Windows files can be damaged during unsafe shutdowns or failed updates, leading to application crashes or missing components.
  • Drive corruption and bad sectors. Physical or logical damage to sectors or NTFS metadata breaks file allocation tables and produces read/write failures. Error 0xC000009C often points to bad sectors.
  • Faulty updates or driver issues. A buggy cumulative update can leave the system image inconsistent and break inbox apps. Rolling back the update or refreshing drivers often restores stability.
  • Permissions and ACL problems. Access denied errors can surface as file system errors when processes lack rights to required files. Code 0xC0000022 (1073741819) frequently indicates a permissions issue.
  • App-specific corruption. Store apps like Photos or Calculator may fail with code -2147219196 (0x80040C04) due to a corrupted Store cache or malformed app package. Resetting the Store cache is a low-risk first step.
  • External drives and formatting quirks. “The parameter is incorrect” frequently appears on corrupted external drives, mismatched partition tables (MBR vs. GPT), or even conflicting regional settings.

The troubleshooting escalation: from mild to mighty

Stop as soon as the error clears. Each method preserves your files unless otherwise noted.

1. Restart the PC

A restart clears in-memory states, hung services, and transient file locks. Reboot before doing anything else. If the error returns immediately, move on.

2. Undo a problematic Windows update

If the failure began right after an update, uninstall it while the system is still bootable.
1. Go to Settings → Update & Security → Windows Update → View update history.
2. Click Uninstall updates, sort by “Installed on,” and remove the suspect update.
3. Pause updates temporarily to prevent automatic reinstallation.
Rollbacks are reversible and keep your files intact.

3. Repair the Windows image with DISM, then system files with SFC

When core components are inconsistent, use Deployment Image Servicing and Management (DISM) to heal the component store, then run System File Checker (SFC) to repair protected files.

DISM: fixing the repair source

DISM has three health-check options:
- CheckHealth: Quickly detects corruption inside the local image (no repair).
- ScanHealth: Performs an advanced scan for issues (can take several minutes).
- RestoreHealth: Scans and automatically fixes the image by fetching clean files from Windows Update or a specified source.

Open an elevated Command Prompt or Terminal (Admin) and run:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

After RestoreHealth completes, run SFC /scannow. SFC scans and replaces missing or corrupted system files using the now-healthy image.

What if DISM fails? If the tool cannot download replacement files—common on air-gapped machines or when Windows Update is borked—you can point it to a clean install.wim or install.esd from a Windows ISO. Mount the ISO, note the drive letter (e.g., E:), and run:

DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\Sources\install.wim /LimitAccess

The ISO must match your exact Windows edition, build, and language. After repair, re-run SFC multiple times to catch stubborn errors.

4. Check disk health with CHKDSK (use with extreme caution)

CHKDSK scans for filesystem errors and bad sectors and attempts repair. Run it only after backing up critical data.

chkdsk C: /f /r

The /f flag fixes structural issues; /r locates bad sectors and recovers readable data. Never run /r on a drive that is clicking, grinding, or repeatedly disconnecting—the intense I/O stress can push a dying drive over the edge. If CHKDSK reports numerous bad clusters, treat the drive as compromised and prioritize data recovery.

5. Reset the Microsoft Store cache (wsreset)

For errors confined to Store apps, reset the cache before reinstalling anything. Press Win + R, type wsreset.exe, and wait for the blank window to close and Store to reopen. This wipes the cache without removing installed apps or accounts. If wsreset itself crashes, follow with DISM+SFC, then consider re-registering Store packages via PowerShell.

6. Reinstall or cleanly remove the problematic app

If a single application fails, uninstall it via Settings → Apps → Installed apps, restart, and install the latest version. For stubborn UWP apps, use PowerShell to remove and re-register the package. Always confirm you have license keys before uninstalling paid software.

7. Reset this PC

When corruption is widespread and survives DISM/SFC and disk checks, use “Reset this PC.” Choose Keep my files first; if that fails, use Remove everything. Cloud download fetches a fresh copy of Windows; local reinstall uses the existing recovery partition. Afterward, reinstall apps and drivers. If corruption returns immediately, hardware is the likely villain.

8. Hardware diagnostics

  • Drive health: Run SMART checks with CrystalDiskInfo or vendor tools (Samsung Magician, WD Data Lifeguard). Look for reallocated sectors or pending sectors.
  • Memory: Run Windows Memory Diagnostic (mdsched.exe) or MemTest86. Bad RAM causes unpredictable file corruption and bluescreens.

Real-world patterns: which fix for which symptom?

  • Photos or Calculator fails with -2147219196: run wsreset → DISM+SFC → reinstall the app.
  • External USB drive shows “The parameter is incorrect”: reboot, scan for malware, run chkdsk X: /f on the external drive, check decimal/regional settings, then recover data and reformat if needed.
  • Several inbox apps break after a Patch Tuesday update: uninstall the update, run DISM /RestoreHealth and sfc /scannow, then CHKDSK if the image tools report disk issues.

Data safety first: backup and recovery rules

  • Before any disk repair, create a full image or copy irreplaceable files to another drive.
  • Follow the 3-2-1 rule: three copies, two different media, one offsite.
  • If files are already missing, run data recovery software before CHKDSK /r or reformatting—recovery chances drop once sectors are overwritten.

Preventive hygiene

  • Apply updates during planned downtime and verify storage controller drivers. OEMs using Intel RST should install vendor-specific drivers.
  • Schedule monthly SMART checks and full image backups. If a drive shows increasing reallocated sectors, replace it immediately.
  • Use reputable antivirus; malware can alter system files and trigger cascading file system errors.

Quick-reference technician’s checklist

  1. Restart the PC.
  2. If recently updated: uninstall the update and pause updates.
  3. For Store-app errors: run wsreset.
  4. Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
  5. chkdsk X: /f /r only after imaging or when hardware checks are clean.
  6. Reinstall or re-register the failing app.
  7. Reset this PC (Keep my files) → Remove everything if needed.
  8. If errors persist post-reset, run SMART, vendor diagnostics, and memory tests.

File system errors are solvable. Methodically moving from gentle fixes to deeper repairs preserves your data and often avoids a time-consuming reinstall. When the same corruption reappears after a reset, switch focus to hardware—memory, drive, or storage controller—and let the diagnostics guide the way.