mfc100chs.dll Won’t Load: Rebuild the Right Runtime on Windows

The program can't start because mfc100chs.dll is missing from your computer. Try reinstalling the program to fix this problem.

If Windows says mfc100chs.dll was not found, could not be loaded, or is a Bad Image, the file is usually part of the Microsoft Visual C++ 2010 MFC runtime used by the program that installed it.

As an Amazon Associate I earn from qualifying purchases.

Which fix applies to you

Use the first matching situation:

• If several older applications fail, repair or reinstall the Visual C++ 2010 SP1 Redistributable.
• If only one program or game fails, repair, verify, or reinstall that program first.
• If the error mentions 0xc000007b, Bad Image, or an incompatible module, install the package matching the application architecture.
• If the file disappeared after an update or installation, check Windows Security Protection history.
• If the file exists but Windows still reports it missing, check related Visual C++ files and the application’s private DLL copy.
• If Windows reports broader system corruption, run DISM followed by SFC.
• If the problem began immediately after a system change, consider System Restore.
• Do not begin by downloading a standalone copy of mfc100chs.dll or running regsvr32.

The safest starting point is the official Visual C++ 2010 package, followed by repair of the affected application.

What mfc100chs.dll is

mfc100chs.dll is a genuine Microsoft Visual C++ 2010 MFC localization DLL. It belongs to the Microsoft.VC100.MFCLOC component and contains Simplified Chinese resources for Microsoft Foundation Classes, commonly called MFC.

The filename breaks down roughly as follows:

• mfc refers to Microsoft Foundation Classes.
• 100 identifies the Visual C++ 10.0 generation, which corresponds to Visual Studio 2010.
• chs identifies the Simplified Chinese resource set.
• .dll means it is a dynamic-link library loaded by an application.

This is not a generic Windows file that every clean Windows installation must contain. It may be installed centrally by a Visual C++ redistributable package, or placed beside a program executable by the program’s installer.

Microsoft documents localized MFC libraries as redistributable components, with separate resource DLLs for supported languages. The MFC localization component is described in Microsoft’s Redistribute the MFC Library documentation.

The file is associated with:

• Visual Studio 2010 and Visual C++ 10.0
• Microsoft Foundation Classes
• The Visual C++ 2010 SP1 Redistributable
• The MFC security update package associated with KB2565063
• Application-local copies bundled by older applications and games

It is not automatically malware because an application reports it as missing. It is also not automatically safe merely because the filename looks familiar. Location, digital signature, architecture, and installation source all matter.

Get the correct Visual C++ package

The official package to try is the Microsoft Visual C++ 2010 SP1 Redistributable Package MFC Security Update.

That Microsoft Download Center page provides:

• vcredist_x86.exe for 32-bit applications
• vcredist_x64.exe for 64-bit applications on ordinary Intel or AMD Windows PCs
• vcredist_ia64.exe for Itanium systems, which is not intended for normal desktop computers

The current Microsoft legacy-runtime index also lists the Visual C++ 2010 SP1 x86 and x64 redistributables. Visual C++ 2010 is a legacy runtime, so it remains installed side by side with newer Visual C++ generations.

Do not assume that installing Visual C++ 2015–2022 replaces Visual C++ 2010. Applications built for the older runtime can still require the older MFC files.

Repair the existing runtime

1. Press Windows + R.
2. Type appwiz.cpl.
3. Press Enter.
4. Find entries named similar to:
5. Microsoft Visual C++ 2010 x86 Redistributable
6. Microsoft Visual C++ 2010 x64 Redistributable
7. Select the entry that matches the affected program.
8. Choose Change, Modify, or Uninstall, depending on what Windows displays.
9. Choose Repair if that option is available.
10. Allow the repair to finish.
11. Restart Windows.
12. Open the affected application again.

If the program is 32-bit, repair the x86 package even when Windows itself is 64-bit. If the program is 64-bit, repair the x64 package.

Reinstall the runtime

If the runtime is absent or Repair fails:

1. Open the official Microsoft download page linked above.
2. Download vcredist_x86.exe for a 32-bit application.
3. Download vcredist_x64.exe for a 64-bit application.
4. On 64-bit Windows, install both packages when you do not know which architecture the application uses.
5. Close the affected program.
6. Right-click the downloaded installer and select Run as administrator.
7. Accept the Microsoft license terms.
8. Complete the installation.
9. Restart Windows.
10. Test the application again.

Installing both x86 and x64 packages on 64-bit Windows is often the most practical coverage for older software because many applications and games remain 32-bit. The package architecture must match the application, not merely the Windows installation.

x86, x64, System32, and SysWOW64

A 64-bit version of Windows can run both 64-bit and 32-bit applications. Those applications do not use the same runtime architecture.

Use this general rule:

Application	Required Visual C++ package
32-bit application	x86
64-bit application	x64
Unknown application on 64-bit Windows	Usually install both
32-bit Windows	x86

A 32-bit program cannot load a 64-bit mfc100chs.dll, and a 64-bit program cannot use a 32-bit replacement.

On 64-bit Windows:

• %windir%\System32 normally contains 64-bit system binaries.
• %windir%\SysWOW64 normally contains 32-bit system binaries used by 32-bit applications.

The names are confusing, but do not move files between these directories manually. Microsoft explains this behavior in its File System Redirector documentation.

The file may also appear in the application’s own folder. That is called application-local deployment. An older program may carry its own MFC files rather than relying entirely on the centrally installed redistributable.

How to identify the application architecture

If the program’s documentation does not say whether it is 32-bit or 64-bit:

1. Open the program’s installation folder.
2. Look for whether it was installed under C:\Program Files or C:\Program Files (x86).
3. Check the program’s installer or launcher settings.
4. Check Task Manager while the program is running. Some Windows versions identify 32-bit processes with a suffix such as (32 bit).
5. If you are using 64-bit Windows and the answer remains unclear, install both Visual C++ 2010 x86 and x64 packages.

The installation directory is a useful clue, not an absolute rule. The application vendor’s documentation and the executable’s actual architecture are more reliable.

Repair the affected application

If only one application reports the error, its own installation is the first place to investigate. The program may use an application-local copy of the MFC runtime, or its installer may have failed to place all required files.

Use the Windows repair option

On Windows 11:

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Find the affected program.
5. Select the three-dot menu.
6. Choose Advanced options if available.
7. Select Repair.
8. Start the program again.

On Windows 10, the path is usually:

1. Open Settings.
2. Select Apps.
3. Select Apps & features.
4. Select the affected application.
5. Choose Advanced options or Modify.
6. Choose Repair when available.

Some traditional desktop programs do not provide a Windows Repair button. In that case:

1. Press Windows + R.
2. Type appwiz.cpl.
3. Press Enter.
4. Select the application.
5. Choose Change or Repair.
6. Follow the installer prompts.

Verify a game installation

For a game, use the launcher’s built-in file verification or repair function. The exact label varies, but it may be called Verify files, Repair, Scan and repair, or Validate installation.

After verification completes:

1. Restart the launcher.
2. Start the game again.
3. If the same DLL error remains, repair or reinstall the Visual C++ 2010 runtime.
4. If both repairs fail, reinstall the game from its original vendor installer.

Do not copy a DLL from the Windows system directory into a game folder automatically. A game’s private DLL may need to match the exact build expected by that game.

Reinstall the application

Reinstalling is the correct fix when:

• The error path points inside the program’s installation folder.
• Only that application fails.
• The program was interrupted during installation or updating.
• A launcher reports missing or corrupted files.
• The application bundled its own Visual C++ runtime.

Before uninstalling, back up saved games, settings, templates, or other application data if the program stores them locally.

Then:

1. Uninstall the application from Settings or Programs and Features.
2. Restart Windows.
3. Download the installer from the original software vendor or use the original installation media.
4. Right-click the installer and choose Run as administrator.
5. Allow the setup to install its prerequisites.
6. Restart Windows if the installer requests it.
7. Start the application.

If the program’s installer includes a Visual C++ prerequisite, allow it to run even if a newer Visual C++ package is already installed.

Understand the common error messages

