You may see one of these messages when starting an old application, hardware utility, installer, or game:

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

This application failed to start because MFC42ENU.dll was not found.
Re-installing the application may fix this problem.

Error loading MFC42ENU.dll.
The specified module could not be found.

The code execution cannot proceed because MFC42ENU.dll was not found.

The filename may also appear in a message saying that the DLL is corrupted, incompatible, or “not designed to run on Windows.” The wording varies by Windows version and by the program that attempted to load it.

As an Amazon Associate I earn from qualifying purchases.

The 60-second answer

mfc42enu.dll is a genuine old Microsoft file from the Visual C++ and Microsoft Foundation Classes ecosystem. It is generally a 32-bit, English-language, resource-only DLL used by legacy MFC applications for dialogs, strings, and other interface resources. It is not the main MFC code library.

The safest repair is to identify the program showing the error and repair or reinstall that program from its original installer or the software publisher’s official media. Do not begin by downloading a random copy of mfc42enu.dll and placing it in System32 or SysWOW64.

Current Visual C++ Redistributable packages are designed for newer Visual Studio generations and are not a guaranteed source for this Visual C++ 5.0/6.0-era MFC resource file. Even when installing a current redistributable is appropriate for another dependency, it may leave this particular error unchanged. Microsoft’s current package guidance is available on the latest supported Visual C++ Redistributable downloads page.

What mfc42enu.dll actually is

The name breaks down into several useful clues:

• MFC means Microsoft Foundation Classes.
• 42 identifies the old MFC 4.2-era runtime family commonly associated with Visual C++ 5.0 and 6.0 applications.
• ENU means English, United States.
• .dll means Dynamic Link Library.

Microsoft documents MFC language files as resource-only DLLs. They contain localized menus, dialogs, strings, icons, and other interface resources that an MFC application can load separately from its executable code. See Microsoft’s documentation on localization of MFC components and localized resources in MFC applications.

That distinction matters. mfc42enu.dll is not interchangeable with the main MFC runtime files:

• MFC42.DLL is the older ANSI or multibyte MFC implementation.
• MFC42U.DLL is the Unicode MFC implementation.
• MFC42ENU.DLL supplies English-language MFC resources.
• MFC42LOC.DLL is a conventional installed name used for an MFC localized resource DLL.

A program may need the resource file alongside one of the main MFC libraries. Replacing the missing resource DLL with MFC42.DLL, MFC42U.DLL, a modern MFC140*.DLL, or an arbitrary similarly named file does not create a compatible substitute.

Is it a Windows system file?

Not in the sense that every current Windows installation must contain it.

The file belongs to the old Microsoft Visual C++ and MFC ecosystem. It may have been installed by:

• A Visual C++ 5.0 or 6.0 application.
• A Visual Basic 6 application or setup package.
• Microsoft Office or an Access Runtime component.
• A phone, printer, scanner, motherboard, or other hardware utility.
• A legacy game or desktop program built with MFC.
• A vendor installer that bundled its own copy of the old MFC files.

The immediate owner is therefore usually an application, not Windows itself. A missing mfc42enu.dll message tells you which dependency failed, but it does not automatically tell you which program originally supplied the file.

Is it malware?

The file is legitimate Microsoft software, but the filename alone does not prove that a particular copy is authentic.

A genuine copy should normally be associated with a trusted application installation or known Microsoft software media. Examine:

• The full path of the file.
• The program that loads it.
• The file’s digital signature, if present.
• The installer or vendor source from which it came.
• Whether the file appeared after an antivirus quarantine or cleanup event.

A copy in an old program’s installation directory can be normal. A copy with no identifiable owner in an unusual temporary or user-profile directory deserves more investigation. Conversely, the absence of a signature does not by itself prove that a legacy file is malicious.

Why the error appears

The most common cause is an incomplete or damaged installation of the application that needs the file. Other causes are possible, but they should be investigated in order.

1. The legacy program did not install completely

