msvcrt20.dll Missing: A Safe Repair Path for Legacy Apps

msvcrt20.dll is the Microsoft C Runtime Library used mainly by software built with Microsoft Visual C++ 2.x. If Windows says msvcrt20.dll is missing, was not found, or could not be loaded, repair the application that requested it before changing Windows system files.

The safest fix is usually to identify the exact program, repair or reinstall that program from its original source, and restore the matching legacy runtime from its installer if the program supplied one. Installing the newest Visual C++ package does not automatically install msvcrt20.dll.

As an Amazon Associate I earn from qualifying purchases.

What msvcrt20.dll is

msvcrt20.dll is a native 32-bit Microsoft C runtime library. Microsoft describes the DLL-form runtime with this name as the runtime associated with Visual C++ 2.x. It was distributed with Visual C++ and with applications built using that compiler. Microsoft’s C runtime documentation explains the historical relationship between the Visual C++ compiler versions and their runtime libraries.

It is not:

• A device driver
• A .NET component
• A DirectX file
• The Universal C Runtime
• The same file as msvcrt.dll
• Interchangeable with msvcr100.dll, msvcr120.dll, or vcruntime140.dll

The file is historically associated with Windows 95-era software and other older Win32 applications. Windows 95 included it, and older Windows generations required or shipped it. Some later Windows installations also contained compatibility copies, but you should not assume that Windows 10 or Windows 11 guarantees msvcrt20.dll as a supported built-in component.

That distinction matters. A missing copy may indicate damaged Windows components, but it may also mean that an old application was incompletely installed, that its private runtime was removed, or that the wrong version was placed beside the program.

Before fixing anything: identify the program

1. Read the complete error

Write down:

• The exact filename shown
• The name of the application or game
• Whether the message says “missing,” “not found,” “not compatible,” or “entry point”
• Whether the problem began after an update, cleanup, antivirus detection, or software installation
• Whether the program is installed through Steam, Epic Games, another launcher, a disc, or a standalone installer

A missing-file message and an entry-point error require different investigations.

For example:

• “The program can’t start because msvcrt20.dll is missing” usually points to an incomplete installation, deleted file, or missing application dependency.
• “The procedure entry point could not be located” usually points to the wrong build or a different copy of the DLL replacing the expected one.
• “This version of MSVCRT20.DLL is only intended for Win32s” indicates that a Win32s build was used in the wrong environment.
• “This version of MSVCRT20.DLL is not compatible with Win32s” indicates the opposite mismatch.

Do not begin by copying a replacement into System32. First determine which executable requested the file.

2. Check whether the program is 32-bit

msvcrt20.dll belongs to the historical 32-bit Visual C++ runtime context. The architecture of the affected application matters more than whether Windows itself is 64-bit.

A 32-bit application cannot load a 64-bit DLL, and a 64-bit application cannot load a 32-bit DLL. On 64-bit Windows, System32 normally contains native 64-bit system files, while SysWOW64 contains 32-bit system files. Microsoft’s explanation of 32-bit applications and the File System Redirector documentation describe this layout.

You can often identify the program architecture by checking its documentation or installer. If the program is an old game, utility, Visual Basic application, or Visual C++ application from the Windows 95 era, assume it may be 32-bit until verified.

Fix 1: Repair the affected application

Time needed: 5–15 minutes

This is the best first fix when the error appears after installing, updating, moving, cleaning, or restoring an old program.

Windows may be able to restore the application’s files without removing your settings.

Windows 11

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

Windows 10

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Apps & features.
5. Select the affected application.
6. Select Advanced options, if available.
7. Select Repair.
8. Try the application again.

Some traditional desktop programs do not expose the modern Repair button. For those applications:

1. Open Start.
2. Search for Control Panel and open it.
3. Select Programs.
4. Select Programs and Features.
5. Select the affected program.
6. Choose Repair, Change, or Modify, depending on what the installer provides.
7. Follow the installer prompts.
8. Restart Windows if requested.

What success looks like

The program opens without the msvcrt20.dll message. The repair may also recreate an application-local copy of the runtime beside the program’s executable.

If Repair is unavailable or fails

Uninstall and reinstall the application from its original vendor, disc, store, or launcher. Keep saved games and personal project files if the installer asks whether to remove them.

For a very old program, use the original installation media if possible. The exact legacy runtime may have been supplied with that application, and a modern redistributable may not contain the file it needs.

