mscorsn.dll Won’t Load? Find the Right Fix on Windows 10 and 11

mscorsn.dll is a native Microsoft .NET Framework component associated with strong-name signing and verification. If Windows reports that mscorsn.dll is missing, was not found, or could not be loaded, repair the matching .NET Framework rather than downloading the DLL separately.

The correct fix depends on where the error appears. A normal application may need .NET Framework 3.5 or a repaired 4.x installation, while ILMerge, InstallShield, or another developer tool may be searching the wrong Framework directory or using the wrong architecture.

As an Amazon Associate I earn from qualifying purchases.

What mscorsn.dll is and where it belongs

The file description is commonly shown as Microsoft .NET Strong Name Support. It is part of the Microsoft .NET Framework, published by Microsoft Corporation, and is a native Framework component rather than an ordinary managed .NET assembly.

Microsoft lists mscorsn.dll in .NET Framework servicing information, including Framework 1.1 and Framework 4.5.2 packages. The Microsoft .NET Framework 1.1 file list and the Framework 4.5.2 file information show that it is a serviced Framework file.

The normal location is inside a versioned .NET Framework directory, not usually the root of System32:

%WINDIR%\Microsoft.NET\Framework\v2.0.50727\
%WINDIR%\Microsoft.NET\Framework\v4.0.30319\
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\

Framework generally contains 32-bit Framework files, while Framework64 contains 64-bit files. Microsoft documents both directory families as .NET Framework locations.

Version and location guide

What you find	What it usually indicates
Framework\v2.0.50727	Older .NET Framework applications, including applications using the 2.0, 3.0, or 3.5 family
Framework\v4.0.30319	.NET Framework 4.x files used by 32-bit processes
Framework64\v4.0.30319	.NET Framework 4.x files used by 64-bit processes
No result from a file search	The required Framework generation may be missing, or the failing tool may be searching another directory
A file exists but still will not load	The path, architecture, signature, or another native dependency may be wrong

There is no single universal mscorsn.dll version or file size. For example, Microsoft lists version 1.1.4322.2407 at 77,824 bytes for one Framework 1.1 package. A Framework 4.5.2 update lists version 4.0.30319.36415 in two x64 package variants with sizes of 26,272 and 25,760 bytes. These are examples from specific serviced packages, not values that every legitimate installation must match.

Microsoft’s strong-name hosting documentation also says that the strong-name hosting library is included as a resource in MSCorEE.dll. This matters because an mscorsn.dll error does not always mean that an ordinary .NET application directly loads this file. An old build tool, an incorrect native binding, or a Framework path problem can produce the same message.

Error messages this guide covers

You may see one of these messages:

Unable to load DLL 'mscorsn.dll': The specified module could not be found.
(Exception from HRESULT: 0x8007007E)

mscorsn.dll cannot be located on your system.
You can set the path to mscorsn.dll using Tools | Options.

The second message is associated with an InstallShield build configuration. It is not the usual message shown when a consumer application starts.

Generic Windows loader messages may also appear:

The code execution cannot proceed because mscorsn.dll was not found.
Reinstalling the program may fix this problem.

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

A “not designed to run on Windows” message usually points to a corrupt, incompatible, invalid, or wrong-architecture binary. It does not by itself identify the precise cause.

Before changing anything, note whether the error appears when:

• Starting a normal application or game
• Launching an older application that may require .NET Framework 3.5
• Running ILMerge or another assembly-merging tool
• Building an installer with InstallShield
• Signing or packaging an assembly
• Running a setup program
• Starting only one damaged application

That distinction determines which fixes are most useful.

Fix 1: Restart Windows and install pending updates

A failed Framework update or incomplete restart can leave related files in an inconsistent state.

1. Save your work.
2. Select Start.
3. Select Power.
4. Choose Restart.
5. After Windows starts, open Settings.
6. Select Windows Update.
7. Select Check for updates.
8. Install available updates.
9. Restart again if Windows requests it.
10. Test the application or build tool.

If the error began immediately after an interrupted update, continue with the .NET Framework Repair Tool and the Windows component repair commands below.

