File system errors on Windows 10 and Windows 11 can look cryptic — a terse message, an error code, or “The parameter is incorrect” when you plug in a USB stick — but they usually point to fixable problems with system files, disk metadata, or the drive itself. This guide consolidates proven, non‑destructive troubleshooting steps (from quick restarts to offline repairs), explains what the common numeric error codes mean, and offers a prioritized workflow so you stop at the least‑disruptive fix that solves the issue.
File system errors are symptoms, not a single disease. They occur when Windows can’t correctly read, write, or validate the structures that keep files organized on an NTFS, exFAT, FAT32 or ReFS volume. Typical triggers include sudden power loss, failed updates, software conflicts, malware, and physical disk damage such as bad sectors. Short-lived glitches will sometimes be cured by a reboot, while persistent errors require targeted repairs.
Microsoft and independent Windows troubleshooting guides recommend an escalation path that starts with the least intrusive actions (restart, app reinstall) and moves to disk checks, image repair tools (DISM + SFC), and — only as a last resort — Reset this PC or a clean reinstall. For Store‑app cache and app‑specific errors, the wsreset utility and app reinstall often work without touching the OS image. (windowscentral.com, learn.microsoft.com)
Caution: If SFC/DISM report that files are unrepairable, and CHKDSK also finds many bad clusters, prioritize data backup and consider hardware checks next.
Source: nerdbot Troubleshooting File System Errors on Windows 10/11 Drives
Background / Overview
File system errors are symptoms, not a single disease. They occur when Windows can’t correctly read, write, or validate the structures that keep files organized on an NTFS, exFAT, FAT32 or ReFS volume. Typical triggers include sudden power loss, failed updates, software conflicts, malware, and physical disk damage such as bad sectors. Short-lived glitches will sometimes be cured by a reboot, while persistent errors require targeted repairs.Microsoft and independent Windows troubleshooting guides recommend an escalation path that starts with the least intrusive actions (restart, app reinstall) and moves to disk checks, image repair tools (DISM + SFC), and — only as a last resort — Reset this PC or a clean reinstall. For Store‑app cache and app‑specific errors, the wsreset utility and app reinstall often work without touching the OS image. (windowscentral.com, learn.microsoft.com)
Why file system errors happen
- Corrupted system files. Protected Windows files can be damaged during interrupted updates or unsafe shutdowns, 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 can produce read/write failures or error codes (for example, 0xC000009C often suggests bad sectors).
- Faulty updates or driver issues. An incomplete or buggy update can leave the system image inconsistent and break inbox apps. Rolling back an update or updating drivers may restore stability.
- Permissions and ACL problems. Access denied or security descriptor errors can surface as file system errors when processes lack rights to required files.
- App-specific corruption (Store apps). Microsoft Store apps use an app package pipeline; a corrupted Store cache or malformed app package often causes codes like -2147219196 for Photos or Calculator. Resetting the Store cache is a low‑risk first step. (learn.microsoft.com, answers.microsoft.com)
- External drives and formatting issues. “The parameter is incorrect” frequently appears when an external drive has filesystem corruption, an unexpected decimal / regional formatting quirk, or a partition table mismatch between MBR and GPT. Many recovery articles list CHKDSK, driver updates, or reformatting (after recovery) as effective remedies. (easeus.com, itechguides.com)
- -2147219196 (0x80040C04) — often tied to invalid app metadata or Store pipeline problems.
- 1073741819 (0xC0000022) — typically a permissions/access error.
- 0xC000009C — associated with bad sectors or physical disk failure.
Troubleshooting workflow — from least disruptive to most
The following methods are ordered so you can stop as soon as the error clears. Each method includes clear steps, what it fixes, and when to avoid it.Method 1 — Restart the PC (fast, safe first step)
A restart clears in‑memory states, pending updates, hung services and transient file locks. Reboot first whenever an app or the Store reports a file system error. This step does not change files or settings. If the error returns immediately after a reboot, proceed to the next methods.Method 2 — Undo a problematic Windows update
If the failure began immediately after installing a Windows update, uninstall the update while Windows still boots normally. This is safer than a full reset and preserves user files.- Open Settings → Update & Security → Windows Update → View update history.
- Click Uninstall updates, select the recently installed update (sort by Installed on), and choose Uninstall.
- Pause updates temporarily to avoid immediate reinstallation while you monitor stability.
Method 3 — Repair the Windows image and protected files (DISM + SFC)
When core Windows components are inconsistent or missing, use DISM to repair the image and SFC to fix protected files. These are the recommended system‑level repair tools.- Open an elevated command prompt or Terminal (Admin).
- Run: DISM /Online /Cleanup-Image /ScanHealth (checks for corruption).
- Then run: DISM /Online /Cleanup-Image /RestoreHealth (repairs the image; may download replacement files).
- After DISM finishes, run: sfc /scannow (checks and repairs protected system files).
- Reboot and retest the failing app.
Caution: If SFC/DISM report that files are unrepairable, and CHKDSK also finds many bad clusters, prioritize data backup and consider hardware checks next.
Method 4 — Check disk health with CHKDSK (use with care)
CHKDSK scans for filesystem errors and bad sectors and attempts to repair them. Use it when CHKDSK‑reported ranges or I/O errors appear, or multiple apps fail unpredictably.- Open Command Prompt as Administrator.
- Run: chkdsk C: /f /r (replace C: with the affected drive letter).
- If prompted to schedule on reboot, type Y and restart.
Method 5 — Reset the Microsoft Store cache (wsreset)
When the error is specific to Microsoft Store apps (Photos, Calculator, etc.), reset the Store cache before reinstalling apps.- Press Windows + R, type wsreset.exe, and press Enter.
- A blank command window appears; wait for it to close and for the Store to open.
Method 6 — Reinstall or cleanly remove a problematic app
If only a single application fails with a file system error code, reinstalling or removing lingering app data can work.- Settings → Apps → Installed apps. Select the app and choose Uninstall.
- Restart, then reinstall the latest package from the Microsoft Store or the vendor’s installer.
- For stubborn UWP/Store apps, use PowerShell to remove and then re‑register the app package.
Method 7 — Reset this PC (Windows reinstall without full hardware swap)
If corruption is widespread and persists after DISM, SFC, and drive checks, Reset this PC offers a controlled reinstall. Choose Keep my files first; if that fails, use Remove everything.- Settings → System → Recovery → Reset this PC → Choose Keep my files or Remove everything → Cloud download or Local reinstall.
- After reset, reinstall apps and drivers and apply updates.
Advanced diagnostics and data‑safety steps
Prioritize data recovery before destructive repairs
If files have already gone missing, recover critical data before running CHKDSK /r or reformatting — some repair tools may overwrite sectors and reduce recoverability. Use imaging tools or professional recovery software if necessary. Community and recovery guides stress backing up accessible files first and then performing repairs. (easeus.com)Use SMART and manufacturer tools to verify hardware health
- Run SMART checks with CrystalDiskInfo or smartctl to detect early SSD/HDD failures.
- Use vendor tools (Samsung Magician, Western Digital Data Lifeguard, Crucial Storage Executive) for firmware updates and extended diagnostics. Community troubleshooting threads frequently recommend these tools for decisive hardware tests.
Test memory when behavior is unpredictable
Bad RAM manifests as occasional corruption and BSODs; run Windows Memory Diagnostic (mdsched.exe) or MemTest86 to rule out DRAM faults. Replacing suspect modules can resolve persistent, otherwise inexplicable system corruption.Practical examples: when to choose which method
- If the Photos or Calculator app fails with -2147219196: run wsreset first, then DISM + SFC if the problem persists, and finally reinstall the app package. (learn.microsoft.com)
- If an external USB drive shows “The parameter is incorrect”: try a quick reboot, scan for malware, run chkdsk on the external drive, check decimal symbol/region settings, and if needed, recover data followed by a full format. (easeus.com, itechguides.com)
- If Windows update coincides with failures across several inbox apps: uninstall the problematic update, run DISM /RestoreHealth and sfc /scannow, then run CHKDSK if the image tools report disk issues. (windowscentral.com)
Risks, caveats, and red flags
- Running CHKDSK /r on a physically failing drive can cause the drive to fail completely; image and back up first. (lifewire.com)
- DISM /RestoreHealth may download replacement files from Windows Update; in air‑gapped or offline environments, you must supply a clean source (install.wim or install.esd). (windowscentral.com)
- Reset this PC can remove installed applications and drivers; generate a list of installed apps and secure license keys before proceeding. Community walk‑throughs emphasize collecting installers and drivers ahead of a reset. (lifewire.com)
- If the same corruption returns immediately after reset, investigate hardware (storage controller, NVMe, SATA cables, motherboard) and firmware settings (Intel RST/RAID vs AHCI), since repeated corruption points to hardware-level instability.
Preventive practices and best hygiene
- Keep regular backups (cloud + external) and follow the 3‑2‑1 backup rule: at least three copies, on two different media, one offsite. Back up before attempting repairs that write to disk.
- Apply Windows updates during downtime and verify driver compatibility for storage controllers; prefer vendor‑supplied storage drivers for OEM systems using Intel RST or similar.
- Run weekly SMART checks and schedule monthly image‑level backups. If a drive shows increasing reallocated sectors or pending sectors, plan replacement.
- Use reputable antivirus and run occasional full scans to remove malware vectors that can alter system files.
Quick checklist: a technician’s condensed workflow
- Restart the PC.
- If recent update: uninstall the update and pause updates.
- Reset Store cache (wsreset) for Store‑app errors.
- Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
- Run chkdsk X: /f /r only after imaging or when hardware checks are clean.
- Reinstall or re‑register the failing app.
- Reset this PC (Keep my files) → Remove everything if necessary.
- If errors persist post‑reset, run SMART, vendor diagnostics, and memory tests to find failing hardware. (windowscentral.com, lifewire.com, learn.microsoft.com)
Conclusion
File system errors on Windows 10 and Windows 11 are usually solvable without replacing hardware or reinstalling everything. The right approach is methodical: try the least intrusive fixes first, validate system integrity with DISM and SFC, and only use CHKDSK or a reset after you’ve secured your data. When corruption returns after deep software repair, switch focus to hardware diagnostics. Maintaining good backups, monitoring drive health, and keeping firmware/drivers updated will minimize surprises and keep the system recoverable when problems arise.Source: nerdbot Troubleshooting File System Errors on Windows 10/11 Drives