Do not download a random replacement DLL to compensate for a damaged installation. Reinstalling the program is more likely to restore the correct runtime, configuration files, registry entries, and supporting libraries together.

Fix 2: Verify game files through the launcher

Time needed: 5–30 minutes

If the error belongs to a game, use the launcher’s file-repair or verification feature before trying Windows repairs.

The names differ between launchers, but the process generally looks like this:

1. Open the launcher used to install the game.
2. Open your library.
3. Find the affected game.
4. Open its menu.
5. Choose Verify, Verify integrity, Repair, or a similarly named option.
6. Wait for the scan to finish.
7. Allow the launcher to replace missing or modified files.
8. Start the game again.

Verification normally compares the installed files with the launcher’s expected files. It may redownload the correct application-local runtime without affecting saved data, although you should still avoid interrupting the process.

What success looks like

The launcher reports that files were repaired or verified, and the game starts normally.

If verification finds nothing

Check whether the game was installed from a different launcher, copied from another computer, or moved to a new folder. The launcher may be checking a different installation than the one producing the error.

If the game still fails, use the launcher’s uninstall and reinstall options or reinstall from the original source. Do not place a DLL from an unrelated game beside the executable merely because the filename matches.

Fix 3: Restore the runtime from the original installer

Time needed: 10–30 minutes

Some old applications used a private copy of msvcrt20.dll in their own installation directory. Others expected a compatible copy in a Windows system location. The correct location depends on the application and the installation technology used at the time.

Use this fix only when the file comes from:

• The original application installer
• Authentic installation media
• A support package supplied by the application vendor
• Documentation that explicitly identifies the application-local runtime

If you still have the installer or disc:

1. Close the affected program.
2. Close any launcher or updater for that program.
3. Run the original installer.
4. Choose Repair, Modify, or a complete reinstall if offered.
5. Allow the installer to restore its runtime files.
6. Restart Windows if requested.
7. Test the application.

If the installer extracts files to a temporary folder, let the installer place them itself. Do not manually choose System32 or SysWOW64 unless the original installation instructions specifically require it for that historical operating system.

Microsoft documents application-local DLL deployment and DLL redirection as legitimate ways for an application to use its own private dependency. Microsoft’s DLL redirection documentation explains why keeping a compatible private DLL with the application can avoid conflicts between unrelated programs.

What success looks like

The application starts using the runtime restored by its own installer.

If the installer restores the wrong file

Stop and note the exact error. Historical versions of this runtime were not universally interchangeable. Microsoft recorded separate msvcrt20.dll builds for Win32s and for Windows NT or Windows 95 environments. Using the wrong build could produce an explicit compatibility error.

Do not select a file based only on its name. The runtime must match the application, operating system environment, and architecture.

Fix 4: Do not confuse msvcrt20.dll with modern Visual C++ packages

Time needed: 10–20 minutes

The current Microsoft Visual C++ Redistributable download page provides packages such as:

• vc_redist.x86.exe
• vc_redist.x64.exe
• vc_redist.arm64.exe

Those current packages support modern Visual C++ applications, including applications built with Visual Studio 2017 and later. The page also links to older Visual C++ packages, but it does not identify a current Visual C++ 2.0 redistributable containing msvcrt20.dll.

This means installing the newest x86 package is not a guaranteed fix for an application that explicitly requests msvcrt20.dll.

The names below refer to different runtime generations:

File	General runtime generation
msvcrt20.dll	Visual C++ 2.x-era runtime
msvcrt.dll	A different Microsoft C runtime name
msvcr70.dll, msvcr71.dll	Visual C++ .NET-era runtimes
msvcr80.dll, msvcr90.dll	Later Visual C++ runtimes
msvcr100.dll	Visual C++ 2010 runtime
msvcr110.dll	Visual C++ 2012 runtime
msvcr120.dll	Visual C++ 2013 runtime
vcruntime140.dll	Visual Studio 2015 and later runtime family

Install a redistributable only when the application documentation or installer identifies that specific runtime. Microsoft recommends obtaining redistributable installers from Microsoft-hosted locations and using Microsoft-signed packages. Microsoft’s troubleshooting guidance covers safe installation and verification practices.

What success looks like

The application starts after the correct Microsoft package has been installed and Windows has been restarted if necessary.

If the package installs but the error remains