An installer may have failed while copying files, been interrupted, lacked permission to write to its destination, or removed a file during an upgrade.

This is especially common with old software being installed on a newer Windows version. The program may launch far enough to request its MFC resources, then stop when the file is missing.

2. Antivirus or cleanup software removed it

Security software may quarantine a legacy DLL if it has suspicious characteristics, is packed inside an old installer, or is detected because the program around it is unwanted.

A system-cleanup utility may also remove files that look unused, particularly when the application is no longer registered correctly.

3. The wrong file was installed

A 32-bit application needs the matching 32-bit MFC files. Copying a similarly named Unicode, localized, newer, or 64-bit file does not solve the compatibility problem.

The matching application installer is the most reliable source because it knows which MFC generation, language resources, and companion files the program expects.

4. A vendor utility was removed incompletely

A device driver may remain installed while its companion control panel, tray utility, or configuration program is partly removed. The remaining startup entry can still try to load mfc42enu.dll.

This is why reinstalling only the driver may not fix an error caused by the vendor’s desktop utility.

5. The program is failing on a dependency

“The specified module could not be found” does not always mean the named DLL itself is absent. Windows can display that message when a dependency required by the named module cannot be loaded. Microsoft documents this general loader behavior in its troubleshooting guidance for module-not-found errors.

The application directory may contain mfc42enu.dll while another required MFC, runtime, or system dependency is missing.

6. An orphaned startup item is calling the file

If the error appears during sign-in even though no application window opens, an old Run entry, scheduled task, or service may still reference a deleted program.

The DLL should not normally be launched as an independent startup application. The entry that calls it should be identified and repaired or removed.

7. Windows component corruption

This is possible, but it is not the default explanation. Windows usually does not protect every application-local legacy MFC file as a system component. SFC and DISM can repair Windows component corruption, but they normally will not reinstall a DLL that belonged to a third-party application.

Fix 1: Repair or reinstall the program named in the error

This is the highest-probability fix.

Step 1: Identify the affected program

Look for the program name in:

• The title bar of the error dialog.
• The application shortcut you just opened.
• The installer that was running.
• Task Manager’s process list.
• A vendor name shown in the file path.
• An application that starts automatically at login.

If the error appears when opening a shortcut, right-click the shortcut, choose Properties, and inspect the Target field. The program path often reveals whether the owner is an old game, Office component, hardware utility, or business application.

If the message appears during startup, note the time and look for a recently removed or upgraded program.

Step 2: Use Windows’ built-in Repair option

On Windows 11:

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

Some desktop programs instead expose repair through Control Panel:

1. Press Start and search for Control Panel.
2. Open Programs.
3. Select Programs and Features.
4. Right-click the affected program.
5. Choose Repair or Change.
6. Follow the installer’s repair wizard.

The exact buttons depend on how the program was packaged. If no Repair option exists, proceed to a clean reinstall.

Step 3: Reinstall from a trusted source

Use, in order of preference:

• The original CD, DVD, or archived installer you own.
• The publisher’s official download.
• The application’s own maintenance or setup program.
• An official enterprise or hardware-vendor deployment package.

Before uninstalling, back up application data, saved games, profiles, license files, and configuration folders. Old applications sometimes store data outside the standard Documents directory.

Then:

1. Uninstall the affected program from Settings > Apps > Installed apps, or from Control Panel > Programs and Features.
2. Restart Windows.
3. Temporarily close other installers and applications.
4. Run the trusted installer as an administrator if the vendor instructs you to do so.
5. Complete the installation.
6. Restart again.
7. Launch the program from its normal shortcut.

If the installer offers optional components, do not skip the application’s MFC, runtime, language, or support files.

Step 4: Check what the installer contains

If you can browse the original installation media, search it for:

MFC42ENU.DLL
MFC42.DLL
MFC42U.DLL

A Visual Basic 6, Visual C++ 6.0, Office, Access Runtime, or third-party installer may contain these files under an OS\SYSTEM, SYSTEM, Redist, Support, or application directory.

