mscorcfg.dll Load Errors: Repair the Legacy .NET Configuration Tool

“The program can’t start because mscorcfg.dll is missing from your computer.”

When Windows says it could not load mscorcfg.dll, the correct repair is usually a missing or damaged legacy .NET Framework configuration component, not a replacement file copied into System32.

As an Amazon Associate I earn from qualifying purchases.

Which fix applies to you

Use the wording of the error to choose the right starting point.

• mscorcfg, Version=2.0.0.0 cannot be loaded: Install or repair the matching .NET Framework 2.0 SDK, Visual Studio SDK component, or application prerequisite. Installing only the .NET Framework runtime may not install this assembly.

  #1 Best Overall

  

  Windows 11 Troubleshooting and User Guide: Step-by-Step Solutions to Fix Errors, Optimize Performance, and Customize Your PC

  $18.99

  Buy on Amazon

• mscorcfg.dll was not found: Repair the affected application first, then repair or reinstall the matching legacy .NET Framework component.

• Error 1304. Error writing to file: mscorcfg.dll: Treat this as an installer access, file-lock, antivirus, disk-space, or permissions problem. It is not the same as an application reporting a missing DLL.

• Bad Image, error 0xc000012f, or an entry-point error: Reinstall the exact official framework or SDK package and check for a version or architecture mismatch.

  ×

  Do these 3 things before closing this tab:

  1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
  Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

• The file disappeared after a security scan: Check Windows Security Protection history and verify whether the file was quarantined.

• Several unrelated Windows components fail: Repair the Windows component store with DISM, then run SFC.

Do not download mscorcfg.dll from a random DLL website. A loose file may have the wrong framework generation, architecture, strong-name identity, dependencies, or malicious modifications. It can also hide the actual problem: a missing SDK, incomplete application installation, or damaged assembly registration.

Use the affected application’s original installer, an official Microsoft package, Windows Features, Windows Update, or Microsoft’s .NET Framework Repair Tool.

What mscorcfg.dll actually is

mscorcfg.dll is a genuine Microsoft .NET Framework assembly from Microsoft Corporation. Its assembly name is mscorcfg, and its documented namespace is Microsoft.CLRAdmin.

It belongs to the legacy .NET Framework Configuration and CLR Administration tooling. The related Microsoft Management Console entry point is usually:

mscorcfg.msc

The .msc file is the MMC snap-in definition. mscorcfg.dll is the managed assembly that supplies the configuration interface and administration functionality behind that snap-in. Related components can include mscormmc.dll, configuration files, GAC registration, and other files installed with the same framework or SDK component.

The historical file description, “Administrative tool for .NET UI,” is useful for identifying the file but does not mean that it is a general Windows user-interface library.

mscorcfg.dll is not a normal Windows system DLL. It is a legacy .NET Framework administration component. It should not normally be restored by copying a file into:

C:\Windows\System32
C:\Windows\SysWOW64

Microsoft documents the Microsoft.CLRAdmin assembly as mscorcfg.dll for .NET Framework 1.0 and 1.1. The .NET Framework 2.0 configuration tool was associated with the .NET Framework 2.0 Software Development Kit rather than only the runtime.

Why the .NET runtime may not be enough

This is the most important distinction in the repair process.

The .NET Framework runtime allows applications to execute managed code. The .NET Framework SDK supplied additional developer and administration tools, including the .NET Framework Configuration tool in the relevant legacy generation.

Therefore, installing .NET Framework 2.0 or enabling .NET Framework 3.5 does not automatically prove that mscorcfg.dll is installed. .NET Framework 3.5 includes the older CLR 2.0 layer, but the separate SDK administration tool may still be absent.

The same principle applies to .NET Framework 4.x. Installing .NET Framework 4.8 does not recreate every .NET Framework 2.0 SDK tool, and .NET Framework 4.x is a separate in-place generation from the older 2.0, 3.0, and 3.5 family.

Microsoft’s .NET Framework version and dependency documentation explains these generation differences.

Check the exact error before repairing anything

The requesting process and assembly version determine the correct package.

Assembly-loading error

A typical error looks like this:

Error while accessing the .NET assembly.
Could not load file or assembly ‘mscorcfg, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies.
The system cannot find the file specified.

This points toward a missing assembly, wrong assembly version, incorrect location, or missing dependency. If the requested version is 2.0.0.0, look for the .NET Framework 2.0 SDK or a vendor package that includes its configuration tool.

