Fix the "Bad Image" error 0xc0000020 on Windows
✓ Reviewed & updated June 2026You open an app and instead of launching, Windows throws a "Bad Image" pop-up saying a file "is either not designed to run on Windows or it contains an error," with error status 0xc0000020. It usually names a specific .dll file. The good news: it's almost always a corrupted or mismatched system file or runtime — not failing hardware — and it's fixable. Work through the steps below in order.
Note the file name. The error names a specific DLL. Write it down — it's a strong clue. If it starts with MSVC, VCRUNTIME or api-ms-win, the fix is almost certainly reinstalling the Visual C++ runtime (step 4).
Quick checklist
- Restart your PC and reopen the app
- Run SFC and DISM scans
- Reinstall the app that triggers the error
- Reinstall the Visual C++ Redistributables
- Install Windows updates
- Run a malware scan
What error 0xc0000020 means
0xc0000020 is a "bad image" status — Windows tried to load a file (usually a DLL) that an app depends on, but found it corrupted, the wrong version, or missing. The most common cause is a damaged Visual C++ runtime, followed by corrupted Windows system files or a broken app install. Each fix below targets one of those.
The 6 fixes
Restart and reopen the app
A pending update or a one-off glitch can cause this, and a clean restart clears it.
- Save your work and restart your PC fully.
- Open the app again. If the error's gone, you're done; if not, continue.
Run SFC and DISM scans
These built-in tools find and repair corrupted Windows system files — a common source of bad-image errors.
- Click Start, type cmd, right-click Command Prompt → Run as administrator.
- Run
sfc /scannowand wait for it to finish. - Then run
DISM /Online /Cleanup-Image /RestoreHealthand let it complete. - Restart and test the app.
Reinstall the app that triggers the error
If only one app shows the error, its own files are likely damaged.
- Go to Settings → Apps, find the app, and Uninstall it.
- Download a fresh copy from the official source and reinstall.
- Open it again.
Reinstall the Visual C++ Redistributables
This is the fix for most 0xc0000020 errors, especially when the named DLL starts with MSVC or VCRUNTIME. Many apps rely on these runtime files, and if they're damaged, you get a bad image error.
- Open Settings → Apps → Installed apps.
- Look for Microsoft Visual C++ Redistributable entries (there are usually several years/versions).
- Download the latest Visual C++ Redistributable packages (both x86 and x64) from Microsoft's official site and run them — choosing Repair if offered, or installing fresh.
- Restart and test the app.
Install Windows updates
Missing system updates can leave runtime files out of date and mismatched.
- Go to Settings → Windows Update → Check for updates.
- Install everything available, then restart and try the app.
Run a malware scan
Malware can corrupt or replace DLL files, which produces bad-image errors.
- Open Settings → Privacy & security → Windows Security → Virus & threat protection.
- Run a full scan and remove anything it finds.
- Restart and test the app.
Frequently asked questions
The error names a specific DLL. Does that matter?
Yes — it's your biggest clue. If the file starts with MSVC, VCRUNTIME or api-ms-win, reinstalling the Visual C++ Redistributables (fix 4) almost always solves it. For other DLLs, reinstalling the app that uses them (fix 3) is the place to start.
The error appears for several different apps. What now?
When it's system-wide rather than one app, the cause is usually corrupted Windows files or a damaged runtime. Run SFC and DISM (fix 2), then reinstall the Visual C++ Redistributables (fix 4).
Is 0xc0000020 a sign of hardware failure?
Almost never. It's a software/file problem — a corrupted or mismatched DLL — not a failing drive or RAM. The fixes here address the file side.
Is it safe to reinstall the Visual C++ Redistributables?
Yes. They're free Microsoft runtime packages that many programs share. Reinstalling or repairing them is safe and won't affect your personal files.
Hitting a different Windows error code? See our fix for Windows Update error 0x80070005. Still stuck here? Tell us the exact DLL named in the error and we'll help.
Send us the details →