That package probably does not contain the legacy runtime the application requests. Return to the application’s repair or reinstall process instead of installing every Visual C++ package in sequence.

Fix 5: Check antivirus quarantine

Time needed: 5–15 minutes

Security software can remove or quarantine a legacy DLL. It is also possible for an old DLL to be modified, replaced, or bundled with an untrusted installer, so do not restore a quarantined file automatically.

To review Microsoft Defender detections:

1. Open Start.
2. Search for Windows Security and open it.
3. Select Virus & threat protection.
4. Select Protection history.
5. Review recent detections involving the affected program or msvcrt20.dll.
6. Open the relevant entry to see whether the file was quarantined, blocked, or removed.

Protection History does not retain events indefinitely, so an older detection may no longer be visible. Microsoft explains this workflow in its guide to Protection History.

What success looks like

The program starts after you reinstall it from a trusted source and Windows Security no longer blocks a legitimate application file.

If the file was quarantined

Prefer reinstalling the original application rather than restoring an isolated DLL. If you are certain the file came from authentic installation media and the detection is a false positive, review the available Windows Security action carefully and scan the entire installer before proceeding.

Never add an unknown DLL to antivirus exclusions simply to make an old program start.

Fix 6: Install pending Windows updates

Time needed: 10–30 minutes, plus download time

Windows updates can repair protected operating-system components and address compatibility problems. They will not necessarily provide an application’s private Visual C++ 2.x runtime, but updating Windows is appropriate when several programs are malfunctioning or Windows itself is unstable.

Windows 11

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install available updates.
6. Restart when prompted.
7. Return to Windows Update and check again.

Windows 10

1. Open Start.
2. Select Settings.
3. Select Update & Security.
4. Select Windows Update.
5. Select Check for updates.
6. Install available updates.
7. Restart Windows.

What success looks like

The application starts after the update and restart, or other Windows component errors disappear.

If the error remains

Continue with the system-file checks below only if there are signs that Windows itself is damaged. A single old application failing while the rest of Windows works normally is more likely to have an application-specific problem.

Fix 7: Repair Windows components with DISM and SFC

Time needed: 15–45 minutes

Use DISM and System File Checker when:

• Multiple Windows programs report missing or corrupt system files
• Windows Update is failing
• Built-in Windows tools are malfunctioning
• The error appeared after system corruption, an interrupted update, or a serious crash
• You have evidence that Windows, rather than the application, owns the missing file

SFC does not magically install a third-party application’s missing private DLL. Microsoft recommends running DISM before SFC. Microsoft’s System File Checker instructions provide the same repair sequence.

1. Open Start.
2. Search for Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes if User Account Control asks for permission.
6. Enter this command and press Enter:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish. Do not close the window if progress appears to pause.
2. Run:

sfc /scannow

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

What success looks like

SFC reports that it found and repaired corrupted files, and the application or Windows component starts normally after the restart.

If SFC reports that it could not repair some files

Restart Windows and run sfc /scannow once more. If it still reports unrepaired files, review the CBS log or continue with Windows Update and System Restore. Do not download a replacement DLL and overwrite protected Windows folders.

Repeating DISM and SFC without knowing what changed can make troubleshooting tedious. Outbyte PC Repair can perform a free scan that shows what it finds; repairs are handled by the full version, and it is optional rather than required. If the DLL belongs to one specific game or application, reinstalling that program remains the definitive fix.

Fix 8: Use System Restore after a known system change

Time needed: 20–60 minutes

System Restore is useful when the problem began immediately after:

• Installing an SDK or old application
• Running a system cleanup tool
• Installing a Windows update
• Installing a driver or security product
• Changing system files or configuration

It rolls back system files, registry settings, drivers, and installed programs to an earlier restore point while normally preserving personal files.

Start System Restore from Windows

1. Open Control Panel.
2. Set View by to Small icons or Large icons.
3. Select Recovery.
4. Select Open System Restore.
5. Choose a restore point created before the msvcrt20.dll failure.
6. Select Next.
7. Review the affected programs.
8. Select Finish.
9. Allow Windows to restart and complete the restore.

You can also press Win+R, enter the following command, and press Enter:

rstrui.exe

Microsoft documents the process in its System Restore guide.

What success looks like

The program starts after Windows returns to the earlier restore point.

If no restore point exists