Generic missing-file error

Windows may display wording such as:

This application has failed to start because mscorcfg.dll was not found.

or:

The program can’t start because mscorcfg.dll is missing from your computer.

This usually means that the application cannot find a required component. It does not prove that the file belongs in System32.

Installer write error

An installer may report:

Error 1304. Error writing to file: mscorcfg.dll.
Verify that you have access to that directory.

This is primarily a Windows Installer problem. The file may be locked, quarantined, blocked by security software, inaccessible because of permissions, or unavailable from the installer source.

Bad Image error

A loader error may look like:

program.exe - Bad Image
...\mscorcfg.dll is either not designed to run on Windows
or it contains an error.
Error status 0xc000012f.

Treat this as a corrupt, incompatible, or mismatched binary. Do not overwrite it with a file downloaded from a third-party site.

Fix 1: Repair or reinstall the affected application

Start here when only one old program fails.

An application installer may have included the .NET configuration assembly, a specific SDK component, or a private registration entry. If that installation is incomplete, repairing the application is more reliable than repairing Windows globally.

Use the installed-app repair option

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

If there is no Repair option:

1. Press Windows + R.
2. Enter:

text
appwiz.cpl

1. Press Enter.
2. Select the affected application.
3. Choose Change, Modify, or Repair.
4. Follow the installer prompts.
5. Restart Windows.

If repair does not work

Use the original installer or the software vendor’s supported installation package. Choose a complete installation when the installer offers separate .NET, SDK, developer, testing, or administration components.

Do not remove only mscorcfg.dll and copy another copy into the application folder. The application may also need mscorcfg.msc, mscormmc.dll, configuration files, GAC registration, or other dependencies.

The repair worked if the application launches without the assembly error and its .NET module or configuration function opens normally.

Fix 2: Install the matching legacy .NET SDK component

This is the most likely fix when the message requests:

mscorcfg, Version=2.0.0.0

The .NET Framework 2.0 configuration tool was supplied with the .NET Framework 2.0 Software Development Kit. A runtime-only installation can leave the application unable to find mscorcfg.dll.

Look for one of these supported sources:

• The original application installer or prerequisite media.
• A matching Visual Studio SDK component.
• A legacy Windows SDK package that explicitly supports the application.
• Microsoft’s official documentation and download pages for the relevant framework generation.

Microsoft’s current .NET Framework downloads page does not provide a standalone current mscorcfg.dll download. The historical .NET Framework 2.0 SDK download is no longer available at its old Microsoft Download Center address, so do not substitute a loose DLL from an unofficial archive.

The official Windows SDK for Windows 7 and .NET Framework 4, version 7.1 is a legacy package that targeted older .NET Framework generations. Use it only when the affected application or vendor documentation supports that SDK and the installer is appropriate for the computer.

Install the component from original media

1. Locate the application, Visual Studio, or SDK installation media.
2. Run setup.exe or the vendor’s installer.
3. Select Modify, Change, or Custom installation.
4. Enable the .NET Framework SDK, Visual Studio SDK, configuration tool, or developer tools component if listed.
5. Complete the installation.
6. Restart Windows.
7. Launch the original program again.

If the installer fails while writing the file, stop treating the problem as a missing-DLL error and follow the Error 1304 section below.

Fix 3: Enable the required .NET Framework runtime

Enable .NET Framework 3.5 when the application requires the older 2.0, 3.0, or 3.5 runtime layer. This may restore a missing runtime dependency, but it does not guarantee that the separate SDK configuration tool will be installed.

Enable .NET Framework 3.5

1. Press Windows + R.
2. Enter:

text
optionalfeatures

1. Press Enter.
2. Tick .NET Framework 3.5 (includes .NET 2.0 and 3.0).
3. Select OK.
4. Choose Let Windows Update download the files for you if prompted.
5. Restart Windows.
6. Test the application.

If Windows cannot download the feature files, install pending Windows updates and try again. On managed computers, the organization may need to provide the Windows component source.

Check the .NET Framework 4.x installation

On some Windows installations, .NET Framework 4.x is included as an operating-system component rather than a separately selectable feature.

1. Open Control Panel.
2. Select Programs.
3. Select Turn Windows features on or off.
4. Review the available .NET Framework entries.
5. Enable the required feature if it is present.
6. Select OK and restart Windows.

