mfc42chs.dll Not Found: Trace the App and Repair It Safely

mfc42chs.dll is a legitimate Microsoft Foundation Classes localization file for Simplified Chinese, usually used by older Visual C++ 6.0 or Visual Basic 6-era applications. If mfc42chs.dll is missing, the safest fix is normally to repair or reinstall the specific application that reports the error.

Do not begin by downloading a replacement DLL, copying files into both Windows system directories, or running regsvr32. This file is generally supplied by the application installer rather than restored by modern Windows Update.

As an Amazon Associate I earn from qualifying purchases.

What mfc42chs.dll is

The file’s description is MFC Language Specific Resources. The CHS suffix refers to Chinese Simplified, also called Simplified Chinese.

It is a resource-only Microsoft Foundation Classes DLL. In practical terms, it contains localized menus, dialogs, messages, and other language resources used by an older Windows application. It is not normally a standalone program, Windows service, device driver, or executable.

Microsoft’s Visual Basic 6 support policy identifies localization binaries such as this as application-supplied files rather than guaranteed current Windows components. Microsoft also documents that localized MFC resource files were supplied with Visual C++ product media and were not automatically installed with every Visual C++ runtime installation.

Item	What it means
File	mfc42chs.dll
Description	MFC Language Specific Resources
Publisher family	Microsoft Visual C++ and Microsoft Foundation Classes
Language	CHS, or Simplified Chinese
Typical software era	Visual C++ 6.0 and Visual Basic 6.0-era applications
Architecture	32-bit legacy component
Current Windows status	Not a guaranteed Windows-shipped component
Universal current version	Not published by Microsoft
Correct owner	Usually the application that needs it

A historical file inventory may show a particular version or file size, but those records do not establish one universal version for every application. Different installers can contain different builds, and the correct copy is the one intended for the affected program.

Microsoft’s Visual Basic 6 support policy explains the supported runtime environment and the 32-bit nature of VB6 components.

What the error usually means

You may see one of these messages:

• “The program can’t start because mfc42chs.dll is missing from your computer. Try reinstalling the program to fix this problem.”
• “mfc42chs.dll was not found.”
• “The code execution cannot proceed because mfc42chs.dll was not found.”
• “Error loading mfc42chs.dll. The specified module could not be found.”
• “mfc42chs.dll is either not designed to run on Windows or it contains an error.”
• “The procedure entry point could not be located in the dynamic link library mfc42chs.dll.”

The first three messages usually mean that the application cannot locate the file it expects. The final three can indicate a damaged file, an incompatible build, an architecture mismatch, or a missing dependency.

A file can exist on disk while Windows still reports that it could not be found. In that situation, the named DLL may be present but one of the DLLs it depends on cannot load.

Microsoft’s general guidance for missing application DLL errors is to reinstall the affected program. See Microsoft’s example of a missing-DLL application error.

First, identify which application needs it

The filename alone cannot identify the application. Several unrelated legacy programs can use the same Microsoft runtime resources.

Before changing Windows, record the program name and the complete error text.

Check the shortcut

1. Right-click the shortcut that produces the error.
2. Select Properties.
3. On the Shortcut tab, inspect Target.
4. Note the program name and installation folder.
5. Select Open File Location if that button is available.
6. Look for the application’s main .exe file and any nearby mfc42*.dll files.

If the shortcut points to a launcher, repeat the process for the actual application executable if you can locate it.

Check installed applications

On Windows 11:

1. Open Start.
2. Select Settings.
3. Choose Apps.
4. Select Installed apps.
5. Search for the program that fails.
6. Open its three-dot menu and choose Advanced options if available.

On Windows 10:

1. Open Start.
2. Select Settings.
3. Choose Apps.
4. Select Apps & features.
5. Search for the affected program.

Desktop programs may instead appear in Control Panel:

1. Press Win+R.
2. Enter appwiz.cpl.
3. Press Enter.
4. Find the application in Programs and Features.
5. Note its exact name and publisher.

The installation path matters. A file beside the application may be correct even when the same filename in a Windows system directory is not.

Fix 1: Repair the affected application

