msr2c.dll Missing: Rebuild the Legacy Forms Dependency Safely

Error messages this guide covers

You may see “This application failed to start because msr2c.dll was not found,” “msr2c.dll is missing from your computer,” or “msr2c.dll could not be loaded.”

Other common variants include “The file msr2c.dll is missing or corrupted,” “A required component is missing: msr2c.dll,” and “The procedure entry point could not be located in msr2c.dll.”

As an Amazon Associate I earn from qualifying purchases.

The 60-second answer

msr2c.dll is a genuine Microsoft legacy Forms DLL associated with old Windows and Internet Explorer-era components. It is primarily a 32-bit legacy file, not a modern Visual C++, DirectX, or .NET runtime.

There is no verified current Microsoft standalone download for msr2c.dll. Do not download a replacement from a random DLL website or copy one into System32. The safest repair is to identify the application that displays the error, then repair or reinstall that application from its original developer installer or trusted installation media.

If the error affects an old Windows installation or virtual machine, repair the matching Windows image instead. Also confirm that the message really names msr2c.dll; Office VBA errors often involve the different file FM20.DLL.

What is msr2c.dll

Historical Microsoft installation records identify msr2c.dll as Microsoft Forms DLL. It appeared with legacy Windows and Internet Explorer components, alongside the related language resource msr2cenu.dll. Historical file records identify Win32 builds, including an older version listed as 1.00.4211.0 and a size of 69,632 bytes.

Those details describe historical releases, not a current Windows 10 or Windows 11 package. Modern Windows may not contain every file from the Internet Explorer-era component set. The absence of msr2c.dll on a modern PC does not automatically mean Windows is damaged.

The file was historically installed in the Windows system directory. It may also be present in an application folder when an old program supplied or retained its own copy. The location matters: a copy in Downloads, Temp, or an ordinary user-writable folder should be treated cautiously until its source and signature are verified.

First, identify the program requesting the file

The error dialog usually names the application that failed. Write down:

• The exact executable or program name
• Whether the error appears during Windows startup or only when launching one program
• The full path shown in the dialog, if available
• Whether the issue began after uninstalling software, restoring a backup, cleaning the disk, or antivirus quarantine
• Whether the program is an old 32-bit application

If only one application fails, its installation is the leading suspect. If several unrelated programs fail, investigate Windows corruption or storage problems instead.

To inspect the requesting program:

1. Right-click the program shortcut.
2. Select Open file location.
3. Right-click the application’s .exe file and select Properties.
4. Check the Details and Digital Signatures tabs.
5. Note whether the executable is installed under Program Files, Program Files (x86), or an older custom folder.

Do not assume that a file named msr2c.dll found elsewhere is a valid replacement. A similarly named DLL from another product may have incompatible exports or dependencies.

Fix 1: Repair or reinstall the affected application

This is the best first repair when one old program produces the error.

Use the application’s repair option

1. Press Windows + I to open Settings.
2. Select Apps.
3. Select Installed apps.
4. Find the affected application.
5. Select the three-dot menu beside it.
6. Choose Advanced options, if available.
7. Select Repair.
8. Restart Windows and test the application.

Some programs provide their own repair function instead:

1. Open the application’s installation folder.
2. Look for setup.exe, repair.exe, a launcher, or a maintenance utility.
3. Right-click it and choose Run as administrator.
4. Select Repair, Verify files, or the equivalent option.

Reinstall from a trusted source

If repair is unavailable or does not work:

1. Back up the application’s documents, saved games, profiles, and license information.
2. Open Settings → Apps → Installed apps.
3. Uninstall the affected program.
4. Restart Windows.
5. Reinstall it from the developer’s official installer, original disc, or trusted business deployment media.
6. Apply the program’s available updates.
7. Start it again from its normal shortcut.

A complete reinstall is more reliable than replacing one DLL because the application may also need old registry entries, type libraries, language resources, or companion files.

If the installer fails on Windows 10 or Windows 11, right-click its setup file, select Properties → Compatibility, enable Run this program in compatibility mode, and test the Windows version suggested by the application vendor. Do not install obsolete Internet Explorer broadly or weaken Windows security merely to satisfy one legacy program.

Fix 2: Check antivirus quarantine

Security software may remove or quarantine an old DLL, particularly when it has weak or unavailable modern publisher metadata. That does not prove the file is malicious, and it does not prove that restoring it is safe.

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Protection history.
4. Look for an event involving msr2c.dll or the affected application.
5. Record the detection name and original file path.
6. Do not restore the file unless it came from trusted application or Windows installation media.
7. Prefer reinstalling the application after confirming the quarantine event.

Then select Scan options → Full scan. If the file appeared in a temporary or user-writable directory rather than the program’s expected folder, leave it quarantined and investigate the application.

Fix 3: Repair Windows component files

Use Windows repair commands when multiple programs report missing files, Windows behaves abnormally, or the affected file belonged to an old Windows installation.

First install pending updates and restart:

1. Press Windows + I.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart the computer.

Then run DISM and System File Checker:

1. Open Start and type Command Prompt.
2. Right-click Command Prompt.
3. Select Run as administrator.
4. Run:

DISM.exe /Online /Cleanup-image /Restorehealth

1. Wait for DISM to finish.
2. Run:

sfc /scannow

1. Restart Windows after the scan completes.
2. Launch the affected application again.

DISM repairs the Windows component store. SFC scans protected Windows files and replaces damaged copies when the installed Windows image contains the relevant component. It is not guaranteed to restore a legacy DLL that modern Windows no longer includes.

If DISM cannot obtain repair files, use a matching Windows repair source supplied by trusted installation media:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

The source must closely match the installed Windows edition and build. Using files from an unrelated Windows release can create additional problems.