System Restore cannot help without a suitable restore point. Return to the application repair or reinstall steps. If many Windows components remain damaged, consider an in-place Windows repair installation that keeps personal files and applications. Back up important files first.

Fix 9: Check application compatibility

Time needed: 10–30 minutes

A program old enough to request msvcrt20.dll may have additional compatibility requirements. The missing DLL may be only the first problem exposed by a modern Windows installation.

Run the compatibility troubleshooter

1. Open Settings.
2. Select System.
3. Select Troubleshoot.
4. Select Other troubleshooters.
5. Find Program Compatibility Troubleshooter.
6. Select Run.
7. Choose the affected application.
8. Follow the recommendations.
9. Test the program.

The exact menus can differ between Windows 10 and Windows 11. You can also right-click the application’s executable, select Properties, open the Compatibility tab, and test an appropriate compatibility mode.

Check optional Windows features

Some older programs depend on a Windows component unrelated to the runtime itself. Do not enable features randomly, but check the application’s documentation if it specifically requires one.

1. Press Win+R.
2. Enter:

optionalfeatures

1. Press Enter.
2. Review the available feature list.
3. Expand Legacy Components if the application requires it.
4. Enable only the component identified by the program’s documentation.
5. Select OK.
6. Restart Windows if requested.

Enabling a legacy feature does not install msvcrt20.dll. It may only provide an additional compatibility component required by a particular old game or application.

Understand the 16-bit limit

A 16-bit Windows application or installer cannot run directly on 64-bit Windows. A 32-bit Win32 application may run under WOW64, but it can still depend on old installers, copy-protection drivers, graphics APIs, or other libraries that modern Windows no longer supports.

If the program is 16-bit, possible solutions include:

• Finding a newer release from the publisher
• Using an official compatibility update
• Running the original 32-bit Windows environment in an isolated virtual machine
• Using the program on appropriate legacy hardware kept away from sensitive networks

Do not weaken Windows security or install unknown drivers solely to run an untrusted old binary.

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

Fix 10: Update or reinstall a related driver only when evidence points there

Time needed: 15–30 minutes

A graphics, chipset, printer, or device driver is not a normal cause of a missing msvcrt20.dll error. The DLL is a user-mode C runtime, not a kernel driver.

Consider a driver investigation only when:

• The error appears inside a specific hardware vendor utility
• The affected installer explicitly bundles the runtime
• The problem began during a driver installation
• Device Manager shows a related device error
• The program fails alongside a visible graphics or hardware fault

Check Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand the category related to the affected hardware.
4. Look for a yellow warning icon.
5. Right-click the device.
6. Select Properties.
7. Review the General and Driver tabs.
8. Use Update driver only with a driver from Windows Update or the hardware manufacturer.
9. Restart Windows.
10. Test the original application.

If the problem began immediately after a driver update, open the device’s Driver tab and use Roll Back Driver if that option is available.

Guessing which of dozens of installed drivers is stale can consume more time than the DLL repair itself. Outbyte Driver Updater provides a free scan showing what it identifies; installing drivers is handled by the full version, and it is optional. A driver update is not a substitute for reinstalling the application that actually requested msvcrt20.dll.

What success looks like

The specific hardware utility or application starts after the relevant driver is repaired, and Device Manager no longer shows a related warning.

If nothing changes

Stop treating the issue as a driver problem. Return to the application installer, runtime version, architecture, or compatibility environment.

Do not use regsvr32 for this runtime

regsvr32 is intended for self-registering DLLs and ActiveX or COM components that provide the DllRegisterServer entry point. Microsoft explains that a normal dependency DLL may produce an “entry point not found” or “not self-registerable” error when passed to Regsvr32.

msvcrt20.dll is a runtime dependency, not a COM registration component. Running this command does not repair a missing-runtime problem:

regsvr32 msvcrt20.dll

If you already tried it and received an error, that result is expected and does not diagnose the original problem.

Why random DLL downloads are unsafe

Do not download msvcrt20.dll from a random DLL catalog, forum attachment, file-sharing page, or “fixer” installer.

A downloaded DLL may be:

• Malware or a modified binary
• The wrong historical build
• The wrong architecture
• The Win32s variant instead of the Windows NT or Windows 95 variant
• Missing required exports
• Intended for a different application
• A file that Windows Security correctly removed

Even a genuine DLL may not fix the root cause if the application also lacks another dependency, has damaged configuration, or is using a second copy from the wrong folder.