Do not copy files blindly just because their names match. The installer may rename a localized resource DLL during setup, or it may place it beside the program rather than in a Windows directory. Let the original setup program determine the destination whenever possible.

How to tell this fix worked

The repair succeeded if:

• The program opens without the error.
• Its menus and dialogs display normally.
• The error does not return after restarting Windows.
• The program’s installation folder contains the expected MFC files.
• Other programs were not affected by the repair.

If the same message returns immediately, the installer may be damaged, blocked by security software, missing permissions, or incompatible with the current Windows environment.

Fix 2: Check Windows Security quarantine

If the file existed before and disappeared after a scan, update, cleanup, or application crash, check quarantine before downloading anything.

Restore a trusted file

In Windows Security:

1. Open Start.
2. Search for Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Expand the detection associated with the application.
7. Review the detected file path and threat details.
8. Choose Actions.
9. Select Restore only if the file came from a trusted, intact installer and you have verified the application.

Microsoft’s Protection History guidance explains this process and warns that restoring a genuinely malicious file can put the system at risk.

Do not restore a file merely because its name is mfc42enu.dll. Verify the original path and source first. If the file came from a questionable installer, leave it quarantined and reinstall the application from a trusted source.

If the file was removed by third-party antivirus software

Open that product’s quarantine or history panel and inspect:

• The detected path.
• The detection name.
• The publisher.
• Whether the file was inside a known application folder.
• Whether the installer itself was downloaded from the official vendor.

If you cannot establish that the file is legitimate, reinstall the application instead of restoring the quarantined copy.

Run a full scan

After resolving the application:

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

A missing DLL does not prove malware, but an unexplained file removal combined with unfamiliar startup items should be investigated.

Fix 3: Do not assume the current Visual C++ Redistributable contains it

This is where many DLL guides send users in the wrong direction.

The current Microsoft Visual C++ Redistributable packages are named:

VC_redist.x86.exe
VC_redist.x64.exe
VC_redist.arm64.exe

They support newer Visual Studio generations. Microsoft’s current redistributable page does not provide a complete Visual C++ 6.0-era catalog, and installing a current package is not a guaranteed way to obtain mfc42enu.dll.

For modern applications:

• A 32-bit program generally needs the x86 package.
• A 64-bit program generally needs the x64 package.
• Some computers need both because they run both 32-bit and 64-bit applications.

For this particular file, however, the commonly identified mfc42enu.dll is an old x86 MFC resource file. A 64-bit package is not a substitute for it. Microsoft’s MFC redistribution guidance also emphasizes that applications need matching MFC versions and architectures.

If the affected program is modern and also reports a different runtime such as MSVCP140.dll or VCRUNTIME140.dll, install the appropriate current Microsoft package from the official page. That may repair the modern dependency while leaving the separate mfc42enu.dll issue to the legacy application’s installer.

Older Visual C++ redistribution packages also did not necessarily include localized MFC satellite files. That is another reason the affected program’s original installer remains the authoritative repair source.

Fix 4: Install pending Windows updates

Windows Update will not normally supply an application-local Visual C++ 6.0-era resource DLL, but keeping Windows current can repair loader, servicing, and compatibility issues around the application.

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install available updates.
6. Restart the computer.
7. Test the affected program again.

Microsoft documents this process in its Windows Update installation instructions.

Do not treat an error-free Windows Update scan as proof that the application file is present. The update process and the legacy application have separate file ownership.

Fix 5: Repair Windows components with DISM and SFC

Use DISM and SFC when you have additional evidence of Windows corruption, such as broken built-in applications, repeated servicing errors, damaged system files, or several unrelated Windows features failing.

They are not the first repair for an isolated application-local mfc42enu.dll error.

Run DISM first

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for it to complete. It may remain at one percentage for a while.