Repeatedly hunting through Windows folders and rerunning SFC or DISM without knowing what changed can make diagnosis harder. Outbyte PC Repair provides a free scan that identifies reported problems, while repairs are handled by the full version. If the missing file belongs to a particular application, reinstalling that application remains the definitive fix.

Fix 4: Check the 32-bit application path

msr2c.dll is a legacy Win32 component. A 32-bit application may fail because it cannot find its required files, even when a different copy exists elsewhere.

Do not copy the DLL into both C:WindowsSystem32 and C:WindowsSysWOW64. On 64-bit Windows, those folders use counterintuitive naming, and placing an incompatible DLL in either location can affect other software.

Instead:

1. Identify the failing executable.
2. Check whether it is installed under Program Files (x86).
3. Reinstall the complete application package.
4. Use the application vendor’s 32-bit or legacy installer when one is provided.
5. Test the program after each repair rather than copying isolated files.

If the program runs only inside a virtual machine, repair the application within that virtual machine. A Windows 2000 or Windows XP-era dependency should be restored from matching installation media or a known-good system backup, not from a newer Windows computer.

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

Fix 5: Use regsvr32 only for a registration error

A DLL is not automatically registerable merely because its name ends in .dll. Microsoft’s regsvr32 command calls a registration entry point such as DllRegisterServer. If that entry point does not exist, registration is not the correct repair.

Use registration only when:

• The error explicitly says the component is not correctly registered
• An old Internet Explorer component repair specifically requires it
• You have a known-good file in the expected Windows directory

Open Command Prompt as administrator and run:

%windir%System32regsvr32.exe "%windir%System32msr2c.dll"

On 64-bit Windows, use the 32-bit registration tool when the DLL and requesting application are 32-bit:

%windir%SysWOW64regsvr32.exe "C:pathtomsr2c.dll"

If Windows reports that DllRegisterServer is missing, stop using regsvr32; the DLL is not registerable through that command. If error 0x80070005 appears, reopen Command Prompt with Run as administrator. Do not register a downloaded or suspicious copy.

Fix 6: Do not confuse msr2c.dll with FM20.DLL

Microsoft Forms filenames are easy to confuse.

FM20.DLL is the Microsoft Forms 2.0 library commonly associated with Office VBA UserForms. msr2c.dll is a different legacy Microsoft Forms DLL associated with older Windows and Internet Explorer components.

Read the exact filename in the error dialog. If it says FM20.DLL and the failure occurs in Excel, Access, or Word:

1. Press Windows + I.
2. Select Apps → Installed apps.
3. Find Microsoft 365 or Microsoft Office.
4. Select the three-dot menu.
5. Choose Modify.
6. Select Online Repair.
7. Follow the prompts and restart Office.

Do not apply Office Forms troubleshooting to an application that actually requests msr2c.dll.

Fix 7: Update related drivers only when the application also reports driver errors

msr2c.dll is not a graphics, audio, chipset, or DirectX driver. Updating a driver will not normally recreate this DLL. Driver work is relevant only when the old application also crashes with display, sound, hardware-acceleration, or device errors.

To update a driver manually:

1. Right-click Start.
2. Select Device Manager.
3. Expand the category for the affected device.
4. Right-click the device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if prompted.

For a clean reinstall, right-click the device, select Uninstall device, restart, and install the current driver from the hardware manufacturer’s official support page. Do not remove devices you cannot identify.

Finding the correct driver manually can involve comparing hardware IDs, Windows versions, and 32-bit versus 64-bit packages. Outbyte Driver Updater provides a free scan showing outdated drivers, while driver installation is handled by the full version. It is not a substitute for reinstalling the application that owns the msr2c.dll dependency.

Fix 8: Check optional Windows features only when the program requires them

Do not enable random legacy features to resolve this filename. msr2c.dll is not evidence that .NET Framework or DirectPlay is missing.

If the application’s own documentation explicitly requires an optional component:

1. Open Start and search for Windows features.
2. Select Turn Windows features on or off.
3. Enable only the named feature, such as .NET Framework 3.5.
4. Select OK.
5. Restart Windows if requested.
6. Test the application.

If no documented feature is required, leave this area unchanged and return to repairing the application installation.

When to stop troubleshooting

Stop copying files and restore the application from a backup or replacement installer when:

• The program is no longer supported and has no compatible installer
• The error remains after a complete reinstall
• More than one legacy dependency is missing
• The file exists only in an untrusted directory
• Windows repair finds broader disk or profile corruption
• The program works only in an old virtual machine

For a legacy business application, preserve the original virtual machine, installer media, license details, and system backup. Moving the application to a supported replacement is safer than weakening current Windows protections.

FAQ

Is msr2c.dll a virus?

The filename itself is associated with a genuine historical Microsoft Forms DLL. A copy in Downloads, Temp, or an application-data folder is not automatically trustworthy. Check its origin, location, antivirus history, and digital signature before considering restoration.

Can I download msr2c.dll separately?

There is no verified current Microsoft standalone download for this file. Use the original application installer, matching Windows installation media, or an appropriate Windows repair process instead.

Why does the file not exist on Windows 11?

It is a legacy Windows and Internet Explorer-era component. Current Windows versions may not include it, and its absence alone does not prove corruption.

Will regsvr32 fix the error?

Only if the DLL supports registration and the error is genuinely registration-related. A missing dependency usually requires repairing or reinstalling the application.

Why does SFC say it found no problem?

SFC repairs protected files present in the installed Windows image. It may report no corruption when msr2c.dll was supplied by an old application or is no longer part of modern Windows.

What if the dialog actually says FM20.DLL?

Follow the Office repair path instead. FM20.DLL and msr2c.dll are different files with different owners and troubleshooting steps.

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.