sodcalculator

10 Tech How-To

Fix Chrome Bad Image Error 0xc000012f (Step-by-Step)

Guide 10-52824 · Updated · Step by step

This guide walks you through fixing the “chrome.exe – Bad Image” error with status code 0xc000012f. This Windows error usually appears when Chrome tries to load a corrupted or incompatible DLL file, often after a Windows update, a Chrome update, or a faulty third-party program. The steps below will help you identify the cause and restore Chrome to working order.

What You’ll Need

  • Administrator access to your Windows PC (to run commands and modify system files).
  • Your Windows login password if prompted.
  • An internet connection (to download updates or reinstall Chrome).

Step-by-Step

  1. Restart your computer. A simple restart can clear temporary glitches that cause this error. If the error persists after restart, continue.
  2. Run Chrome as Administrator (temporary test). Right-click the Chrome shortcut and select “Run as administrator.” If Chrome opens without the error, the problem is likely a permission or file-corruption issue that the next steps will fix. Close Chrome and proceed.
  3. Update Windows. Go to Settings > Update & Security > Windows Update, then click “Check for updates.” Install any pending updates and restart your PC. Many bad image errors are fixed by Windows patches.
  4. Update Chrome. Open Chrome (if it opens), go to the three-dot menu > Help > About Google Chrome. Chrome will check for updates and install them automatically. Restart Chrome after updating. If Chrome won’t open at all, skip to step 5.
  5. Repair Chrome using the installer. Download the latest Chrome installer from the official Google Chrome website. Run the installer – it will repair the existing installation without deleting your bookmarks or passwords. Restart your PC afterward.
  6. Run System File Checker (SFC). Open Command Prompt as administrator (type “cmd” in the Start menu, right-click, and select “Run as administrator”). Type sfc /scannow and press Enter. Wait for the scan to complete (this can take 10-20 minutes). If it finds and repairs corrupted system files, restart your PC.
  7. Run DISM (Deployment Imaging Service and Management Tool). In the same Command Prompt window, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs the Windows system image. Wait for it to finish (may take 20-30 minutes), then restart.
  8. Check for conflicting third-party software. Some programs (especially antivirus tools, VPNs, or system optimizers) can inject DLLs into Chrome and cause this error. Temporarily disable your antivirus or uninstall recently installed programs that might interfere. If the error goes away, re-enable or reinstall them one by one to find the culprit.
  9. Clear Chrome’s cache and profile (if Chrome opens occasionally). If Chrome opens but shows the error intermittently, go to Chrome settings > Privacy and security > Clear browsing data. Also consider resetting Chrome settings to default (Settings > Advanced > Reset and clean up > Restore settings to their original defaults).
  10. Reinstall Chrome completely. If none of the above work, uninstall Chrome via Settings > Apps > Apps & features. Select Chrome, click Uninstall, and check the box to delete browsing data. Then download and install a fresh copy from the official Google Chrome page.
  11. Check for malware. Run a full system scan with Windows Defender (or your preferred antivirus). Malware can corrupt DLL files and cause bad image errors. Go to Windows Security > Virus & threat protection > Scan options > Full scan.
  12. Use the Event Viewer for more details (advanced). Press Win + X and select “Event Viewer.” Go to Windows Logs > Application and look for errors related to “chrome.exe” or the error code 0xc000012f. The details may show which specific DLL file is failing, which can help you target the fix.

Common Mistakes

  • Skipping the restart. Many users jump straight to reinstalling Chrome without trying a simple reboot, which can fix temporary file-lock issues.
  • Downloading Chrome from unofficial sources. Always use the official Google Chrome website. Third-party download sites may bundle modified Chrome installers that cause this exact error.
  • Running SFC but not DISM. SFC often cannot fix corrupted system files if the underlying Windows image is damaged. DISM must be run first or after SFC to fully repair the system.
  • Ignoring third-party software. Assuming the error is always Chrome’s fault. Antivirus or system utilities can overwrite Chrome’s DLLs.
  • Not backing up bookmarks before reinstalling. If you choose to delete browsing data, you’ll lose bookmarks unless you export them first (Chrome menu > Bookmarks > Bookmark manager > Export).

Tips

  • Keep Windows and Chrome updated automatically. Enable automatic updates for both to prevent future DLL mismatches.
  • Use Chrome’s built-in cleanup tool. Go to Chrome settings > Advanced > Reset and clean up > Clean up computer. This scans for harmful software that might be interfering.
  • Create a system restore point. Before making major changes (like running DISM or uninstalling Chrome), create a restore point (Control Panel > System > System Protection > Create). This lets you roll back if something goes wrong.
  • Check the specific DLL mentioned in the error. If the error message names a DLL (e.g., “chrome.dll” or “msvcp140.dll”), search for that filename online to see if it’s a known issue with a specific fix.
  • Use the 64-bit version of Chrome. If you’re on a 64-bit Windows, ensure you’re using the 64-bit Chrome build (check in Chrome’s About page). The 32-bit version can sometimes have compatibility issues.

Troubleshooting

If the error persists after following all steps, try these additional checks:

  • Check for corrupted user profile. Create a new Windows user account and try running Chrome from there. If it works, your original profile is corrupted. You can migrate your bookmarks and passwords manually.
  • Perform a clean boot. Use msconfig to disable all non-Microsoft services and startup items, then restart. If Chrome works, re-enable services one by one to find the conflict.
  • Update your graphics drivers. Outdated GPU drivers can cause DLL conflicts. Visit your GPU manufacturer’s website (NVIDIA, AMD, Intel) and install the latest driver.
  • Check for pending Windows updates again. Sometimes a failed update can leave the system in an inconsistent state. Run Windows Update again and install any optional updates.
  • Use the Chrome Enterprise policy to disable extensions. If the error mentions an extension DLL, you can launch Chrome with the flag --disable-extensions to test. If that works, disable extensions one by one in Chrome’s settings.
  • If all else fails, consider a system restore. Use a restore point from before the error started. This will revert Windows system files to a previous state without affecting your personal files.

Frequently Asked Questions

What does error 0xc000012f mean?

This error code indicates that a DLL file required by Chrome is either corrupted, missing, or incompatible with your current Windows version. It’s a Windows-level error, not a Chrome-specific bug.

Will I lose my bookmarks if I reinstall Chrome?

If you choose to delete browsing data during uninstall, yes. To avoid this, export your bookmarks first (Bookmarks > Bookmark manager > Export bookmarks) or sync them with your Google account. If you just run the Chrome installer to repair, your data stays intact.

Why does this error happen after a Windows update?

Windows updates can change system DLLs or security policies that Chrome depends on. If the update is incomplete or conflicts with Chrome’s current version, you’ll see this error. Running SFC and DISM often resolves it.

Can antivirus software cause this error?

Yes. Some antivirus programs integrate with Chrome by injecting DLLs to scan web traffic. If those DLLs are outdated or incompatible, they trigger the bad image error. Temporarily disabling or uninstalling the antivirus can confirm this.

Is this error dangerous or a sign of a virus?

Not necessarily. It’s usually a software conflict or file corruption. However, if you downloaded Chrome from a non-official site, malware could be involved. Running a full antivirus scan is recommended as a precaution.

How long does the SFC/DISM process take?

SFC typically takes 10-20 minutes, while DISM can take 20-30 minutes or longer. Both require an administrator command prompt and a stable internet connection for DISM to download repair files.

Related

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 →