Fix 2: Run Microsoft’s .NET Framework Repair Tool

This is the best first repair step when a normal application reports that mscorsn.dll is missing or cannot be loaded.

Microsoft provides the official .NET Framework Repair Tool. The documented current release is version 1.5.

Repair with the graphical tool

1. Download the repair tool from Microsoft.
2. Open your Downloads folder.
3. Right-click NetFxRepairTool.exe.
4. Select Run as administrator.
5. Accept the license terms.
6. Allow the tool to inspect the installed Framework.
7. Accept the recommended repairs.
8. Restart Windows when prompted.
9. Start the affected program again.

If the tool reports that it could not repair everything, install pending Windows updates and try the official Framework installer in the next section.

Run the repair tool from Command Prompt

To run the documented quiet repair:

NetFxRepairTool.exe /q

For a targeted .NET Framework 4 repair:

NetFxRepairTool.exe /q /r .net4

For both the 3.5 and 4.x families:

NetFxRepairTool.exe /q /r .net35;.net45

Run these commands from the directory containing NetFxRepairTool.exe, or provide its full path.

A successful repair should allow the affected program to start without the same mscorsn.dll error. If only one application still fails, the application itself may be damaged.

Fix 3: Install or enable the Framework generation the program requires

Installing a newer Framework does not automatically satisfy every application that requires the older 2.0, 3.0, or 3.5 family.

.NET Framework 3.5 includes .NET Framework 2.0 and 3.0. An older program may therefore fail even when .NET Framework 4.8.1 is already installed.

Enable .NET Framework 3.5 through Windows Features

On supported Windows 10 and earlier Windows 11 releases:

1. Open Start.
2. Search for Windows Features.
3. Open Turn Windows features on or off.
4. Select .NET Framework 3.5 (includes .NET 2.0 and 3.0).
5. Select OK.
6. Allow Windows to download or install the required files.
7. Restart if prompted.
8. Test the application again.

Microsoft’s Framework 3.5 installation instructions explain the available installation methods.

On Windows 11 version 26H1, build 28000, and later, Microsoft says .NET Framework 3.5 is no longer supplied as a normal Windows component. Those systems require the version-specific standalone installer described in Microsoft’s .NET Framework 3.5 Windows 11 FAQ.

Do not assume that installing 4.8.1 replaces 3.5. The two Framework families serve different application compatibility requirements.

Install or repair .NET Framework 4.x

For applications that require .NET Framework 4.x, use Microsoft’s .NET Framework 4.8.1 download page.

The page provides:

• A web installer that downloads files during setup
• An offline installer named NDP481-x86-x64-AllOS-ENU.exe
• A Developer Pack intended for building applications

For a program that only needs to run, choose the Runtime or offline installer rather than the Developer Pack.

.NET Framework 4.5 through 4.8.1 are in-place updates within the .NET Framework 4 family. Installing 4.8.1 does not install .NET Framework 3.5.

After installing or repairing Framework 4.x:

1. Restart Windows.
2. Start the failing program.
3. If it still fails, repair the Windows component store and system files.
4. If only that application fails, repair or reinstall the application.

Fix 4: Check which .NET Framework 4.x release is installed

You can check the Framework 4.x release value in the registry with PowerShell.

1. Open Start.
2. Search for PowerShell.
3. Right-click Windows PowerShell.
4. Select Run as administrator.
5. Run:

Get-ItemPropertyValue `
  -LiteralPath 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' `
  -Name Release

Microsoft documents this registry value and its release-key mapping in How to determine which .NET Framework versions are installed.

If the command reports that the registry path or value does not exist, the full .NET Framework 4 installation may be absent or damaged. That does not prove that .NET Framework 3.5 is absent, because the two families are checked differently.

Fix 5: Locate and inspect every copy of mscorsn.dll

A file search helps determine whether the problem is absence, path selection, architecture, or file integrity.

Search from Command Prompt

Open Command Prompt and run:

dir "%WINDIR%\Microsoft.NET\Framework*\v*\mscorsn.dll" /s /b

This searches the versioned Framework and Framework64 directories.