The safe sources are:

• The original application installer
• Authentic installation media
• The application vendor’s official repair package
• A game launcher’s built-in file verification
• Microsoft-hosted Visual C++ redistributables when the application explicitly requires that runtime

Microsoft’s current redistributable page does not establish that its modern packages install msvcrt20.dll, so do not treat vc_redist.x86.exe as a universal solution.

If the DLL exists but the error continues

A copy of the file on disk does not prove that the application can load it.

Check these possibilities:

The executable is using another copy

Windows normally searches the application directory before system directories. A damaged or incompatible copy beside the executable can override a usable system copy. Microsoft documents the DLL search order.

Look in the program’s installation directory for duplicate copies. Do not delete them blindly. First use the application’s repair or reinstall process.

The architecture is wrong

A 32-bit application needs a compatible 32-bit runtime. Do not copy files between System32 and SysWOW64 as a generic repair method.

The error names an entry point

An entry-point error often means the DLL is present but is the wrong version. This can happen when an older installer overwrites the runtime expected by a newer application. Reinstall the affected application from its original source and restore its expected files in the correct order.

Another dependency is missing

The loader may report msvcrt20.dll when the actual failure involves another dependency or an incompatible application environment. Repairing only one DLL may leave the program unable to start.

The launcher uses a different folder

A shortcut, launcher, or compatibility wrapper may start a different executable from the one you inspected. Open the program’s shortcut properties and verify the Target path. Then repair the installation associated with that exact executable.

Common causes and the matching fix

Likely cause	Best response
Incomplete or damaged application installation	Repair or reinstall the application
Game file removed or changed	Verify files through the game launcher
Wrong Visual C++ generation installed	Install the runtime named by the application, not a random newer package
Win32s and Windows NT/95 build mismatch	Restore the matching file from original media
Older installer overwrote a newer runtime	Repair the application that originally required the newer build
Antivirus quarantine	Review Protection History, then reinstall from a trusted source
Windows component corruption	Run DISM, then SFC
Recent update or cleanup caused the failure	Use System Restore
16-bit application on 64-bit Windows	Use a supported newer release or isolated legacy environment
Driver utility is the only affected program	Investigate the related device driver
regsvr32 was used	Stop using it; runtime DLLs are not normally registered

Frequently asked questions

Is msvcrt20.dll a Windows system file?

It was part of or required by some historical Windows releases, including Windows 95-era environments. It may also have been installed by Visual C++ or by individual applications.

Do not assume that every Windows 10 or Windows 11 installation should contain it. The application that requested the file may own the required copy.

Is msvcrt20.dll 32-bit or 64-bit?

Treat it as a 32-bit legacy runtime and verify the target application. A 32-bit application cannot load a 64-bit DLL.

Will installing the latest Visual C++ Redistributable fix it?

Not necessarily. Current redistributables support later Visual C++ generations and are not identified as Visual C++ 2.x packages containing msvcrt20.dll.

Can I copy the file into System32?

Do not use that as a general repair. On 64-bit Windows, System32 and SysWOW64 represent different system environments, and copying the wrong file can create additional conflicts.

Use the original application installer or an application-local copy documented by the vendor.

Should I copy the DLL beside the program?

Only when the copy comes from the original installer, authentic installation media, or a trusted vendor support package, and when it matches the application’s architecture and expected version.

Should I run regsvr32 msvcrt20.dll?

No. msvcrt20.dll is a runtime dependency, not a normal COM component that needs registration.

Will SFC restore it?

Only if Windows owns the file and has a matching protected copy. SFC does not automatically supply a missing private DLL used by an old game or application.

Why does the error mention Win32s?

The program may have loaded the Win32s build of the runtime on an incompatible Windows environment, or loaded the standard Windows NT/Windows 95 build where Win32s was expected. Restore the correct file from the original application or development environment.

What information should I provide when asking for help?

Include:

• The exact error text
• The application name and version, if known
• Whether it is a game, utility, installer, or development tool
• Windows 10 or Windows 11
• Whether Windows is 32-bit or 64-bit
• Where the program came from
• Whether Repair, reinstall, or launcher verification was attempted
• Whether the message says missing, incompatible, or entry point

The most reliable repair path is to trace msvcrt20.dll back to the program that requested it, restore that program from its original source, and use Windows component repairs only when there is evidence that Windows itself is damaged.

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.