mscorld.dll Errors: Trace the Correct Legacy .NET Runtime

“The program can’t start because mscorld.dll is missing from your computer.”
“This application failed to start because mscorld.dll was not found.”

You may also see “Error loading mscorld.dll. The specified module could not be found” or “mscorld.dll is either not designed to run on Windows or it contains an error.” These messages indicate that Windows or an application could not load the legacy .NET Framework component named mscorld.dll.

As an Amazon Associate I earn from qualifying purchases.

The 60-second answer

mscorld.dll is a genuine Microsoft .NET Framework runtime file, not a random third-party DLL. It is associated with older .NET Framework installations, including the v1.0.3705, v1.1.4322, and v2.0.50727 runtime directories. Microsoft security bulletins list the file in .NET Framework manifests for versions 1.0 and 1.1. See the MS07-040 file manifest and MS09-061 file manifest.

The safest first repair on Windows 10 and most Windows 11 systems is:

1. Open Start, search for Windows Features, and select Turn Windows features on or off.
2. Select .NET Framework 3.5 (includes .NET 2.0 and 3.0).
3. Select OK and allow Windows to download the required files.
4. Restart Windows and try the affected application again.

Do not download mscorld.dll from a DLL archive and copy it into System32, SysWOW64, or the application folder. That can introduce the wrong version, wrong architecture, a modified file, or malware, while leaving the damaged .NET installation untouched.

If the problem affects only one program, repair or reinstall that program after enabling .NET Framework 3.5. If several unrelated programs fail, repair Windows components and inspect the installed .NET Framework instead.

What is mscorld.dll?

mscorld.dll is a Microsoft .NET Framework runtime component. The repeated description “Microsoft Remote object loader” is best treated as an internal or metadata label. Microsoft’s public documentation verifies the file’s presence in .NET Framework file manifests and its association with the product, but it does not provide a complete public functional explanation of the DLL.

This distinction matters because mscorld.dll is not normally a standalone Windows system DLL stored in C:\Windows\System32. It traditionally belongs inside the Microsoft .NET Framework directories.

Typical locations include:

C:\Windows\Microsoft.NET\Framework\v1.0.3705\
C:\Windows\Microsoft.NET\Framework\v1.1.4322\
C:\Windows\Microsoft.NET\Framework\v2.0.50727\

On 64-bit Windows, corresponding 64-bit runtime files may be under:

C:\Windows\Microsoft.NET\Framework64\

In general:

• Framework is associated with the 32-bit .NET Framework runtime.
• Framework64 is associated with the 64-bit runtime.
• A 32-bit application may need the copy under Framework.
• A 64-bit application may use the copy under Framework64.
• .NET Framework 2.0, 3.0, and 3.5 use the v2.0.50727 runtime family.

Microsoft documents these framework directory conventions in its provider installation and .NET Framework guidance.

The file should not normally be copied into System32 or SysWOW64. Those directories are not substitutes for the .NET Framework runtime directories.

Which .NET Framework versions contain it?

Microsoft manifests verify these examples:

Framework release or update	Verified file version	Verified size
.NET Framework 1.0 security update	1.0.3705.6060	86,016 bytes
.NET Framework 1.1 update	1.1.4322.2407	102,400 bytes
.NET Framework 1.1 SP1 update	1.1.4322.2443	102,400 bytes

The exact version installed on a particular computer can vary with the servicing update, operating system, architecture, and language. Public installation inventories also show mscorld.dll under v2.0.50727, but exact v2.0 file versions and sizes should be read from the installed file or supplied by the official application installer.

Do not use the table to select a replacement DLL manually. The correct repair must restore the complete runtime package that owns the file.

Why Windows reports this error

The message does not always mean that mscorld.dll itself is absent. “The specified module could not be found” can also mean that Windows found the named DLL but could not load a dependency required by it. Microsoft explains this distinction in its module-not-found guidance.

The practical causes usually fall into these groups:

What happened	What it usually means	Best next action
A clean Windows installation or upgrade preceded the error	The legacy runtime is missing or disabled	Enable .NET Framework 3.5
Only one application reports the error	That application may be incomplete or damaged	Repair or reinstall the application
The file exists but Windows says it is invalid	The file or its dependencies may be corrupted or incompatible	Repair the runtime and run DISM and SFC
Defender recently detected or removed a file	The file may be quarantined	Inspect Protection History and reinstall from Microsoft
The path mentions v1.1.4322	The program may target .NET Framework 1.1	Check compatibility before installing the old package
The error occurs after cleanup software ran	Runtime files or component-store files may have been removed	Repair .NET and Windows components
A 32-bit program cannot load a 64-bit copy	The runtime architecture does not match the application	Restore the correct framework installation
The named file exists but the error persists	A dependency or application file may be missing	Identify the calling executable and inspect its logs

Before changing anything, identify whether the problem is system-wide or limited to one application.

First, identify the application and exact path

The error dialog often names the missing DLL but not the program that requested it. That program matters because a single damaged application requires a different repair from a missing Windows feature.

Check the following:

1. Read the complete error message and record the executable name if it appears.
2. Look at the shortcut you used to start the program.
3. Right-click the shortcut and select Properties.
4. Read the Target field.
5. Note whether the target points to a game, business application, installer, launcher, or an old utility.
6. Note whether the error began after an uninstall, application update, Windows upgrade, cleanup operation, antivirus detection, or failed .NET installation.

If the error appears only when one program starts, that program is the leading suspect. If several unrelated programs fail, prioritize the .NET Framework and Windows component repairs.

You can also search the installed .NET directories for existing copies. Open PowerShell from Start and run:

Get-ChildItem "$env:windir\Microsoft.NET" -Filter mscorld.dll -Recurse -Force |
  Select-Object FullName, Length,
    @{Name="FileVersion";Expression={$_.VersionInfo.FileVersion}}

Interpret the result carefully:

• If no result appears, the expected runtime component may be missing.
• If a result appears under Framework\v1.1.4322, the application may require .NET Framework 1.1.
• If a result appears under Framework\v2.0.50727, the application may be using the .NET 2.0 through 3.5 runtime family.
• If a file exists but the application still fails, the application may be loading another architecture or a dependency may be missing.
• A file’s presence does not prove that its contents are healthy or that the application is requesting that particular copy.

Do not replace a file merely because its version does not match an online list. Servicing updates can change the version.

Fix 1: Enable or repair .NET Framework 3.5

This is the best first repair for most modern Windows installations running an older .NET application. .NET Framework 3.5 includes .NET Framework 2.0 and 3.0, which use the older v2.0.50727 runtime family.

Windows 10 and most Windows 11 installations

1. Select Start.
2. Type Windows Features.
3. Select Turn Windows features on or off.
4. Find .NET Framework 3.5 (includes .NET 2.0 and 3.0).
5. Select its check box.
6. Select OK.
7. When Windows asks to download files from Windows Update, allow it.
8. Wait for the installation to finish.
9. Restart the computer.
10. Start the affected application again.

If the application starts normally, the missing runtime was the cause. Leave the repaired framework installation in place.

If Windows says it could not complete the requested changes, do not download mscorld.dll separately. Use the DISM method below.

Windows 11 version 26H1 and later

On Windows 11 version 26H1, build 28000, and later, .NET Framework 3.5 is installed through Microsoft’s standalone package rather than through Windows Features. Use Microsoft’s .NET Framework 3.5 download guidance and the Windows 11 .NET Framework installation FAQ.

Use only the package supplied through Microsoft’s official download pages. The available official .NET Framework 3.5 SP1 packages include:

• The 3.5 SP1 web bootstrapper, named dotnetfx35setup.exe.
• The 3.5 SP1 full package, named dotnetfx35.exe.

After installation, restart Windows and test the application. If the installer reports that the framework is already installed but the error remains, continue with application repair and the Windows component checks.

Fix 2: Repair or reinstall the affected application

If only one program reports mscorld.dll, repairing that program is often more appropriate than copying a framework file into its directory.

Repair a Microsoft Store or supported Windows application

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

Microsoft documents these steps in Repair apps and programs in Windows.

If Repair does not solve the problem and the application provides Reset, understand that Reset may remove the application’s local settings or stored data. Check the application’s own documentation before using it.

Repair a traditional desktop program

1. Open Start.
2. Type Control Panel and open it.
3. Select Programs.
4. Select Programs and Features.
5. Select the affected program.
6. Look for Repair, Change, or a similar maintenance option.
7. Follow the installer prompts.
8. Restart Windows if requested.
9. Test the program again.

If no repair option exists, uninstall the program and reinstall it using the original vendor installer, official launcher, or trusted installation media. Do not download a replacement mscorld.dll from a file archive.

If the error began after an application update, use the application’s official file-verification or repair function if it provides one. If the program owns a private copy of the DLL, reinstalling the program is the definitive repair for that copy.

Fix 3: Repair the .NET Framework installation

If .NET Framework 3.5 is enabled but the error continues, Microsoft’s .NET Framework Repair Tool can repair supported setup and registration problems.

Download the Microsoft .NET Framework Repair Tool. Microsoft’s supporting documentation explains that the tool supports .NET Framework 3.5 SP1 and attempts known setup repairs. It is not a standalone replacement for mscorld.dll.

Run it as follows:

1. Download NetFxRepairTool.exe from Microsoft.
2. Open the downloaded file.
3. Accept the license terms.
4. Allow the tool to inspect the .NET Framework installation.
5. Apply the recommended repairs.
6. Restart Windows if requested.
7. Start the affected program again.

If the tool reports that it cannot repair the installation, record the result and continue with DISM and SFC. Do not repeatedly run the repair tool without addressing a component-store or application-installation problem.

The manual process of hunting through Windows features, comparing framework folders, and repeating SFC or DISM without knowing what changed can be time-consuming. Outbyte PC Repair provides a free scan that shows what is wrong, while repair actions are handled by the full version, so it remains optional and is not required for this fix.

Fix 4: Repair Windows component files with DISM and SFC

Use these commands when Windows components may be damaged, when .NET installation repeatedly fails, or when several applications show related system-file errors.

You must run the commands from an elevated Command Prompt.

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

DISM.exe /Online /Cleanup-image /Restorehealth

1. Wait for DISM to finish. It may remain at a particular percentage for a while.
2. After DISM completes, run:

sfc /scannow

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

Run DISM first and SFC second. DISM repairs the Windows component source that SFC uses when it replaces protected system files. Microsoft documents this repair sequence in its System File Checker instructions.

What the results mean

If DISM reports that the restore operation completed successfully and SFC reports that it found and repaired corrupt files, restart and test the application.

If SFC reports that it found no integrity violations, the problem may be the application installation, the .NET Framework feature, or a missing dependency rather than a protected Windows file.

If SFC says it found corrupt files but could not repair some of them, restart and run the commands again only if the first run clearly completed. If the same result persists, use the Microsoft .NET Framework installer or repair tool, and repair the affected application.

SFC is not a substitute for reinstalling an application. It may repair framework-related files only when Windows has a matching protected component source.

Fix 5: Check Microsoft Defender Protection History

Antivirus software can quarantine a file after a false positive or after detecting tampering. Do not assume that every quarantined file should be restored.

Check Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review detections around the time the mscorld.dll error began.
7. Expand any relevant detection.
8. Record the path, detection name, and action taken.

Microsoft explains Protection History in its Windows Security documentation.

If the quarantined file was under a legitimate Microsoft .NET Framework directory, confirm the path and source before taking any action. Do not blindly restore it. Prefer reinstalling or repairing the official .NET Framework package so Windows receives a complete, trusted installation.

If the file was in an unexpected temporary folder, a download directory, or an application directory that you do not recognize, leave it quarantined and run a full scan.

To run a full scan:

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

If malware is suspected or the detection returns after reinstalling the runtime, use Microsoft Defender Offline from the same scan options screen.

Fix 6: Check the runtime architecture

A 32-bit application and a 64-bit application do not always use the same runtime directory.