This is the best first repair when only one application fails.

Repair through Windows Settings

On Windows 11:

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

If the program opens, the repair restored the required files. If it still fails, return to the same screen and use Reset only if you understand that it may remove the program’s settings or local data.

Windows 10 may show a Repair button directly under the application entry. Use it if present.

Repair through Control Panel

For a traditional desktop program:

1. Press Win+R.
2. Enter appwiz.cpl.
3. Press Enter.
4. Right-click the affected program.
5. Choose Repair or Change.
6. Follow the installer prompts.
7. Select any language, Chinese, runtime, or optional component related to the program.
8. Restart Windows if the installer requests it.
9. Test the application.

The exact menu depends on the vendor’s installer. Some programs provide only Change, which may open a maintenance wizard containing Repair.

Reinstall from original media

If repair is unavailable or fails:

1. Back up the application’s documents and configuration files.
2. Obtain the original installer, installation disc, vendor download, or managed deployment package.
3. Uninstall the affected application from Settings or Programs and Features.
4. Restart Windows if requested.
5. Run the original installer as an administrator.
6. Install the same language and optional components used previously.
7. Start the application before adding unrelated updates or plug-ins.

If the reinstall restores mfc42chs.dll beside the application and the program starts, the problem was an incomplete, damaged, or altered application installation.

Do not assume that reinstalling Windows is necessary because one legacy application lost a file. The application installer is normally the correct source.

Fix 2: Check Windows Security quarantine

Older DLLs are sometimes quarantined because they are uncommon, unsigned, packed with an old installer, or located in a directory associated with legacy software. Quarantine is particularly likely after a security scan, application update, cleanup utility, or interrupted installation.

Inspect Protection History

1. Open Start.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Choose Protection history.
6. Expand detections related to the application.
7. Inspect the original file path and detection details.

Do not restore the file merely because its name resembles a Microsoft filename. A Microsoft-style name does not prove that a particular copy is genuine.

Restore or allow the file only when all of the following are true:

• The application is legitimate and expected on the computer.
• The file was located in the application’s original installation directory.
• The application came from trusted vendor media.
• The detection appears to be a false positive or a quarantine event caused by the installation.
• You can repair or reinstall the application immediately afterward.

If the file came from an unknown source, a suspicious archive, or a directory you do not recognize, leave it quarantined. Remove the suspicious software and reinstall the legitimate application from clean media.

Microsoft’s Protection History instructions explain how to review and manage Windows Security detections.

Fix 3: Check whether the program is 32-bit

Legacy Visual C++ and Visual Basic 6 applications are normally 32-bit. Microsoft states that VB6 runtime components remain 32-bit and run under WOW64 on 64-bit Windows.

A 32-bit program needs 32-bit dependencies. A 64-bit program cannot load a 32-bit DLL, and a 32-bit program cannot load a 64-bit DLL.

How to identify the application architecture

The age of the application is a useful clue, but it is not proof. To investigate:

1. Open the application’s installation folder.
2. Right-click the main .exe file.
3. Select Properties.
4. Open the Details tab and record the product information.
5. Check the vendor’s documentation for architecture information.

For a more technical check, use Microsoft’s development or diagnostic tools if they are already installed, or ask the vendor which architecture the program requires.

Do not replace mfc42chs.dll with:

• mfc42.dll
• mfc42u.dll
• mfc42cht.dll
• mfc42loc.dll
• mfc80 or mfc90 localization files
• A 64-bit DLL with a similar name

mfc42cht.dll is associated with Traditional Chinese resources, not Simplified Chinese. A similarly named file may belong to a different MFC generation or language.

Do not copy blindly into System32 and SysWOW64

On 64-bit Windows, System32 is the native system directory and SysWOW64 is used for redirected 32-bit system components. The names are confusing, and copying a random DLL into both locations can create further conflicts.

Microsoft documents these rules in its file-system redirector guidance.

For a private application installation, the correct destination is often the application directory, but only the original installer or vendor documentation can establish that for a particular program.

Fix 4: Restore the file from the application installer

Manual copying is acceptable only when the source is trustworthy and the destination is known.

