DISM exe 1392 error on Windows 10: Fixes

The DISM.exe error 1392 on Windows 10 means the Deployment Imaging Service and Management tool cannot read or repair a corrupted file, usually because the file’s checksum or security descriptor is damaged. The fix is to run a specific sequence of System File Checker and DISM commands in a particular order, then reboot and retry. Below is the exact process, why it works, and what to do if the standard steps fail.

What Is DISM and Why Does Error 1392 Happen?

DISM (Deployment Imaging Service and Management) is a built-in Windows command-line tool that services and repairs Windows images, including the component store (WinSxS) that holds system files. Error 1392, with the message “The file or directory is corrupted and unreadable,” typically appears when you run DISM /Online /Cleanup-Image /RestoreHealth and DISM encounters a file it cannot parse. This can happen after a failed update, a disk error, a sudden power loss, or malware that damaged system files. The error is not a hardware failure by itself, but it often indicates that the Windows image is in a state where standard repair tools struggle.

Before You Start: Check Disk and Back Up

Before running any repair commands, do two things. First, back up any important files to an external drive or cloud service—repair tools can occasionally make things worse if the disk is failing. Second, check the disk for physical errors with chkdsk. Open Command Prompt as Administrator and run:

chkdsk C: /f /r

This will schedule a scan on restart. Let it complete. If chkdsk finds bad sectors, that is a hardware problem, and the 1392 error may persist even after repair. In that case, replace the drive and restore from backup.

The Standard Fix: Run SFC and DISM in the Right Order

Microsoft recommends running System File Checker (SFC) first, then DISM, then SFC again. The order matters because SFC repairs files using the local cache, and DISM repairs the cache itself. If you run DISM first and it fails, you still have a chance with SFC. Here is the exact sequence:

Open Command Prompt as Administrator (right-click Start, choose “Command Prompt (Admin)” or “Windows PowerShell (Admin)”).
Run sfc /scannow. Wait for it to finish. If it says it found and repaired files, reboot and check if the error is gone.
If SFC reports that it could not repair some files, run DISM /Online /Cleanup-Image /RestoreHealth. This will take 10-20 minutes. If it completes with “The restore operation completed successfully,” reboot and run sfc /scannow again.
If DISM fails with error 1392, try the steps below.

What to Do When DISM Itself Fails with 1392

If DISM throws 1392 even after SFC, the component store is likely too damaged to repair from itself. Try these in order:

Use a Windows installation media as a repair source. Insert a Windows 10 USB or DVD, then run: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim /LimitAccess (replace D: with the drive letter of your media). This uses the clean image from the media instead of the local store.
If you only have an ISO file, mount it by double-clicking it, then note the drive letter and use that in the /Source path.
If the install.wim is too large or you get an error about the source, extract the install.wim to a folder first, then use /Source:C:\path\to\install.wim.
Try the offline repair: Run DISM /Online /Cleanup-Image /StartComponentCleanup first to clear out old versions, then retry RestoreHealth.

If DISM Still Fails: Use Windows Update and Reset

Sometimes the repair source itself is corrupted. In that case, try these alternatives:

Run DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\Windows\WinSxS (this is the default, but it may already be broken).
Use the Windows Update as a source: DISM /Online /Cleanup-Image /RestoreHealth /Source:Windows Update (this is the default when no source is specified). If Windows Update is blocked, this fails.
If all DISM attempts fail, the last resort is to reset Windows 10 via Settings > Update & Security > Recovery > “Reset this PC.” Choose “Keep my files” to preserve personal data, but reinstall apps. This will replace the entire system, eliminating the corrupted files.

Common Mistakes and Misconceptions

One common mistake is running DISM without administrative privileges—it will fail instantly. Another is expecting DISM to fix hardware issues; it cannot. Also, many users think error 1392 means their SSD is dead, but it is almost always a software corruption issue. A frequent misconception is that you should run DISM before SFC; Microsoft’s official guidance is to run SFC first, then DISM, then SFC again. Running DISM first can sometimes make the problem worse if the component store is already broken, because DISM tries to read the same corrupted files.

Frequently Asked Questions

Can I ignore DISM error 1392?

If you only see the error when running DISM manually and your system works fine, you might ignore it temporarily. But it indicates underlying corruption that can cause future update failures or crashes. It is best to fix it.

Will error 1392 delete my files?

No, running DISM or SFC does not delete personal files. The commands only repair system files. However, if you use “Reset this PC” with “Remove everything,” that will delete files, so choose “Keep my files” if you want to preserve them.

How long does DISM take?

Typically 10-20 minutes, but it can take longer on slower drives or if the image is large. Do not interrupt it—let it finish.

Do I need an internet connection for DISM?

If you use the default source (Windows Update), yes. If you specify a local source like a USB drive, no internet is needed.

What if I get error 87 or 0x800f081f instead of 1392?

Error 87 means the command syntax is wrong—check your spelling. Error 0x800f081f means the source files cannot be found, so check the path to the install.wim.

Is there a way to avoid this error in the future?

Keep Windows Update enabled, run chkdsk periodically, and avoid force-shutting down your PC. Also, run sfc /scannow monthly as a preventive measure.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →