Fix Windows Error 0x23D: Missing System File

This error means a required system file is corrupt or missing. Usually triggered by bad updates or disk issues. Repair it with SFC and DISM, then check your disk.

Quick Answer

Run sfc /scannow from an elevated command prompt, then DISM /Online /Cleanup-Image /RestoreHealth, then chkdsk /r. Reboot after each step. That fixes 90% of these cases.

Now let's back up. The error code 0X0000023D shows up as a blue screen or a dialog that says "The required system file %hs is bad or missing." That %hs is a placeholder for the actual file name, but it often doesn't show up. You're left guessing which file. From my years at the help desk, I've seen this triggered by a failed Windows update that left a driver or system DLL half-written. Sometimes it's a failing hard drive with bad sectors. Once in a while, it's a corrupted registry entry from a forced shutdown.

Don't panic. You don't need to reinstall Windows yet. Follow these steps in order—they're boring but they work. Each one repairs a different layer of the problem.

Before You Start

You'll need admin rights. If you can log into Windows, great. If not, boot into Safe Mode or the Recovery Environment. To get to Safe Mode from the login screen, hold Shift while clicking Restart. From there choose Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4. If you're already at the desktop, just right-click the Start button and select "Command Prompt (Admin)" or "Windows PowerShell (Admin)".

Step-by-Step Fix

Step 1: Run System File Checker (SFC)

Open Command Prompt as administrator. Type sfc /scannow and press Enter.
Let it run—it takes 10-15 minutes. Don't close the window.
When it finishes, you'll see one of three messages: "Windows Resource Protection did not find any integrity violations" (good), "found corrupt files and successfully repaired them" (even better), or "found corrupt files but was unable to fix some of them" (means you need Step 2).

After this, restart your PC even if it says no issues. I've seen SFC report clean but a reboot clears the error because the filesystem gets refreshed.

Step 2: Run DISM to Repair the System Image

If SFC couldn't repair everything, the system image itself is damaged. DISM fixes that.

In the same admin command prompt (or reopen it), type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
This takes up to 30 minutes. It's normal for it to look stuck at 20% for a while.
When it says "The operation completed successfully," reboot.

Then run sfc /scannow again. DISM repairs the source files that SFC needs.

Step 3: Check Your Hard Drive for Errors

If the error still appears, the file might be on a bad sector. A disk check will find and mark those sectors. This is especially common on older mechanical drives.

Open an admin Command Prompt.
Type chkdsk /r and press Enter.
You'll see a prompt that the drive is in use and asking to schedule it for the next restart. Type Y and press Enter.
Restart your PC. chkdsk will run before Windows loads—it looks like a black screen with white text and a progress bar. Let it finish. It can take over an hour on a large drive.

Once it's done, Windows starts normally. Test if the error is gone.

Alternative Fixes If Those Don't Work

Roll Back Recent Updates

If this error started after a Windows Update, roll back. Go to Settings > Windows Update > Update History > Uninstall updates. Look for the most recent quality or driver update and uninstall it. I've fixed machines where a graphics driver update caused this exact error code. After uninstalling, reboot and pause updates for a week to see if the error stays away.

Use System Restore

If you have a restore point from before the error, use it. Search for "System Restore" in the Start menu, run it, pick a point that's a few days old. This won't touch your personal files, but it will remove installed programs from after that date. Only do this if SFC and DISM didn't help.

Repair Install (Last Resort)

If you're still stuck, do an in-place repair install. Download the Windows 11 Installation Assistant (or Windows 10 Media Creation Tool) from Microsoft's site. Run it and choose "Upgrade this PC now." It keeps your files and apps but replaces all system files. It's a 2-hour process, but it's saved me more than once. Make sure you have 20GB of free space.

Prevention Tips

The best way to avoid this error is to not let your system files get corrupted in the first place. Three things I tell everyone:

Don't force shutdowns. If your PC is frozen, wait 5 minutes before holding the power button. Sudden power loss mid-write is a top cause of corrupt system files.
Check your disk health yearly. Use CrystalDiskInfo for free. It can read the S.M.A.R.T. data and warn you about failing drives before they take your files down with them.
Keep automatic updates on. Yes, they can cause problems, but they also include fixes. If you're worried, set active hours so updates install at night. The risk of skipping them is worse.

That's it. Start with SFC and DISM, then run chkdsk. If the error persists after all three, try rolling back updates or a repair install. One of those will get you back to work.