A missing result does not prove that all .NET Framework components are absent. The application may require another Framework generation, or a developer tool may be searching a path different from the one Windows uses.

Search and inspect from PowerShell

Run:

Get-ChildItem "$env:windir\Microsoft.NET" -Filter mscorsn.dll -Recurse -ErrorAction SilentlyContinue |
  Select-Object FullName, Length,
    @{Name='FileVersion';Expression={$_.VersionInfo.FileVersion}},
    @{Name='Signature';Expression={(Get-AuthenticodeSignature $_.FullName).Status}}

Review these fields:

• FullName: the exact directory
• Length: the file size
• FileVersion: the installed file version
• Signature: the Authenticode signature status

A legitimate Framework file should be in a versioned Microsoft .NET Framework directory. If a copy appears in a Downloads folder, a temporary directory, or an unexpected application folder, do not use it as a replacement without first checking its origin and signature.

To inspect a particular file in more detail:

1. Right-click the file.
2. Select Properties.
3. Open the Digital Signatures tab.
4. Select the signer.
5. Select Details.
6. Confirm that Windows reports a valid signature.

A file with the correct name can still be corrupt, modified, or from the wrong architecture.

Fix 6: Repair Windows component corruption with DISM and SFC

If the Framework installation is damaged, Windows component-store repair may restore the files needed for Framework repair.

Microsoft recommends running DISM before System File Checker.

1. Open Start.
2. Search for Command Prompt.
3. Right-click it.
4. Select Run as administrator.
5. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish.
2. Then run:

sfc /scannow

1. Restart Windows.
2. Test the affected program.

Do not close the window while either scan is running. If DISM reports an error, install pending Windows updates and run the command again. If SFC reports that it could not repair some files, restart and repeat the repair sequence before moving to System Restore or an in-place Windows repair.

If manually comparing component versions and repeating SFC/DISM leaves you unsure what changed, Outbyte PC Repair can show the problems found by its free scan; repair is performed by the full version. It is optional, and it does not replace repairing the specific .NET Framework or reinstalling an application that owns the failure.

Repair a failed .NET Framework 3.5 feature installation

If Windows cannot download the .NET Framework 3.5 files, use matching Windows installation media.

Replace X: with the drive letter of installation media from the same Windows build:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:X:\sources\sxs /LimitAccess

Do not use the sources\sxs directory from a different Windows build. A mismatched source can produce additional servicing errors.

Microsoft provides more guidance in its .NET Framework 3.5 installation-error documentation.

Fix 7: Repair or reinstall the affected application

If .NET Framework repairs complete successfully but only one program still reports mscorsn.dll, the application installation may be damaged.

Try these steps in order:

1. Open the application’s own settings or launcher.
2. Choose Repair, Scan, or Repair installation if available.
3. Restart Windows.
4. Test the program.
5. If it still fails, uninstall it.
6. Restart Windows.
7. Reinstall it from the original vendor or launcher.
8. Test again.

For a game, use the launcher’s file-verification feature rather than copying a DLL into the game directory.

The usual Steam path is:

Library → right-click the game → Properties → Installed Files →
Verify integrity of game files

The usual Epic Games Launcher path is:

Library → three dots beside the game → Manage → Verify

There is no verified basis for assuming that a particular commercial game regularly requires mscorsn.dll. Ask for the exact game executable and full error path before treating this as a game-specific dependency.

Fix 8: Check Windows Security quarantine

Antivirus software can quarantine or remove a Framework file. This is a possible cause, but it should be verified rather than assumed.

1. Open Start.
2. Search for Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for an event involving mscorsn.dll.
7. Expand the event.
8. Confirm the original file path.
9. Check whether the file was in a Microsoft .NET Framework directory.
10. Scan the computer.

Microsoft explains Protection History in its Windows Security documentation.

Do not immediately restore a quarantined file just because its filename is mscorsn.dll. Confirm the original path and digital signature first. Reinstalling the official Framework from Microsoft is safer than restoring a questionable copy.

If you determine that the file was a false positive:

1. Confirm that it came from the expected Framework directory.
2. Confirm that Microsoft is shown as the signer.
3. Run a full security scan.
4. Restore or allow the file only after the false-positive determination is justified.

