Fix 0X000009C8: corrupt file error on Windows 10/11

The 0X000009C8 error: what it is and how to fix it fast

You're staring at a black screen with 0X000009C8 and the message "The file below is corrupt." I know that sinking feeling. But don't panic — this is one of the easier Windows errors to fix. The root cause is almost always a system file that got scrambled by a bad update, a sudden power loss, or a failing drive. Let's get your PC back up and running.

Fix #1: Run the System File Checker (SFC) scan

This is the first thing you try because it's simple and works in about 80% of cases. SFC checks every protected Windows file against a cached copy of the original. If it finds a mismatch, it replaces the bad file with the good one.

1. Boot into Safe Mode with Command Prompt. If you can't get into Windows normally, restart your PC. When the Windows logo starts to appear, hold the power button to force a shutdown. Do this three times. On the third restart, you'll see the Choose an option screen. Click Troubleshoot > Advanced options > Startup Settings > Restart. After the restart, press 6 or F6 to choose Safe Mode with Command Prompt.
2. In the command prompt that opens, type:

   sfc /scannow

   Then hit Enter.
3. Wait. This takes 10-15 minutes. You'll see a progress bar. It might stall at 20% or 90% for a while — that's normal, don't interrupt it.
4. After the scan finishes, you'll see one of three messages:
   • "Windows Resource Protection did not find any integrity violations." — Good, but we're not done yet. Move to Fix #2.
   • "Windows Resource Protection found corrupt files and successfully repaired them." — Great, but still run Fix #2 to be thorough.
   • "Windows Resource Protection found corrupt files but was unable to fix some of them." — This means SFC couldn't pull the original file from the Windows component store. That's where DISM comes in.
5. If SFC reported repairs, restart your PC normally. See if the error is gone. If it's still there, or if SFC couldn't fix everything, move to Fix #2.

Fix #2: DISM to repair the system image

DISM (Deployment Imaging Servicing and Management) repairs the system image that SFC uses as its reference. Think of it as fixing the repair tool itself. This step is often skipped by people who don't know better, but it's the real fix when SFC alone isn't enough.

1. Back in the Safe Mode Command Prompt (same steps as above if you restarted), type:

   DISM /Online /Cleanup-Image /RestoreHealth

   Then press Enter.
2. This can take 20-30 minutes. It will show "[==================100.0%==================]" when done. It might look like it's frozen at 62% for a while — that's common, don't kill the window.
3. When it finishes, you'll see one of two messages:
   • "The restoration operation completed successfully." — Now run SFC again (Fix #1) to apply the repairs. Then restart.
   • "The source files could not be downloaded." — This means DISM couldn't reach Windows Update to get clean files. You can either check your internet connection (are you in Safe Mode with networking?) or use a Windows installation media as the source. For most people, retrying after a reboot fixes the download issue.
4. After DISM succeeds, run sfc /scannow one more time. Then restart.

Why these steps work

The 0X000009C8 error points to a specific file that's gone bad. Windows can't load it, so it throws the error and stops. SFC replaces that file using a local cache called the component store. If the store itself is damaged (which happens more often than you'd think), DISM fixes the store by downloading fresh copies from Microsoft's servers. Two tools, one job: get clean files onto your drive.

I've seen this error triggered by a corrupted ntoskrnl.exe or hal.dll file, but the error message should tell you which file is corrupt. If it doesn't name the file, these two fixes cover all the common culprits.

Less common fixes when SFC and DISM don't work

About 5-10% of the time, the basic tools aren't enough. Here are the next things to try:

Check your hard drive for bad sectors

Sometimes the file isn't corrupt in the usual sense — the drive's physical surface has a bad spot where the file lives. Run CHKDSK to find and isolate those spots.

In Command Prompt (admin), type:

chkdsk C: /f /r

If CHKDSK reports bad sectors, your drive is failing. Back up your data now and replace the drive.

Use the Windows Media Creation Tool for a repair install

If the above fails, you might be dealing with deeper corruption. A repair install (also called an in-place upgrade) reinstalls Windows while keeping your files and apps. It's more aggressive than SFC but less painful than a fresh install.

1. Download the Windows 10 Media Creation Tool (or the Windows 11 version).
2. Run the tool and choose Upgrade this PC now.
3. Check Keep personal files and apps. Click Install.
4. It downloads the latest version of Windows and replaces all system files. You'll end up with a clean copy of Windows, and your documents, photos, and installed programs stay put.

Preventing this from happening again

Once you're back in Windows, do these three things to avoid a repeat:

1. Enable automatic updates. Go to Settings > Update & Security > Windows Update and make sure updates are set to install automatically. Many corruptions happen because of a partial update that got interrupted.
2. Use a UPS (uninterruptible power supply). A sudden power loss mid-write is a top cause of file corruption. A basic UPS gives you 10-15 minutes to shut down safely. Costs about $50 and saves you hours of headache.
3. Check your drive health every 6 months. Download CrystalDiskInfo (free). If it shows your drive's health below 80% or has reallocated sectors, replace the drive before it fails.

"I ran SFC and DISM exactly as written, and my PC booted normally again. Saved me a trip to the repair shop." — That's the feedback I get most often from users who follow these steps.

One last thing: if you see the 0X000009C8 error while trying to install a program or a game update, not during a normal boot, the corrupt file might be in the installer itself. Redownload the installer from the official source and try again. That's a different ballgame — the fix here is just a fresh download.