On 64-bit Windows:

• A 32-bit application generally uses files under C:\Windows\Microsoft.NET\Framework\.
• A 64-bit application generally uses files under C:\Windows\Microsoft.NET\Framework64\.

Do not copy a file from Framework64 into Framework, or the reverse, simply because the filename matches.

To identify the application architecture, check the vendor’s documentation or inspect the program’s installation details. You can also use the application’s executable properties where that information is exposed, but the most reliable evidence is the application installer and its runtime configuration.

Architecture is especially relevant when:

• The error affects only an older 32-bit program.
• The error appears after installing a 64-bit runtime.
• One copy of mscorld.dll exists, but it is in a different framework directory from the one expected by the program.
• Windows reports that the file is “not designed to run on Windows.”

The correct response is to repair or install the appropriate .NET Framework runtime, not to move individual DLLs between directories.

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

Fix 7: Determine whether the application needs .NET Framework 1.1

Some genuinely old programs target .NET Framework 1.0 or 1.1. .NET Framework 4.x is not automatically a drop-in replacement for every application targeting an older CLR. The application configuration and target runtime determine which framework it can use. Microsoft describes runtime targeting in the supportedRuntime documentation.

Look at the path in the error or the PowerShell search result:

C:\Windows\Microsoft.NET\Framework\v1.1.4322\

A reference to v1.1.4322 is evidence that the program may require .NET Framework 1.1. Do not install it merely because mscorld.dll is missing.

For a genuinely old application on a compatible legacy Windows version, use Microsoft’s official .NET Framework 1.1 Redistributable. Check the application’s compatibility requirements and applicable service updates before installation.

On current Windows versions, .NET Framework 1.1 may be obsolete or incompatible. A program that truly requires it may need to run in a supported compatibility environment or virtual machine rather than forcing an unsupported runtime onto the host operating system.

Fix 8: Do not use regsvr32 for this file

Routine advice to run:

regsvr32 mscorld.dll

is not appropriate.

regsvr32 is intended for self-registering COM and OLE DLLs that export the DllRegisterServer entry point. A .NET Framework runtime file is normally repaired by its installer, Windows Features, the .NET Framework Repair Tool, DISM, or the affected application’s installer. Microsoft explains the scope and limitations of regsvr32 in its Regsvr32 troubleshooting guidance.

Registering the file manually will not restore a missing framework payload, repair a corrupted binary, correct a 32-bit versus 64-bit mismatch, or install a missing dependency.

If a separate application specifically identifies a COM component and its vendor instructs you to register that component, follow that vendor’s instructions for that component. That does not make regsvr32 mscorld.dll a valid repair for this error.

Fix 9: Check drivers only when the evidence points to a driver

mscorld.dll is not a hardware driver, and Device Manager does not repair the .NET Framework. Do not update random drivers merely because this DLL error appears.

Use Device Manager only if the same application also reports a hardware, graphics, audio, storage, or chipset problem:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant hardware category.
4. Right-click the device with a warning icon.
5. Select Properties.
6. Read the Device status message.
7. Open the Driver tab.
8. Use Update Driver only when you have a correct driver source from the hardware manufacturer or Windows Update.
9. Restart Windows and retest the application.

Do not remove a working driver as a speculative response to a .NET DLL error.

Manually checking dozens of driver versions can be tedious when a separate hardware problem is involved. Outbyte Driver Updater provides a free scan showing which drivers are stale, while driver installation is handled by the full version; it is optional and does not replace repairing the .NET Framework or reinstalling a program-specific component.

Fix 10: Use System Restore for a recent system-wide failure

System Restore can help when the error began immediately after a software installation, cleanup operation, update, or configuration change and an appropriate restore point exists.

Before using it, understand that System Restore can undo recent updates, installed programs, drivers, and registry changes. It normally does not remove personal documents, photographs, or other personal files.

To open System Restore:

1. Open Control Panel.
2. Select Recovery.
3. Select Open System Restore.
4. Choose a restore point created before the error began.
5. Select Next.
6. Review the affected programs.
7. Select Finish.
8. Allow Windows to restart.