Microsoft warns that allowing a detected threat can expose the device, and that broad exclusions reduce protection.

Fix 9: Check the correct Framework architecture

A 32-bit program and a 64-bit program can use different Framework directories.

Check the computer architecture:

1. Open Settings.
2. Select System.
3. Select About.
4. Review System type.

Then identify the failing process:

• A 32-bit tool commonly uses %WINDIR%\Microsoft.NET\Framework\.
• A 64-bit tool commonly uses %WINDIR%\Microsoft.NET\Framework64\.
• A 32-bit developer tool running on 64-bit Windows may still require the Framework directory.
• A 64-bit tool may require Framework64.

Do not copy an x86 file into a 64-bit Framework directory or copy an x64 file into a 32-bit directory. Microsoft’s Framework servicing tables include distinct x64 variants with different sizes, confirming that the architecture is not interchangeable.

Fix 10: Correct the path in ILMerge or InstallShield

This is the most important branch when the error happens during development or installer creation.

InstallShield

InstallShield can report that mscorsn.dll cannot be located and provide a setting under Tools and Options. This is a build configuration problem, not necessarily a broken Windows installation.

Check the configured Framework path:

%WINDIR%\Microsoft.NET\Framework\v4.0.30319

Use Framework64 only when the InstallShield process is actually 64-bit and the build requires the 64-bit Framework directory.

After correcting the path:

1. Close InstallShield.
2. Reopen it with the required permissions.
3. Rebuild the installer.
4. Confirm whether the same build error appears.

ILMerge and strong-name signing

ILMerge can fail while signing or merging assemblies when its native strong-name binding cannot locate the required Framework component. The file may exist in another Framework directory and still be invisible to the tool.

Check:

• The ILMerge executable path
• The target Framework
• The /targetplatform setting
• Whether the process is 32-bit or 64-bit
• Whether the configured Framework directory matches that architecture
• Whether the signing step is the point at which the error occurs

If the tool is targeting an older Framework, do not automatically point it at the newest directory. Match the tool’s target runtime and architecture first.

A build-tool error can therefore be fixed by correcting the path or target platform without reinstalling Windows.

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

Fix 11: Investigate a missing dependency when the file exists

Windows can show “module could not be found” even when the named DLL is physically present. The loader may be unable to load another native dependency required by that DLL.

If the PowerShell search finds mscorsn.dll, collect:

Full error text
Failing executable name and path
Windows version and architecture
Installed Framework versions
Exact mscorsn.dll path
File version and size
Digital signature status
Whether the failure is in a consumer app or build tool

Then check:

1. Is the failing program 32-bit or 64-bit?
2. Is it searching Framework or Framework64?
3. Does the file have a valid Microsoft signature?
4. Did the error begin after an update, cleanup utility, or antivirus action?
5. Does another application fail, or only this one?
6. Is the failure during launch, assembly merging, signing, or installer building?

If a developer tool is responsible, its own logs and path settings are often more useful than reinstalling the entire operating system.

Fix 12: Update a driver only when the full error identifies one

mscorsn.dll is not a display, audio, chipset, or DirectX driver. Driver repair is a low-probability path unless the complete error also identifies a separate driver DLL or the problem includes broader hardware-related symptoms.

If a separate driver is named:

1. Right-click Start.
2. Select Device Manager.
3. Expand the device category named in the error.
4. Right-click the device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows.
8. Test the application.

You can also check:

1. Open Settings.
2. Select Windows Update.
3. Select Advanced options.
4. Select Optional updates.
5. Open Driver updates.
6. Install only the driver relevant to the identified hardware.

If checking drivers one by one is taking you through a long list of versions, Outbyte Driver Updater can show which driver updates its scan finds; driver installation is performed by the full version. It is optional and should not replace Framework repair when the full error names only mscorsn.dll.

DirectX redistributables and Visual C++ Redistributables are separate from the .NET Framework. The DirectX June 2010 package restores legacy DirectX side-by-side libraries, not .NET Framework files. Install it only when the full error names a DirectX component.

Fix 13: Use System Restore after a recent system change