If DISM reports that repair files cannot be found and you have a valid matching Windows installation source, Microsoft documents this form:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace C:\RepairSource\Windows with the actual path to a matching repair source. Do not use an arbitrary folder.

Run SFC second

In the same elevated Command Prompt, run:

sfc /scannow

Restart Windows after the scan finishes and test the affected program.

Typical outcomes include:

• Windows Resource Protection did not find any integrity violations: Windows did not detect a repairable protected-system-file problem.
• Windows Resource Protection found corrupt files and successfully repaired them: restart and test again.
• Windows Resource Protection found corrupt files but was unable to fix some of them: review the result, repair the Windows image with DISM, and run SFC again if appropriate.

Microsoft’s instructions for using System File Checker and repairing Windows components should be followed for the exact output on your system.

If SFC reports no problems and the application still cannot find mfc42enu.dll, that is expected evidence that the file belongs to the application rather than to the protected Windows component store.

When manually comparing DISM and SFC results or repeating repairs, it is easy to lose track of what changed. Outbyte PC Repair can scan for system issues and show what it identifies, while the repair action is performed by the full version; it is optional, and reinstalling the affected program remains the definitive fix when the missing file belongs to that application.

Fix 6: Reinstall a hardware utility, not just its driver

If the message appears when opening a printer panel, motherboard utility, phone suite, scanner tool, audio console, or other device program, the DLL may belong to the companion utility rather than the driver itself.

Check the device in Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters, Sound, video and game controllers, Printers, Universal Serial Bus controllers, or Network adapters.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Record the provider, date, and version.
8. Use the vendor’s official support package if a driver update is required.

Do not use Device Manager’s generic search as the only repair method for a missing application DLL. Device Manager may update the hardware driver while leaving the vendor’s old configuration utility untouched.

Instead:

1. Uninstall the vendor utility from Settings > Apps > Installed apps.
2. Restart Windows.
3. Download the complete device software package from the hardware manufacturer.
4. Install the utility and driver components together when the installer offers that choice.
5. Restart again.
6. Open the vendor application.

If the error belongs to a device utility, reinstalling the driver alone may not restore mfc42enu.dll.

When a system has many devices and it is difficult to determine which driver package is stale, Outbyte Driver Updater can scan and identify driver issues, while the actual driver installation is handled by the full version; it is optional, and it will not replace the need to reinstall the application that owns mfc42enu.dll.

Fix 7: Investigate an orphaned startup entry

If the message appears immediately after login and no visible program is open, locate the startup item that calls the old application.

Microsoft’s Autoruns utility can show Run entries, scheduled tasks, services, shell extensions, and other automatic launch points.

Use it carefully:

1. Download Autoruns from Microsoft Sysinternals.
2. Extract the archive.
3. Run the version appropriate for your Windows installation.
4. Approve administrator access.
5. Select the Everything tab.
6. Use Find and search for mfc42enu.dll.
7. Inspect the image path, publisher, and parent application.
8. Record or export the entry before changing it.
9. If the program was removed and the entry is obsolete, clear the entry or disable it.
10. Restart Windows and check whether the message is gone.

Do not disable an entry solely because it contains a DLL. Determine which executable loads the DLL and whether that software is still installed.

A startup entry that directly references mfc42enu.dll, especially from a temporary or unusual directory, should be treated as a possible malware or cleanup-remnant issue. Run a full security scan and investigate the parent executable.

Fix 8: Handle dependency and path errors

An error saying “The specified module could not be found” can mean that mfc42enu.dll is present but cannot load one of its own dependencies.

Check the affected application directory for the related MFC files:

MFC42.DLL
MFC42U.DLL
MFC42ENU.DLL

Their presence alone is not enough. They must belong to the correct application and MFC generation.

Useful searches include:

where /r C:\ mfc42enu.dll

This may take a long time on a large drive.

PowerShell provides another method:

Get-ChildItem -Path C:\ -Filter mfc42enu.dll -Recurse -ErrorAction SilentlyContinue