You can also press Win+R, enter rstrui.exe, and select OK. Microsoft documents the feature in its System Restore guidance.

Use System Restore after identifying a plausible restore point. It should not replace repairing the application or installing the correct Microsoft runtime when those options are available.

If the error still appears

Record the following before escalating:

• The complete error text.
• The executable that displays the message.
• The full path shown in the error.
• Whether the error affects one application or several.
• Your Windows edition and build.
• Whether Windows is 32-bit or 64-bit.
• Whether Framework or Framework64 appears in the path.
• Whether the path contains v1.1.4322 or v2.0.50727.
• The result of the PowerShell search.
• The final DISM and SFC messages.
• Any matching Windows Security Protection History entry.

If only one program fails after .NET and Windows repairs, repair or reinstall that program again and inspect its official diagnostic log. The program may have a missing dependency unrelated to mscorld.dll.

If the message says “specified module could not be found” while the named DLL exists, the missing item may be a dependency. Process Monitor or the application vendor’s diagnostic tools can identify which file Windows attempted to load next.

If only one Windows user profile is affected, test the program under a new local Windows account. If it works there, investigate profile permissions, per-user configuration, stale startup entries, or damaged application settings rather than replacing the system runtime.

If malware, disk corruption, or repeated file damage is suspected, run a full Windows Security scan and consider Microsoft Defender Offline. A failing drive or broader Windows installation problem may require a system repair rather than a DLL replacement.

Frequently asked questions

Is mscorld.dll a Windows system DLL?

It is a Microsoft-supplied .NET Framework runtime DLL, but it is not normally a generic System32 or SysWOW64 file. Its expected locations are under the Microsoft .NET Framework directories.

Is mscorld.dll a driver?

No. It is a .NET Framework component. Device Manager is not the normal repair tool.

Which framework should I install first?

On modern Windows, enable or repair .NET Framework 3.5 (includes .NET 2.0 and 3.0) first. This restores the v2.0 runtime family used by many older applications. Do not assume that .NET Framework 4.x alone replaces every v1 or v2-targeted application requirement.

Should I download mscorld.dll by itself?

No. Unofficial DLL downloads can contain malware, the wrong architecture, the wrong servicing level, or a modified file. They can also leave the .NET installation inconsistent. Use Windows Features, Microsoft’s official .NET packages, the .NET Framework Repair Tool, DISM, SFC, or the affected application’s installer.

Should I copy the file into System32?

No. The normal runtime locations are under Microsoft.NET\Framework or Framework64. Copying the file into System32, SysWOW64, or an application directory does not install the framework and may create an architecture mismatch.

Does installing .NET Framework 4.x fix the problem?

Not necessarily. Older applications can target .NET Framework 1.0, 1.1, or the v2.0 runtime family. .NET Framework 4.x is not automatically a drop-in replacement. Check the application’s configuration and enable the runtime it requires.

When is .NET Framework 1.1 relevant?

It is relevant only when an old application specifically targets .NET Framework 1.1 or the error path references v1.1.4322. Use Microsoft’s official package only after checking compatibility with the Windows version.

Why does Windows say the specified module could not be found when the file exists?

The named DLL may be present while one of its dependencies is missing or cannot load. Repair the framework and application, then use the application’s diagnostic log or Process Monitor to identify the dependency.

Does SFC always repair mscorld.dll?

No. SFC repairs protected Windows files when Windows has a matching component source. It is not a replacement for installing .NET Framework or reinstalling an application that owns a private copy.

What is the correct repair order?

Enable or repair .NET Framework 3.5, restart, and test. Then repair or reinstall the affected application. After that, run the .NET Framework Repair Tool, DISM, and SFC. Check Defender quarantine and investigate architecture or legacy .NET 1.1 requirements if the error remains.

How do I know the repair worked?

The repair worked when the affected application starts without the mscorld.dll message and its normal functions operate. Finding a file with the same name is not enough. The application must successfully load the correct runtime and its dependencies.

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.