Troubleshooting File System Errors on Windows 10/11 Drives

Tried to open the app on Windows 10 or 11 and been greeted with a file system error and a confusing error code? That’s the problem many users run into when corrupted files or disk issues interrupt normal operations. Fortunately, these errors rarely require a full reinstall or new hardware. With the right built-in tools and a few easy steps, you can restore stability and recover access to your files. In this article, you’ll find step-by-step methods to fix file system errors on Windows 10 and 11.

Why Do File System Errors Happen

File system errors like the parameter is incorrect on Windows 10 and 11 usually point to problems with how the operating system reads, writes, or organizes data on a drive. They can occur suddenly after an update, gradually as a drive develops bad sectors, or when corrupted system files disrupt normal operations. In many cases, the error message is accompanied by a numerical code that hints at the root cause.

Common causes include:

• Corrupted system files. Windows files can become damaged during failed updates, improper shutdowns, or unexpected power loss, and prevent the OS from working correctly.
• Faulty Windows or software updates. Unstable or incomplete updates can disrupt essential processes, which can lead to compatibility issues and file system errors.
• Bad sectors on the drive. Physical imperfections on the storage medium can make certain parts of the disk unreadable and trigger read/write errors.
• Malware infections. Viruses can alter or delete system files, change key configurations, and even damage the file system structure.
• Hardware or connection issues. Loose cables, failing storage devices, or malfunctioning controllers can interrupt data access and cause the system to misread the drive.
• Application conflicts. Certain third-party programs, especially those interacting directly with files or system settings, may cause instability.

Most file system error messages display a numeric code. These codes often indicate the type of issue and can be matched to known causes. If the same code appears when opening a certain app (such as Photos or Microsoft Store), it usually signals a software-related or app-specific problem rather than a hardware fault. 

Some of the most frequently reported file system errors include:

• -2147219196 (0x80040C04). Often tied to corruption in system files or invalid file system metadata, typically affecting apps like Photos or Calculator.
• 1073741819 (0xC0000022). Usually linked to permission or access issues that prevent certain files or programs from running.
• 0xC000009C. Indicates bad sectors on the disk, often a result of physical damage or wear on the drive.
• The parameter is incorrect Windows 10/11.  A common error that appears when connecting external storage devices, often due to file system corruption, partition errors, or improper formatting.

Now that you know what the error codes represent, the next step is to apply the right fix.

How to Fix File System Errors in Windows 10 & 11

Windows includes several built-in tools to handle both corrupted system files and problems within the drive itself. The best approach is to begin with the simplest fixes and only then move on to advanced repairs. For clarity, each method in this guide is arranged step-by-step from least disruptive to most drastic, so you can stop as soon as the error clears. 

Keep in mind that if files have already disappeared, data recovery should come first. Some repair commands may overwrite data that could still be restored. In this section, we’ll cover the main solutions to the most common issues, but you may also want to look into Data Recovery Experts, who provide a deeper examination of data loss and recovery cases.

Method 1. Restart Your Computer

A restart is the simplest way to clear temporary glitches in Windows. File system errors sometimes appear because of a stalled process, glitch, an incomplete update, or a temporary cache problem. Restart reloads all system services and allows Windows to start fresh. It does not resolve deep issues such as corrupted system files, bad sectors, or hardware problems. No backup is needed for this step since a restart does not affect files or settings.

1. Click the Start button in the lower-left corner of your screen.
2. Select the Power icon from the menu.
3. Choose Restart from the list of options.

A restart is quick and safe, but it only fixes temporary faults. If the error comes back immediately, continue with more advanced methods below. Still, always try this first, it may save time when the problem is minor. 

Method 2. Uninstall Problematic Windows Updates

If the file system error appeared immediately after a Windows update, remove the offending update first. This method rolls back only the selected update and keeps your files. Use it when the PC boots normally, but a recent quality update seems to have broken core apps or Settings. Avoid this if the update is security‑important and no restore point or backup exists. If possible, create or verify a backup before you proceed.

1. Open the Start menu and click Settings (gear icon).
2. In the Settings window, choose Update & Security (Windows 10, for 11, skip this step)
3. Select Windows Update from the sidebar and click View update history.

4. Click Uninstall updates.

5. Find the most recent update in the list (look at the “Installed on” date), select it, and click Uninstall.

Rollbacks revert only the selected update, so you retain files and apps. If the problem returns after Windows offers the same update again, use Pause updates for a short period and monitor stability. 

Method 3. Run the DISM Command and Fix Protected Files with SFC

The Deployment Image Servicing and Management (DISM) command repairs the Windows system image, which holds key files required for the operating system. This method is the most useful when updates fail or corruption spreads across multiple components. DISM alone will not repair damaged system files; it only restores the image store. No backup is required. However, remember not to use this command on a failing drive. 

1. Press Windows + S, type cmd, then right-click Command Prompt and select Run as administrator.

2. In the command window, type: DISM /Online /Cleanup-Image /ScanHealth. Press Enter. This checks for corruption but does not repair it.

3. Next, type: DISM /Online /Cleanup-Image /RestoreHealth. Click Enter. This command repairs the system image. Wait for the process to complete, then close the window.

4. In the same window, enter: sfc /scannow.
5. Wait for verification to reach 100% and restart the PC.

If SFC reports repairs but the error returns, repeat SFC once after a reboot. Persistent failures after DISM/SFC usually point to disk corruption or an app-specific issue.

Method 4. Run the CHKDSK Command

CHKDSK (Check Disk) checks for bad sectors and repairs the file system structure on your drive. It can resolve errors caused by drive corruption or metadata inconsistencies. However, on a drive showing physical failure symptoms (clicking, grinding noises, repeated disconnections), CHKDSK may worsen the problem. Always back up important files before running them on suspect hardware.

1. Open Command Prompt as Administrator.

2. Enter the command: chkdsk C: /f /r. Replace C: with the affected drive letter.

3. If prompted to schedule the scan on reboot, type Y and restart your PC. Wait for the scan to finish before testing the drive again.

CHKDSK addresses generic “File system error” messages rooted in NTFS corruption or bad sectors. Use it when errors appear system‑wide, and data access also looks unreliable. If CHKDSK reports many bad clusters, plan immediate data recovery.

Method 5. Reset the Microsoft Store Cache

Store-based apps may crash with file system errors when the Store cache is corrupted. A reset clears the cache without removing installed apps or your account. Use this when the error appears with Microsoft Store or Store apps, including Photos and similar apps. It directly targets codes -2147219195 (Store/Photos) and helps with -2147219196 (Photos/Calculator) if the issue stems from the Store pipeline. No backup is required. 

1. Press Windows key + R to open Run.
2. Type wsreset.exe and press Enter.

3. Wait for the reset window to complete; the Store reopens.
4. Launch the app that failed and confirm the result.

A cache reset does not repair deeper OS corruption. If Store apps still fail across the board, run DISM + SFC next. If only one Store app fails, reinstall that app from the Store or use the next method to remove it cleanly, then install it again. 

Method 6. Reinstall the Problematic Application

If the error relates to a single program, you can reinstall it. This often resolves the problem. A standard uninstall may leave registry entries and cache behind. Use a cleanup tool, and it removes them completely. Before you uninstall, confirm that you have the license key or installation files for paid software. Remember, it works only if one app is affected. This method does not fix system-wide errors.

1. Open Setting. Go to Apps and then to Installed apps.
2. Select the problematic program and choose Uninstall.

3. Confirm removal and restart the PC.

4. Download the latest version of the program from its official website.
5. Reinstall the software and test if the error persists.

A clean reinstall often resolves codes tied to a single app: -2015294522 (Notepad), -2143322101 (Minecraft Launcher/PC Game Pass), and -2147219196 (Photos/Calculator). If many apps fail with similar codes, switch to DISM/SFC.

Method 7. “Reset this PC” (last resort re‑install of Windows)

If the error persists across many apps and methods, Reset this PC reinstalls Windows. You can keep personal files or remove everything. Apps and drivers reinstall afterward, so plan time and have installers and license keys ready. Back up documents to OneDrive or an external drive first, and sign out of apps. Use this only after other methods fail.

1. Open Settings. Go to System and then Recovery.

2. Select Reset this PC.

3. Choose Keep my files (recommended first) or Remove everything.

4. Choose Cloud download or Local reinstall, then confirm and start.

5. After the reset completes, install updates and your apps, and restore your files

A reset clears deep corruption that resists repair and can resolve stubborn Store and inbox app errors, plus broad system faults that DISM/SFC did not fix. Treat it as a clean slate. If corruption returns quickly, suspect hardware (drive/RAM) and test the PC.

Conclusion

File system errors on Windows 10 and 11 can usually be resolved without a hardware replacement. With the right steps, you can fix errors, restore stability, and use your apps normally. Act early before errors become more serious. After each fix, confirm that the error is gone. Do not run through every solution at once. If files disappear during the process, recover them first, then apply the next change. Finally, keep regular backups so future errors never put important data at risk.