Appropriate sources include:

• The original application installer.
• Original Microsoft development media used by the application vendor.
• A vendor-provided repair package.
• A known-good backup of the same application installation.

Before copying, confirm:

1. The file is intended for the affected application.
2. It is the correct 32-bit architecture.
3. It matches the application’s MFC generation and language.
4. The file came from trusted media.
5. The vendor’s instructions specify the destination.
6. Windows Security has not flagged the source.

If those conditions are met, copy the file beside the application executable or into the vendor-designated private runtime directory. Then start the application again.

Do not overwrite a working system-wide MFC file to repair one program. Do not place an unknown copy in both System32 and SysWOW64.

Microsoft provides guidance for redistributing MFC libraries with applications, including application-local deployment.

Fix 5: Do not assume the Visual C++ redistributable is the answer

mfc42chs.dll belongs to the older Visual C++ 6 and MFC 4.2-era ecosystem. It is not the same component as modern files such as vcruntime140.dll or msvcp140.dll.

The historical Visual C++ 6 redistributable installs core files such as mfc42.dll and mfc42u.dll, but Microsoft’s documentation states that it does not install localized satellite DLLs. That means installing the ordinary VC6 redistributable is not a definitive repair for a missing mfc42chs.dll.

The current Microsoft Visual C++ redistributable page explains package architectures and side-by-side runtime behavior. Installing the current x64 package, x86 package, or both may repair a modern application that needs a current Visual C++ runtime, but it does not recreate every VC6-era localization file.

If the application installer includes its own prerequisites, use those prerequisites first. They are more likely to match the program’s expected files.

Fix 6: Do not treat the VB6 runtime as a guaranteed repair

Microsoft’s historical Visual Basic 6 SP6 runtime package is called VB6.0-KB290887-X86.exe and contains vbrun60sp6.exe. Its primary purpose is the base VB6 runtime, including components such as msvbvm60.dll.

Installing it may be appropriate when the application vendor specifically requires the VB6 runtime, but it should not be presented as a guaranteed way to install mfc42chs.dll. Microsoft classifies this localization file separately and expects the application setup to provide it.

The official historical package is available through Microsoft’s Visual Basic 6.0 Service Pack 6 download page.

Microsoft also publishes separate VB6 SP6 security and cumulative updates:

• Visual Basic 6 SP6 security rollup
• Visual Basic 6 SP6 cumulative update
• VB6 runtime extended-file documentation

Those packages update supported VB6 runtime and ActiveX components. Their published manifests do not establish that they install mfc42chs.dll.

Fix 7: Repair Windows components only when other Windows files are failing

Because mfc42chs.dll is generally application-distributed, SFC and DISM should not be your first response to an isolated error from one old program.

Use them when several Windows components are also damaged, built-in applications fail, Windows features behave incorrectly, or the problem affects more than one unrelated program.

Run DISM

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the operation to finish.
2. Leave the elevated Command Prompt open.

Run SFC

After DISM completes, enter:

sfc /scannow

Wait until verification reaches 100 percent. Then restart Windows and test the application.

Success means that Windows reports no integrity violations or that it repaired protected Windows files. It does not prove that the application-owned mfc42chs.dll has been restored.

If SFC reports that it could not repair some files, save the exact message and investigate broader Windows corruption. Do not repeatedly run the same commands without recording what changed.

When manually hunting through logs, comparing repair results, and repeating SFC or DISM is taking time without identifying the damaged component, Outbyte PC Repair can scan for problems and show what it found; repairs are performed by the full version, and it is optional. If the missing file belongs to one specific legacy application, repairing or reinstalling that application remains the definitive fix.

Microsoft’s System File Checker guidance covers the recommended DISM-then-SFC sequence.

Fix 8: Use System Restore after a recent change

System Restore can help when the application worked immediately before a cleanup program, driver installation, Windows change, or other system modification.

It is more useful when:

• A restore point exists from before the failure.
• The application worked before that point.
• The problem began directly after a system change.
• Other programs or settings changed at the same time.

Start System Restore