If you find several copies, record their full paths rather than choosing the newest-looking one. The copy beside the affected application may be the correct one, while a copy in another program’s directory may be incompatible.

To calculate a file hash:

Get-FileHash "C:\path\to\MFC42ENU.DLL" -Algorithm SHA256

A hash is useful when comparing a file with a trusted installer or known-good backup. It is not, by itself, proof that a DLL is safe.

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

Where should the file go?

Do not automatically place it in:

C:\Windows\System32

or:

C:\Windows\SysWOW64

On 64-bit Windows, those directory names do not mean what many users expect. System32 is primarily used for 64-bit system files, while SysWOW64 contains 32-bit system files. That naming is not a safe instruction for manually installing a legacy application DLL.

Application-local deployment is generally safer because the program can load the file from its own directory without changing shared system components. Microsoft documents the Windows DLL search order, including the importance of the application directory.

Only recover a file manually when it came from the application’s trusted installer, original media, or a verified backup, and when the application’s deployment structure clearly indicates the destination. Back up any existing file before replacing it.

Do not use regsvr32 for this file

regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer. A resource-only MFC language DLL normally does not need COM registration.

Running:

regsvr32 "C:\path\to\MFC42ENU.DLL"

may produce an error such as:

The module was loaded but the entry-point DllRegisterServer was not found.

That does not mean you need another version of regsvr32. It means the DLL is not a registerable COM or ActiveX component. Microsoft’s explanation of DLL registration and the required entry point covers this distinction.

Do not register the file merely because its extension is .dll.

Windows Features, DirectX, and .NET are usually unrelated

Turning Windows Features on and off will not normally install this old MFC language resource. Do not enable random components such as legacy .NET Framework features, SMB options, or media features in the hope that one will create mfc42enu.dll.

DirectX installers are also not established sources for this file. DirectX errors usually involve DirectX components with names such as d3dx9_35.dll, not MFC42 language resources. Microsoft’s DirectX installation guidance is useful when the error actually names a DirectX file.

Avoid random DLL download websites

Do not download mfc42enu.dll from an arbitrary DLL repository and copy it into a Windows directory.

That approach can fail because:

• The file may be malicious or modified.
• The version may belong to a different MFC generation.
• The architecture may be wrong.
• The language resource may not match the application.
• The file may require other missing dependencies.
• A shared system copy can break another application.
• The original problem may be a damaged installer or orphaned startup entry.

The safe sources are:

• The affected application’s original installer.
• The official software publisher’s installer.
• Trusted Microsoft installation media when the file is clearly part of that package.
• A verified backup from the same application installation.

Microsoft does not currently provide a verified standalone download page specifically for mfc42enu.dll.

Fix 9: Use System Restore only after identifying the change

System Restore can help if a suitable restore point was created before the file disappeared. It will not help if no restore point predates the problem.

To open it:

1. Open Control Panel.
2. Select Recovery.
3. Select Open System Restore.

Alternatively:

1. Press Win + R.
2. Enter:

rstrui.exe

1. Press Enter.

Then:

1. Select a restore point from before the error began.
2. Select Scan for affected programs.
3. Review the applications and drivers that will be changed.
4. Confirm the restore only if the impact is acceptable.
5. Allow Windows to restart.
6. Test the affected application.

Microsoft documents the process in its System Restore instructions.

System Restore is more appropriate when an update, cleanup operation, or software removal clearly caused the problem. It is not a substitute for reinstalling a damaged legacy application when a known-good installer is available.

32-bit applications on 64-bit Windows

The commonly identified mfc42enu.dll is an x86 file. An old 32-bit application can run on 64-bit Windows through WOW64, but that does not make the application a 64-bit program or create a 64-bit version of this resource DLL.

The important rule is:

• Match the file and runtime to the application that loads it.
• Do not infer the destination from System32 or SysWOW64.
• Do not replace an x86 MFC file with an x64 DLL.
• Do not assume a modern x64 Visual C++ package supplies an old x86 MFC resource.