The wording changes with the Windows version, application, language, and point of failure. Common variants include:

• The program can't start because mfc100chs.dll is missing from your computer.
• The code execution cannot proceed because mfc100chs.dll was not found.
• Reinstalling the program may fix this problem.
• Error loading mfc100chs.dll. The specified module could not be found.
• mfc100chs.dll could not be loaded.
• mfc100chs.dll is either not designed to run on Windows or it contains an error.
• Bad Image
• An installer error naming a path such as C:\Windows\SysWOW64\mfc100chs.dll

These messages do not all mean the same thing.

A missing-file message commonly means that Windows could not find the DLL in the locations searched for that application.

A Bad Image message can mean that the DLL is corrupted, is the wrong architecture, or cannot be loaded because a related dependency is invalid. Microsoft’s generic Bad Image wording is documented in the MS-ERREF error reference.

“Specified module could not be found” can also refer to a dependency of mfc100chs.dll. The named file may exist while another required runtime file is absent.

Check related Visual C++ files

MFC applications often use several files from the same runtime generation. Depending on the program, related files may include:

• mfc100.dll
• mfc100u.dll
• msvcp100.dll
• msvcr100.dll

Do not download these individually. Their absence is a reason to repair or reinstall the complete Visual C++ 2010 package or the application that supplied them.

If mfc100chs.dll exists but the program still fails:

1. Note the complete path shown in the error.
2. Check whether the path is inside the application folder, System32, or SysWOW64.
3. Confirm that the application architecture matches the installed runtime.
4. Check whether related Visual C++ 2010 files are present beside the same application.
5. Review the application’s installation or launcher logs.
6. Repair the application.
7. Repair or reinstall the matching Visual C++ package.

Microsoft documents how Windows searches for DLLs and why an application-folder copy can take precedence over a system copy in Dynamic-link library search order.

Check Windows Security quarantine

Antivirus software can remove or quarantine a runtime file during an installation, update, or later scan. A quarantine event does not by itself prove that the file was malware.

Check the event before restoring anything:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Protection history.
4. Open the detection associated with the application or runtime.
5. Inspect the detected file path.
6. Note the detection name and action taken.
7. Determine whether the file came from the official Microsoft installer or the application’s original installer.

Do not restore a quarantined file merely because the application now fails. If the file was from an untrusted source, leave it quarantined and run a full scan.

If the file came from an official installer and is confirmed to be a genuine Microsoft runtime file, reinstalling the official package is generally preferable to manually restoring a single file. Microsoft explains the risks and behavior of restored detections in its Protection History guidance.

To run a full scan:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Choose Full scan.
5. Select Scan now.
6. Restart Windows if requested.

If the problem returns after reinstalling, run Microsoft Defender Offline and investigate the application directory for an untrusted replacement.

Repair Windows components with DISM and SFC

mfc100chs.dll is normally a Visual C++ redistributable or application component, not necessarily a protected Windows component. SFC may report no problem even when the Visual C++ runtime is missing.

Use DISM and SFC when:

• Several unrelated Windows components are failing.
• Windows updates or system files also appear damaged.
• DISM or SFC has already reported component corruption.
• The runtime installer itself behaves abnormally.
• The error began with broader system instability.

Run DISM before SFC.

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes at the User Account Control prompt.
6. Enter:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the command to finish.
2. Keep the elevated Command Prompt open.
3. Enter:

sfc /scannow

1. Wait until the scan reaches 100 percent.
2. Restart Windows.
3. Test the application.

If DISM repairs the component store but SFC reports no integrity violations, continue with the Visual C++ runtime and application repairs. That result does not prove that mfc100chs.dll itself was present or correctly deployed.

Repeatedly running SFC and DISM without recording what changed rarely helps. Outbyte PC Repair can scan for system problems and show what it identifies, while repair actions are performed by the full version; it is optional, and reinstalling the affected application remains the definitive fix when that program owns the DLL.

Deal with broken installer registration

Sometimes the Visual C++ runtime appears in Programs and Features, but Repair or Uninstall fails because Windows Installer data is incomplete.

Typical signs include:

• Repair reports that the installation source cannot be found.
• Uninstall asks for an unavailable installation package.
• Reinstallation stops before completion.
• The runtime entry remains after an unsuccessful removal.
• The installer reports that another installation is in progress.

Try this order:

1. Restart Windows.
2. Open Programs and Features with appwiz.cpl.
3. Select the Visual C++ 2010 x86 or x64 entry.
4. Choose Repair.
5. If Repair fails, run the official matching redistributable installer again.
6. Restart Windows.
7. Try the installer once more.

For scripted or silent repair environments, Microsoft documents these installer options:

vcredist_x86.exe /q /norestart
vcredist_x64.exe /q /norestart

Most home users should use the normal graphical installer so that errors are visible.

If Windows Installer registration remains damaged, use Microsoft’s Program Install and Uninstall troubleshooter, then restart Windows and rerun the official redistributable installer.

Do not use regsvr32 for this error

regsvr32 is not a general DLL repair command. It registers DLLs that expose a registration entry point such as DllRegisterServer.

mfc100chs.dll is an MFC language-resource runtime file. Registering it does not install the Visual C++ runtime, restore missing dependencies, correct x86 and x64 mismatches, or repair application-local deployment.

Do not run commands such as:

regsvr32 mfc100chs.dll

unless the application vendor specifically documents that procedure for its own component. For an ordinary missing or unloadable mfc100chs.dll error, repair the runtime or application instead. Microsoft describes the command’s actual purpose in its regsvr32 documentation.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Be cautious with manual DLL copying

Random DLL download sites are unsafe sources for this file. A downloaded copy can contain malware, have the wrong architecture, belong to a different Visual C++ build, or fail because another dependency is still missing.

Manual copying can also create a worse DLL search-order problem. If an incorrect copy is placed in an application folder, Windows may load it before a valid system copy.

The supported repair path is:

1. Use the official Microsoft Visual C++ 2010 redistributable installer.
2. Use the affected application’s Repair or Verify files function.
3. Reinstall the application from its original vendor installer.
4. Check antivirus quarantine before restoring anything.
5. Verify architecture before investigating individual files.

Application-local deployment is a legitimate option for software vendors, but it does not mean end users should obtain DLLs individually. Microsoft explains both centralized and application-local deployment in Redistribute Visual C++ files.

Check the DLL’s location and signature

The expected location depends on how the program was installed.

A centrally deployed copy may be found through the normal Windows system directories. On 64-bit Windows, a 32-bit application normally uses the redirected 32-bit system environment. An application-local copy may instead be beside the program executable.

To inspect the file:

1. Right-click the DLL.
2. Select Properties.
3. Open the Details tab.
4. Review the file description, product information, and version information if present.
5. Open the Digital Signatures tab if it exists.
6. Confirm that the signature is valid.
7. Select the signature and choose Details.
8. If Windows reports that the signature is invalid or absent where one is expected, do not replace or restore the file blindly.
9. Run a Microsoft Defender scan and reinstall the official runtime or application.

Do not treat one file size or version as universally correct. Microsoft has documented multiple Visual C++ 2010 builds and hotfix revisions, so size alone cannot establish authenticity.

Update drivers only when the evidence points there

mfc100chs.dll is not itself a graphics-driver, DirectX, or .NET component. Driver repair should be considered only when the affected vendor installer also identifies a driver problem or when another driver DLL is named.

If a driver-related error is present:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters, Sound, video and game controllers, or Network adapters.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Note the provider, date, and version.
8. Use Update Driver and let Windows search automatically, or install the driver from the hardware manufacturer.
9. Restart Windows.
10. Test the original application again.

Do not uninstall a working display or storage driver merely because mfc100chs.dll is missing. Outbyte Driver Updater can scan for outdated drivers and identify what it finds, while driver installation is performed by the full version; it is optional, and it does not replace repairing the Visual C++ runtime or reinstalling the affected application.

Use System Restore after a recent system change

System Restore is appropriate when the problem started immediately after:

• A runtime removal
• An application update
• A driver installation
• A system cleanup operation
• A Windows configuration change
• Security software changes

It is less appropriate as the first response to an isolated missing runtime file.