1. Press Win+R.
2. Enter:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point from before the error began.
4. Select Scan for affected programs if available.
5. Review the programs and drivers that may be changed.
6. Select Close to return to the restore-point list.
7. Select Next.
8. Confirm the restore.

System Restore does not normally replace personal documents, but it can remove applications, drivers, and updates installed after the selected restore point. Microsoft explains the process in its System Restore instructions.

If the application still fails afterward, repair or reinstall it from its original media.

Fix 9: Investigate a missing dependency

If the file exists but the error says “The specified module could not be found,” the problem may be a dependency rather than mfc42chs.dll itself.

Check the following:

• The file is in the application’s expected directory.
• The file is not zero bytes or obviously damaged.
• The application is using the intended installation folder.
• The required mfc42.dll or mfc42u.dll files are present if the application installer expects them.
• Required C runtime files are present.
• Antivirus has not blocked another DLL.
• The application has not been partially moved to another drive.
• The file and its dependencies match the same legacy application build.

A dependency failure can occur when one file was copied without the rest of the application runtime. Reinstalling the complete application is safer than assembling individual DLLs.

Fix 10: Consider a driver only when the evidence points to one

mfc42chs.dll is not a device driver, so Device Manager is not normally involved. Do not update every driver simply because an old application displays a DLL error.

Check Device Manager only when the application also reports hardware, display, audio, printer, scanner, USB, or virtual-device failures.

Inspect Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand the hardware category related to the application.
4. Look for a yellow warning icon.
5. Right-click the affected device.
6. Select Properties.
7. Open the General tab and read the device status.
8. Open the Driver tab to inspect the provider and date.
9. Use Update Driver only when the hardware vendor or application vendor supports that driver.

Do not replace a DLL with a driver update. Resolve the application runtime problem separately.

When identifying which of many hardware drivers is actually stale is the difficult part, Outbyte Driver Updater can scan and identify driver updates; installation is handled by the full version, and it is optional. A driver update will not replace an application-owned mfc42chs.dll unless the evidence shows that a separate hardware problem is preventing the application from starting.

Windows Features are usually not the fix

Turning on random Windows Features does not restore mfc42chs.dll.

To inspect available optional components:

1. Press Win+R.
2. Enter:

optionalfeatures

1. Press Enter.
2. Review the list of Windows Features.
3. Enable a feature only when the application vendor specifically requires it.
4. Select OK and restart if prompted.

Legacy applications sometimes depend on an old .NET version, IIS component, multimedia feature, or ActiveX-related component, but those dependencies are separate from the MFC localization DLL. Do not enable features based only on the filename.

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

What not to do

Do not download the DLL from a random website

Unverified DLL downloads can contain malware, the wrong architecture, the wrong language resource, a mismatched build, or a modified file. Even a genuine-looking file may not fix the missing dependency that caused the error.

Use the original application installer, original vendor media, or a Microsoft package that the application documentation specifically requires.

Do not run regsvr32 on this file

regsvr32 is intended for self-registering COM and OLE DLLs, including certain ActiveX controls. A resource-only MFC localization DLL normally does not export DllRegisterServer.

Running:

regsvr32 mfc42chs.dll

may produce a “not self-registerable” or entry-point error. It does not repair a missing resource file.

Microsoft explains how Regsvr32 works and how to troubleshoot its errors.

Do not rename another MFC file

Renaming mfc42.dll, mfc42u.dll, or a different language file to mfc42chs.dll does not create the required resources. It can also make future repairs harder.

Do not copy the file into both system directories

This can introduce version conflicts and does not account for the application’s private search path. Use the application directory or vendor-specified location instead.

Do not expect Windows Update to restore it

Windows Update may repair current protected Windows components, but it is not expected to restore an application-supplied VC6 localization file.

Do not assume the file is malware-free

The filename resembles a Microsoft component, but any copy can be replaced or planted by malware. Check its path, source, digital signature where available, security history, and the legitimacy of the application.

Windows documents DLL loading behavior in its DLL search order guidance and explains related risks in its DLL security guidance.

When the file exists but the program still will not start

Work through this checklist:

1. Confirm the application executable that is failing.
2. Confirm the exact path of mfc42chs.dll.
3. Check whether the application is 32-bit.
4. Confirm that the file is Simplified Chinese resources, not a Traditional Chinese substitute.
5. Check for missing mfc42.dll or mfc42u.dll files required by the same application.
6. Review Windows Security Protection History.
7. Repair or reinstall the complete application.
8. Check whether the application was moved from its original directory.
9. Look for a second copy of the program installed under another path.
10. Check the full error text for “bad image,” “entry point,” or “specified module.”
11. If only this program fails, avoid global Windows repairs.
12. If many programs fail, investigate broader runtime or system corruption.

Some older MFC deployments also used a system-wide localization file, creating language conflicts when different applications expected different resource languages. That is another reason to avoid replacing system-wide MFC files casually.

If the error started after a game installation

Do not assume that DirectX is responsible. mfc42chs.dll is not a DirectX file.

Use the game launcher’s built-in Verify, Repair, or Verify integrity command first. If the launcher does not contain the file, identify which executable reports the error. The DLL may belong to an included configuration utility, installer, editor, launcher, or older bundled component rather than the game engine.

If the game’s own repair process fails, reinstall the game from its official installer or contact the game vendor. Do not use a generic DLL download as a substitute.

If every old program reports the error

An error from multiple applications may indicate:

• A damaged system-wide legacy MFC installation.
• A cleanup or security product removing shared files.
• Malware or DLL side-loading.
• A damaged Windows installation.
• Multiple applications depending on an unavailable legacy runtime.

Collect the exact application names and file paths before making global changes. Run a full security scan, inspect Protection History, and use DISM and SFC only when other Windows components are also failing.

If the applications depend on obsolete installers, ActiveX controls, or hardware drivers, modern Windows compatibility may remain limited even after the DLL is restored. Microsoft supports VB6 applications as 32-bit programs under WOW64, but the VB6 development environment itself has never had a native 64-bit version. A supported vendor update, isolated legacy installation, or virtual machine may be the practical long-term solution.

Frequently asked questions

Is mfc42chs.dll a Windows system file?

It is a Microsoft runtime resource, but it is not a guaranteed current Windows-shipped component. The application installer is generally expected to provide it.

Is it part of Visual C++ 6.0 or Visual Basic 6.0?

It belongs to the older MFC and Visual C++ runtime ecosystem and can also be used by Visual Basic 6-era applications. The exact application cannot be identified from the filename alone.

Does the CHS suffix matter?

Yes. CHS means Simplified Chinese resources. Do not substitute a Traditional Chinese file or a different MFC localization generation.

Do I need both x86 and x64 Visual C++ packages?

Modern applications may need one or both, depending on their architecture. However, installing current Visual C++ packages does not guarantee that they will recreate the VC6-era mfc42chs.dll. Repair the application that requires the file first.

Will vbrun60sp6.exe fix the problem?

Not necessarily. It provides the base VB6 runtime, but Microsoft treats the localized MFC resource file separately. Use the application installer unless the vendor specifically directs you to install the VB6 runtime.

Will SFC restore mfc42chs.dll?

Usually not. SFC repairs protected Windows files, while this file is generally supplied by an application. Use SFC and DISM when other Windows components are also damaged.

Should I register the file?

Normally no. A resource-only MFC localization DLL is not normally registered with regsvr32.

Where should the file go?

Usually beside the application executable or in another private directory specified by the application vendor. Do not copy an unknown file into both System32 and SysWOW64.

Why does Windows say the file is missing when it is visible?

The file may be in the wrong directory, the application may be loading another copy, or one of its dependencies may be missing or corrupt.

What information should I provide when asking for help?

Include:

• The exact application name and publisher.
• The complete error text.
• The full path shown in the error or installation directory.
• Your Windows version.
• Whether Windows is 32-bit or 64-bit.
• Whether the application is 32-bit.
• Whether the problem began after an update, cleanup, reinstall, or security alert.
• Whether Windows Security quarantined a file.
• Whether the file exists and where it was found.

That information usually identifies whether the next step is application repair, quarantine review, dependency troubleshooting, or broader Windows repair.

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.