Some very old applications may also require compatibility settings, older installers, or a supported 32-bit environment after the missing file is restored. If the DLL error disappears but the program still fails, the remaining problem may be application compatibility rather than the MFC file itself.

If reinstalling does not restore the file

Check these areas before trying random replacements:

Installer logs

Look for setup logs in the application directory, %TEMP%, or the installer’s support folder. Search for:

MFC42ENU.DLL
access denied
file in use
rollback
failed

Permissions

Run the installer again using an administrator account if the publisher requires it. Confirm that the destination drive is writable and that security software is not blocking the setup process.

Disk space

An installer that runs out of space can leave an incomplete directory that looks installed but lacks support files.

Endpoint-security blocks

Check Windows Security and any third-party antivirus history while running the installer. A setup that repeatedly loses the same file may be blocked during installation.

Damaged installation media

If the installer is on an old disc, archive, network share, or compressed package, obtain a fresh copy from the publisher or verify the original media.

Wrong application owner

A reinstall will not help if you are repairing the wrong program. Confirm the executable path, startup entry, or installer that requests the DLL.

Frequently asked questions

Is mfc42enu.dll part of Visual C++?

Yes. It is associated with the old Microsoft Visual C++ and MFC ecosystem. It is a language-specific, resource-only MFC DLL rather than the main MFC implementation library.

Is it part of Visual Basic 6?

It may be included with Visual Basic 6 setup media or applications built with that toolchain, but it is not exclusive to Visual Basic. Other legacy Visual C++ applications, Office components, hardware utilities, and third-party software may bundle it.

Do I need the current Visual C++ Redistributable?

Not necessarily. Current redistributables target newer Visual Studio generations and are not a guaranteed source for this old MFC resource file. Install a current package only when the application or another error specifically requires that runtime, and use the application’s original installer for mfc42enu.dll.

Should I install both x86 and x64 redistributables?

Modern software sometimes needs both because 32-bit and 64-bit programs use different runtime packages. For this file, the commonly identified version is x86, so installing an x64 package does not substitute for the required legacy resource.

Should I copy the file into System32?

No. Do not use System32 or SysWOW64 as generic DLL drop locations. Repair the application and let its installer select the correct location.

Should I copy it beside the application?

Only when the file comes from that application’s trusted installer, original media, or verified backup and the program’s deployment structure clearly expects an application-local copy. Do not use a random download or a copy from an unrelated program.

Should I run regsvr32?

No. A resource-only MFC DLL is not normally a COM or ActiveX control and does not need registration.

Why does SFC say everything is fine?

SFC checks protected Windows system files. It may report no problems when an application-local legacy DLL is missing. That result does not repair or disprove an absent mfc42enu.dll.

Why does the error appear when no program is open?

An old startup entry, scheduled task, service, or vendor utility may be trying to launch after sign-in. Use Autoruns to identify the parent program and disable only an entry you have confirmed is obsolete or unwanted.

Is a “not designed to run on Windows” message proof that the file is fake?

No. It can indicate corruption, an incompatible binary, or a wrong architecture. Verify the file’s source, path, and relationship to the application before replacing it.

Can Windows Update fix it?

Windows Update can improve general compatibility and repair Windows components, but it is not a dependable source for an application-local Visual C++ 6.0-era language DLL.

What information should I provide when asking for help?

Include:

• The complete error text.
• The program or installer that displays it.
• Your Windows edition and version.
• Whether Windows is 32-bit or 64-bit.
• The full path named in the error.
• Whether the problem began after an update, reinstall, cleanup, antivirus detection, or migration.
• Whether MFC42.DLL and MFC42U.DLL are beside the program.
• Whether searches found another copy of mfc42enu.dll.
• What Repair, reinstall, Windows Security, SFC, and DISM reported.

The most useful starting point is still the application named in the error. Once that owner is identified, the correct installer usually matters more than any generic DLL 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.