Do not assume that enabling .NET Framework 4.x will restore a .NET Framework 2.0 SDK assembly. If the error names Version=2.0.0.0, continue with the matching SDK or application repair.

Fix 4: Find out whether the assembly exists

Before reinstalling anything, check the locations where historical installations placed the file.

Typical historical locations include:

%WINDIR%\Microsoft.NET\Framework\v1.0.3705\
%WINDIR%\Microsoft.NET\Framework\v1.1.4322\

The file may also have been installed in the .NET Framework Global Assembly Cache or in an SDK directory such as:

...\SDK\v2.0\Bin

The exact path varies by framework generation, SDK, Visual Studio installation, application, and Windows architecture.

Open PowerShell and run:

Get-ChildItem "$env:windir\Microsoft.NET\Framework" -Directory |
  Select-Object -ExpandProperty Name

Get-ChildItem "$env:windir\Microsoft.NET\Framework64" -Directory |
  Select-Object -ExpandProperty Name

Then search likely framework and SDK locations:

Get-ChildItem "$env:windir\Microsoft.NET",
              "$env:ProgramFiles\Microsoft.NET",
              "${env:ProgramFiles(x86)}\Microsoft.NET" `
              -Filter mscorcfg.dll -File -Recurse -ErrorAction SilentlyContinue

If the command returns a path, do not automatically copy that file elsewhere. Check whether it belongs to the same framework generation and whether the failing application expects that assembly version.

Check the GAC

If the Global Assembly Cache tool is installed, open a Visual Studio Developer Command Prompt and run:

gacutil -l mscorcfg

Microsoft documents gacutil -l for viewing GAC contents. Microsoft also states that Gacutil is intended for development purposes and should not be used to install production assemblies.

A file being visible in the GAC does not mean that manually creating GAC folders or copying files into them is safe. Use the original Windows Installer, SDK installer, or application installer to repair production registration.

Fix 5: Diagnose an assembly-binding failure with Fuslogvw

Sometimes the message names mscorcfg.dll, but the actual missing item is one of its dependencies or the application is requesting the wrong version.

Use the Assembly Binding Log Viewer when the application reports a specific assembly version or says that one of the dependencies could not be loaded.

1. Open the Visual Studio Developer Command Prompt as Administrator.
2. Enter:

text
fuslogvw

1. In the viewer, select Settings.
2. Enable logging for failed assembly binds.
3. Choose a log location with enough free space.
4. Reproduce the application error.
5. Return to Fuslogvw.
6. Refresh the log list.
7. Open the failed bind entry.
8. Review the requested version, probing paths, and dependency failure.

Microsoft’s Fuslogvw documentation explains how to interpret these logs.

The result tells you whether the problem is:

• the assembly is not installed;
• the application requests a different version;
• the file is in an unexpected location;
• a dependency is missing;
• the assembly cannot be loaded because of architecture or corruption.

Disable binding-failure logging after troubleshooting because the logs can consume disk space.

Fix 6: Resolve Error 1304 when the installer cannot write the file

If the error says:

Error 1304. Error writing to file: mscorcfg.dll.

follow this sequence.

Restart and close locking programs

1. Save your work.
2. Restart Windows.
3. Do not open the failing application after signing in.
4. Close Visual Studio, MMC consoles, TestStand, setup programs, and developer tools.
5. Run the official installer again.
6. Right-click the installer.
7. Select Run as administrator.

A process that has loaded the old assembly can prevent the installer from replacing it.

Check storage and permissions

1. Open File Explorer.
2. Select This PC.
3. Check the free space on the Windows drive.
4. Make sure the installer source is still available.
5. Avoid running the installer from a disconnected network location.
6. If the installer is on removable media, copy it to a local folder and retry.
7. Confirm that the account has local administrator rights.

Do not take ownership of framework directories or loosen permissions on Windows folders merely to force the installation through.

Check Windows Security

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Protection history.
4. Look for an event involving the application, installer, or mscorcfg.dll.
5. If the file came from a verified Microsoft or vendor installer, follow the organization’s security policy before restoring or allowing it.
6. Re-run the official installer after resolving the quarantine event.

Microsoft notes that a restored quarantined file may be detected again. If the file’s origin is uncertain, reinstall the official package instead of restoring it.

Fix 7: Repair damaged .NET Framework files

Use Microsoft’s .NET Framework Repair Tool when multiple .NET applications fail or the framework installation appears damaged.

1. Download the tool from Microsoft.
2. Right-click the downloaded file.
3. Select Run as administrator.
4. Accept the license terms.
5. Allow the tool to scan the installed .NET Framework versions.
6. Apply the recommended repair.
7. Restart Windows.
8. Test the original application.

If the repair tool reports that the framework is healthy but the application still requests mscorcfg, Version=2.0.0.0, the missing component is more likely the legacy SDK or application prerequisite.

Manually repeating DISM and SFC can be slow when you do not know which component changed; Outbyte PC Repair can scan and show what it finds, while any repair is performed by the full version. It is optional, and a missing legacy SDK assembly still requires the affected application or original Microsoft prerequisite to be repaired.

Fix 8: Repair Windows components with DISM and SFC

DISM and SFC are useful when Windows itself has component corruption, Windows Update is failing, or several unrelated protected files are damaged. They are not the primary repair for a missing .NET Framework SDK assembly.

Run DISM first, then SFC.

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

text
DISM.exe /Online /Cleanup-image /Restorehealth

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

text
sfc /scannow

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

Microsoft recommends DISM before SFC because DISM can provide the repair source for corrupted Windows components. Follow Microsoft’s System File Checker and DISM guidance if either command reports that it could not complete the repair.

If SFC reports that it found no integrity violations, that does not prove that the .NET 2.0 SDK tool is installed. It only indicates that protected Windows system files were not identified as corrupted.

Fix 9: Check 32-bit and 64-bit compatibility

Historical installer evidence identifies a common .NET 2.0 mscorcfg assembly as an x86, or PE32, assembly. That does not justify guessing between System32 and SysWOW64, and it does not establish that every historical SDK build used the same file arrangement.

A 32-bit assembly cannot be loaded into a 64-bit process and vice versa. The correct architecture is determined by the requesting application and the package that supplied the assembly.

Use these rules:

• Do not copy a 32-bit DLL into System32 or SysWOW64 as a workaround.
• Do not assume that a 64-bit version is required because Windows is 64-bit.
• Do not replace a requested assembly with a file from another framework generation.
• Repair the application or install the SDK component that matches the application.
• Use Fuslogvw when the error requests a particular assembly version or dependency.

Microsoft’s documentation on running 32-bit applications explains the architecture boundary.

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 driver only when the evidence points there

A driver is a low-probability cause of an mscorcfg.dll error. This assembly is not identified as a driver component. Consider a driver repair only when the named failing installer is clearly a hardware or vendor package that bundles an old .NET administration tool.

Update through Device Manager

1. Press Windows + X.
2. Select Device Manager.
3. Expand the category containing the affected device.
4. Right-click the device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Install the offered driver.
8. Restart Windows.
9. Retry the hardware vendor’s application or installer.

If the problem began immediately after a driver update:

1. Open Device Manager.
2. Right-click the affected device.
3. Select Properties.
4. Open the Driver tab.
5. Select Roll Back Driver if the button is available.
6. Restart Windows.

Manually identifying an old chipset or graphics driver can mean hunting versions across several vendor pages; Outbyte Driver Updater can scan and show which drivers are stale, while driver installation is performed by the full version. It is optional and low priority for mscorcfg.dll; the affected application’s prerequisite remains the first repair target.

The driver path worked only if the vendor installer or hardware application now completes and the original mscorcfg.dll error no longer appears.

Fix 11: Use System Restore after a recent change

System Restore is appropriate when the failure began immediately after an update, cleanup utility, application installation, or security event and a suitable restore point exists.

1. Press Windows + R.
2. Enter:

text
rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the error began.
4. Select Scan for affected programs.
5. Review the applications and drivers that may be changed.
6. Select Next.
7. Select Finish.
8. Allow Windows to restart.

Microsoft’s System Restore guidance explains the process and limitations.

System Restore does not replace the need to install a missing SDK. It is useful when a previously working installation was damaged by a recent system change.

Do not use regsvr32 for this repair

regsvr32 is intended for self-registering native or COM DLLs. It is not the normal repair mechanism for this managed .NET assembly.

Running commands such as these is not a correct general fix:

regsvr32 mscorcfg.dll
regsvr32 C:\Windows\System32\mscorcfg.dll
regsvr32 C:\Windows\SysWOW64\mscorcfg.dll

A managed assembly is normally installed and registered through its framework or application installer, often involving the Global Assembly Cache. Managed COM registration, when genuinely required by a particular application, uses the appropriate version of Regasm.exe, not an arbitrary regsvr32 command. Microsoft documents this distinction in its Regasm guidance.

Do not use Regasm.exe either unless the application’s documentation specifically requires COM registration. Registration alone cannot supply a missing SDK tool or repair an incompatible assembly.

Where historical installations may contain the file

Depending on the framework generation and installer, historical copies may have appeared in:

%WINDIR%\Microsoft.NET\Framework\v1.0.3705\
%WINDIR%\Microsoft.NET\Framework\v1.1.4322\

Other possible locations include:

The .NET Framework Global Assembly Cache
A .NET Framework SDK Bin directory
A Visual Studio SDK directory
An application-specific installation directory

A documented .NET 2.0 SDK-related location used by an older installation was similar to:

Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin

These are historical examples, not a promise that every computer uses the same path. The absence of the file from one directory does not prove that the installation is broken, and its presence in one directory does not prove that it matches the requesting application.

Legacy Windows compatibility

.NET Framework 1.0 and 1.1 are legacy technologies. Some applications built for those generations may not run correctly on current Windows versions even after the file is restored.

If the application is business-critical:

• Check whether the vendor has a newer application release.
• Use the vendor’s supported compatibility instructions.
• Preserve the original installer and prerequisites.
• Consider an isolated legacy virtual machine when the application cannot be upgraded.
• Do not force obsolete framework files into current Windows system directories.

A successful file copy does not make an old application supported or secure.

How to confirm the repair worked

The repair is complete when all of the following are true:

1. The original program starts without the mscorcfg.dll message.
2. The program’s .NET module, configuration screen, or installer function opens normally.
3. The error does not return after a restart.
4. The relevant application or SDK appears correctly in installed programs.
5. If the application requested Version=2.0.0.0, the matching prerequisite is installed rather than a random file copied into a system folder.
6. If the problem was Error 1304, the official installer completes without another write failure.

If the same error returns, record the exact wording, requested assembly version, executable name, and whether the failure happens at application launch or during installation. That information determines whether the next step is SDK installation, application repair, binding diagnosis, antivirus review, or Windows component repair.

Frequently asked questions

Is mscorcfg.dll a Windows system file?

No. It is a legacy Microsoft .NET Framework administration assembly, not a general Windows System32 DLL.

Should I copy it into System32 or SysWOW64?

No. Do not guess between those directories. Install the matching .NET Framework SDK, Visual Studio SDK component, or application prerequisite.

Is mscorcfg.dll the same as mscorcfg.msc?

No. mscorcfg.msc is the MMC snap-in entry point. mscorcfg.dll is the managed assembly used by the configuration tool. Replacing one does not necessarily repair the other.

Will installing .NET Framework 4.8 fix it?

Not necessarily. If the application requests mscorcfg, Version=2.0.0.0, it may need the older .NET Framework 2.0 SDK or an application-specific prerequisite. .NET Framework 4.x does not automatically recreate every older SDK tool.

Will enabling .NET Framework 3.5 install the file?

It may provide the older CLR 2.0 runtime layer, but it does not guarantee that the separate .NET Framework Configuration SDK tool is installed.

Can I run regsvr32 mscorcfg.dll?

No. regsvr32 is not the normal registration tool for this managed assembly. Repair it through the framework, SDK, or application installer.

Is there a safe standalone download for mscorcfg.dll?

Microsoft’s current .NET Framework download page does not offer a standalone current mscorcfg.dll package. Use the original application media, an official Microsoft SDK or framework package, Windows Features, or the application’s supported repair process.

Why does the error mention mscorcfg.dll when the file exists?

The missing item may be a dependency, the application may request a different assembly version, or the file may be in a location the loader does not probe. Use fuslogvw to inspect the failed bind.

Does this belong to a particular game?

No specific modern game dependency is established here. If a game or launcher shows the error, repair that game through its official installer only after confirming that it is the process producing the message. Do not assume that a generic DLL replacement is appropriate.

Should I reinstall a graphics or chipset driver?

Only when a hardware vendor’s installer is clearly the failing program. mscorcfg.dll is a legacy .NET administration assembly, not a driver file. Repair the affected application or SDK first.

What is the safest long-term fix?

Install the exact framework generation and SDK component requested by the application, or move to a supported application version. Keep the original installer and prerequisites available, apply Windows updates, and avoid loose DLL downloads.

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.