System Restore is useful when the error began immediately after:

• A Windows update
• A cleanup utility
• A Framework installation
• An application installation
• A security-software action

To open it:

1. Press Windows key + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Choose a restore point dated before the problem began.
3. Review the affected programs.
4. Start the restore.
5. Restart Windows.
6. Test the application.

Microsoft says System Restore rolls back system files, settings, updates, drivers, and installed programs while normally preserving personal files. More information is available in Microsoft’s System Restore documentation.

Fix 14: Repair-install Windows as a last resort

If DISM, SFC, Framework repair, and application reinstallation do not help, Windows itself may have deeper component-store damage.

On supported Windows 11 systems:

1. Open Settings.
2. Select System.
3. Select Recovery.
4. Find Fix problems using Windows Update.
5. Select Reinstall now.
6. Follow the prompts.

Microsoft says this reinstalls the current Windows version while preserving apps, files, and settings. See Fix issues by reinstalling the current version of Windows.

If that option is unavailable, use Windows installation media and select Keep personal files and apps for an in-place repair. Microsoft describes this process in its installation-media repair instructions.

What not to do

Do not download mscorsn.dll from a random DLL website

A loose DLL download can contain malware, the wrong Framework generation, the wrong architecture, or a modified binary. Even a clean file may not fix the underlying problem if Windows is missing another dependency or the application is searching the wrong directory.

Use Microsoft’s official .NET Framework downloads and repair tools instead.

Do not copy the file into System32, SysWOW64, or the application folder

Framework files are versioned and serviced as a set. The correct location depends on the Framework generation and process architecture.

Do not copy mscorsn.dll from another PC, a backup with unknown provenance, or an archive. Defensible restoration sources are an official Microsoft installer, an official Windows image, System Restore, or a system backup.

Do not use regsvr32 as a general DLL repair command

regsvr32 is intended for DLLs that expose COM self-registration functions such as DllRegisterServer. It is not a general-purpose repair tool.

Registering mscorsn.dll is not the normal fix. Repair it through the .NET Framework installer, Windows servicing, or the developer tool’s configuration. Microsoft documents the command in its regsvr32 reference and explains COM self-registration separately.

Do not delete other Framework files to force a reinstall

Manual deletion can make the Framework installation less repairable. Use the official repair tool, Framework installer, DISM, and SFC instead.

Frequently asked questions

Is mscorsn.dll a Windows system DLL?

It is a Microsoft .NET Framework component installed under versioned Framework directories. It is not normally a standalone file that should be downloaded into System32.

Does mscorsn.dll belong to .NET Framework 3.5 or 4.8.1?

The file appears in multiple serviced Framework generations, and there is no single universal version or size. The application or tool’s target Framework determines which installation matters.

.NET Framework 4.8.1 does not automatically install the older .NET Framework 3.5 family.

Why does the error say the module is missing when the file exists?

The process may be searching a different Framework directory, using the wrong architecture, or failing to load another native dependency. A present filename does not prove that the Windows loader can load it.

Should I put mscorsn.dll in the game folder?

No. Repair or reinstall the game and the required .NET Framework. If the game launcher supports file verification, use that feature.

Is mscorsn.dll a managed .NET assembly?

It is a native Framework component associated with strong-name support. Microsoft’s .NET 4 hosting documentation also notes that the strong-name hosting library is included as a resource in MSCorEE.dll, so an application does not necessarily load mscorsn.dll directly.

Will DirectX or Visual C++ Redistributable repair fix it?

Not normally. DirectX, Visual C++, and .NET Framework are separate components. Use the full error to determine which runtime is actually missing.

Should I register mscorsn.dll with regsvr32?

No. regsvr32 applies to COM self-registering DLLs. Use .NET Framework repair, Windows servicing, or the affected tool’s path configuration.

What should I provide if the problem continues?

Record the complete error, the failing executable and path, Windows architecture, installed Framework versions, every mscorsn.dll path found, its version and size, its signature status, and whether the failure occurs in an application or a build tool. That information separates a damaged Framework installation from a path, architecture, dependency, quarantine, or application-specific problem.

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.