To open System Restore:

1. Press Windows + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the error began.
4. Select Scan for affected programs if available.
5. Review the programs and drivers that will be changed.
6. Select Next.
7. Select Finish.
8. Allow Windows to restart.

Microsoft says System Restore normally rolls back system files, registry settings, and installed programs without removing personal files. It can remove applications installed after the selected restore point, so review the affected-program list carefully.

After the restore completes, repair the Visual C++ 2010 package if the runtime still needs attention.

What to do when several programs fail

Several applications failing points toward a shared runtime, system cleanup, or security-software event.

Use this order:

1. Check Windows Security Protection history.
2. Repair the Visual C++ 2010 x86 package.
3. On 64-bit Windows, repair or install the x64 package as well.
4. Restart Windows.
5. Run DISM and SFC if other Windows components are also malfunctioning.
6. Test two affected applications.
7. If the error remains, inspect the paths named in each error dialog.

If all failures point to Windows runtime directories, the central redistributable is the main suspect. If each program points to its own installation directory, several application installations may have been damaged independently.

What to do when only one program fails

One affected program usually means the program’s own files or private runtime are incomplete.

Use this order:

1. Run the program’s Repair option.
2. For a game, verify or repair files through its launcher.
3. Check the error path.
4. Reinstall the program from its original installer.
5. Install the Visual C++ 2010 package requested by the application.
6. Check antivirus history.
7. Contact the application vendor with the exact error and path.

Do not replace a private application copy with a file copied from System32 or SysWOW64. The application may require a particular build.

Prevention after the repair

Once the program works:

• Keep the original application installer and its prerequisite installers.
• Do not remove older Visual C++ redistributables simply because newer generations are installed.
• On 64-bit Windows, retain both x86 and x64 packages when older applications use both architectures.
• Allow game launchers and application installers to complete before restarting or shutting down.
• Review antivirus quarantine before deleting a runtime component.
• Avoid registry cleaners and DLL repair utilities that offer unrelated replacement files.
• Do not copy DLLs between System32, SysWOW64, and application directories.
• Record the full error path when reporting the problem.
• Keep the affected program’s installer or launcher available for repair.

FAQ

Is mfc100chs.dll a Windows system file?

It is a Microsoft runtime component, but it is not guaranteed to be present on every clean Windows installation. It may be installed by Visual C++ 2010 or bundled beside an application.

Does chs mean the file is suspicious?

No. chs is consistent with Microsoft’s Simplified Chinese MFC resource set. The suffix identifies language resources, not malware.

Do I need Visual C++ 2010 or the latest Visual C++ package?

You generally need the Visual C++ 2010 generation for mfc100chs.dll. The modern 2015–2022 redistributable does not generally replace older Visual C++ 2010 files.

Should I install x86, x64, or both?

Install the package matching the application. On 64-bit Windows, installing both x86 and x64 is usually the safest approach when the application architecture is unknown or several older programs are affected.

Why is the file in SysWOW64?

On 64-bit Windows, SysWOW64 normally contains 32-bit system binaries used by 32-bit applications. Do not move the file manually.

Why does the file exist but Windows still say it is missing?

The file may be the wrong architecture, corrupted, blocked, or unable to load a dependency. An incorrect application-folder copy may also be taking precedence over a valid system copy.

Can I download just mfc100chs.dll?

Do not download it from a random DLL website. Use the official Microsoft redistributable or the original application installer.

Will regsvr32 fix it?

Usually no. This file is a runtime language-resource DLL, not a component that should normally be registered manually.

Will SFC restore it?

Not necessarily. mfc100chs.dll usually belongs to a Visual C++ redistributable or application installation, so SFC can report a healthy Windows component store while the runtime remains missing.

Is the file malware if antivirus quarantined it?

Not automatically. Check the detection path, source, signature, and detection name. Reinstall the official package rather than restoring an unverified copy.

What should I tell support?

Provide the application name and version, Windows version, the complete error text, the full path shown for mfc100chs.dll, whether one or several programs fail, whether the program is 32-bit or 64-bit, and what happened immediately before the error appeared.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.