mscories.dll Missing on Windows: Restore the Legacy .NET Component

The exact mscories.dll errors

You may see one of these messages when Windows or an application cannot load the file:

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

#	Preview	Product	Price
1		Microsoft Windows 11 (USB)	$127.70	Buy on Amazon
2		Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |...	$119.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

There was a problem starting mscories.dll. The specified module could not be found.

×Recommended: Fix Windows Errors and Clear Junk Files in Minutes - Free Scan →Free scan · no reinstallRecommended: Update Every Outdated Driver on Your PC in One Scan - Free →Free scan · exact hardware match

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Error loading mscories.dll. The specified module could not be found.

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
• Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
• Make the most of your screen space with snap layouts, desktops, and seamless redocking.
• Widgets makes staying up-to-date with the content you love and the news you care about, simple.
• Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

$127.70

Buy on Amazon

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

mscories.dll is either not designed to run on Windows or it contains an error.

mscories.dll is a genuine Microsoft .NET Framework file, not a Visual C++ Redistributable file. The safest repair is to restore the legacy .NET Framework 3.5 component through Windows or the affected program’s official installer.

The 60-second answer

On most Windows 10 and Windows 11 installations, the first repair to try is:

1. Press Windows + R.
2. Type optionalfeatures.
3. Press Enter.
4. Turn on .NET Framework 3.5 (includes .NET 2.0 and 3.0).
5. Select Let Windows Update download the files for you if prompted.
6. Allow the installation to finish.
7. Restart Windows.
8. Open the application again.

.NET Framework 3.5 provides compatibility for applications built for the older .NET Framework 1.0 through 3.5 family. Installing .NET Framework 4.8 or 4.8.1 alone is not a guaranteed replacement because .NET Framework 4.x does not support applications targeting .NET Framework 1.1 through 3.5. Microsoft documents this compatibility relationship in its .NET Framework 3.5 installation guide.

If Windows cannot enable the feature, repair Windows first with DISM and SFC, then try again. If only one game or application reports the error, repair or verify that program before replacing Windows components.

What mscories.dll actually is

The internal description of mscories.dll is Microsoft .NET IE SECURITY REGISTRATION. Its product is Microsoft .NET Framework, and its publisher is Microsoft Corporation.

The name refers to a legacy registration helper associated with .NET Framework and Internet Explorer security registration. It is a native Windows DLL with Install and Uninstall exports. Microsoft-serviced file lists identify it among .NET Framework 2.0, 3.0, 3.5, or 3.5.1 component files, depending on the Windows release and servicing branch. Microsoft’s historical MS14-057 file list shows the file as part of the .NET Framework servicing payload.

This is why the file may appear during:

• A legacy application’s installation.
• A program’s startup.
• A Windows sign-in operation.
• A .NET Framework feature installation.
• A Windows update or component repair.
• An Active Setup registration step.

It is not normally an application that you launch directly.

Why IE SECURITY REGISTRATION appears in the description

The description is an internal product label, not a warning that the file is a browser add-on or an Internet Explorer executable. Older .NET Framework components used registration steps connected with Windows and Internet Explorer security integration. The wording is therefore technical and dated, but it is consistent with a Microsoft .NET Framework component.

A logon-related command may look similar to this:

Rundll32.exe C:\Windows\System32\mscories.dll,Install

That command invokes the DLL’s Install export through rundll32.exe. Seeing it in Autoruns or during sign-in does not automatically mean that someone launched malware or that the file is a normal startup application.

Is mscories.dll legitimate or dangerous

The file is legitimate when it is restored by Windows or an official Microsoft .NET Framework package and appears in the expected Windows component location.

Common expected locations include:

C:\Windows\System32\mscories.dll
C:\Windows\SysWOW64\mscories.dll

On 64-bit Windows, System32 contains 64-bit system files, while SysWOW64 contains 32-bit system files. The directory names are confusing, but this separation is normal. A 32-bit application may use the 32-bit .NET-related files even when Windows itself is 64-bit.

Do not decide whether the file is safe solely from its filename. A malicious program can use the same filename in an unusual directory. Check the following:

• Is the file under the Windows directory or a trusted Windows component path.
• Is its digital signature valid and issued to Microsoft Corporation.
• Did Windows Features, Windows Update, DISM, SFC, or an official application installer restore it.
• Does Windows Security show that it was quarantined.
• Is the file located in a random application folder, temporary folder, downloads directory, or user profile path.

A copy outside the expected Windows component paths is not automatically malicious, but it deserves verification before being allowed to run.

Why the error can appear in different situations

The same loader message can have several causes. The wording does not identify the root cause by itself.

During application launch

A legacy desktop application may require the .NET Framework 2.0, 3.0, or 3.5 component family. If .NET Framework 3.5 is disabled or incomplete, Windows may fail before the application opens.

The application may display a missing-file message even when the real problem is a missing dependency, an incomplete Windows component store, or an incompatible private copy of the DLL.

During installation

An old installer may enable .NET Framework features or run an Active Setup registration command. If Windows Update cannot download the required payload, installation can stop with a mscories.dll message or a .NET installation error.

In this situation, reinstalling the application repeatedly usually produces the same result. Repair the Windows feature or provide matching Windows installation media first.

During logon

A sign-in error can be connected with an Active Setup registration entry. The command may reference rundll32.exe and mscories.dll,Install.

Do not delete the Active Setup entry just because it appears in Autoruns. Repair the .NET component and verify the file path first. Removing the entry may hide the symptom without restoring the registration that Windows or a legacy program expects.

After Windows Update

A failed update, incomplete servicing operation, or damaged component store can leave .NET Framework files unavailable. The result may be a missing-file error, a “not designed to run on Windows” message, or a feature installation failure.

Run DISM and SFC before attempting several manual replacements.

After antivirus quarantine

Windows Security or another antivirus product may have quarantined the file if it was damaged, modified, or found in an unexpected location. Open the antivirus history and identify the exact path before restoring anything.

Do not restore a file simply because an application says it is missing. Confirm that it came from a trusted Windows path and that its Microsoft signature is valid.

Fix 1: Enable .NET Framework 3.5 in Windows Features

This is the most likely fix on Windows 10 and on Windows 11 releases that still provide .NET Framework 3.5 as a Windows feature.

Exact steps

1. Save your work and close the affected program.
2. Press Windows + R.
3. Type:

text
optionalfeatures

1. Press Enter.
2. In Windows Features, locate .NET Framework 3.5 (includes .NET 2.0 and 3.0).
3. Select the checkbox.
4. If Windows shows two subordinate options, leave the default selections enabled unless your administrator has a specific configuration.
5. Select OK.
6. If Windows asks to download files from Windows Update, choose Let Windows Update download the files for you.
7. Wait for the feature installation to complete.
8. Restart Windows.
9. Launch the application again.

How to tell whether it worked

The application should open without the mscories.dll message. You can also reopen optionalfeatures and confirm that the .NET Framework 3.5 checkbox remains selected.

If the checkbox clears itself, Windows displays an error, or the installation remains stuck, continue with the component repair steps below.

Windows 11 version 26H1 and later

On Windows 11 version 26H1, build 28000, and later, Microsoft changed the delivery model. .NET Framework 3.5 is no longer provided as a Windows optional component in the same way. Use the standalone installer that matches the installed Windows release instead.

Microsoft explains the version-specific process in its .NET Framework 3.5 Windows 11 FAQ and provides the applicable Windows 11 .NET Framework 3.5 installation guidance.

Do not use an installer intended for a different Windows release. The .NET package must match the Windows version and servicing model.

Fix 2: Repair Windows with DISM and SFC

Use this path when .NET Framework 3.5 will not enable, when the message says the file is corrupt or “not designed to run on Windows,” or when Windows has recently experienced an interrupted update.

DISM repairs the Windows component store. SFC then checks protected system files against the repaired component store.

Run DISM

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

bat
DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the operation to reach 100 percent and return a result.
2. Keep the administrator Command Prompt open.

The command may take time and may appear to pause at a percentage. Do not close the window merely because progress is slow.

Run SFC

After DISM completes, run:

sfc /scannow

Wait until SFC reports its result. Common outcomes include:

• Windows Resource Protection did not find any integrity violations: SFC found no protected-file problem.
• Windows Resource Protection found corrupt files and successfully repaired them: restart Windows and test the application.
• Windows Resource Protection found corrupt files but was unable to fix some of them: restart, run DISM again if necessary, and review the CBS log or continue to the matching installation-media method.

Restart Windows after the commands finish. Then enable .NET Framework 3.5 again through Windows Features.

Microsoft’s DISM repair documentation and System File Checker documentation describe these tools and their intended use.

When the manual DISM and SFC cycle becomes repetitive, Outbyte PC Repair can scan for the system issues involved and show what needs attention, while repair actions are performed by the full version. It is optional, and it does not replace the official Windows component repair path when .NET itself is missing.

What success looks like

After restarting, Windows Features should be able to enable .NET Framework 3.5. The application should then launch without the DLL error.

If DISM reports that source files could not be found, use matching installation media rather than copying mscories.dll from another computer.

Fix 3: Install .NET Framework 3.5 from matching Windows media

This method is useful when Windows Update is unavailable, blocked by policy, or unable to download the .NET Framework 3.5 payload.

You need installation media that matches the installed Windows release. A mismatched ISO can create a component state that is unsupported or difficult to service.

Exact steps

1. Obtain Windows installation media for the same Windows release and architecture.
2. Mount the ISO by double-clicking it in File Explorer.
3. Note the drive letter assigned to the mounted media. In the example below, it is D:.
4. Open Command Prompt as administrator.
5. Run:

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

1. Replace D: with the actual mounted-media drive letter.
2. Wait for DISM to finish.
3. Restart Windows.
4. Test the affected application.

Microsoft documents this method in its DISM deployment guide for .NET Framework 3.5.

Important installation errors

Windows feature installation may fail with codes including:

• 0x800F0906
• 0x800F0907
• 0x800F081F
• 0x800F0922

These codes commonly indicate that Windows could not obtain or validate the required .NET Framework source files. Microsoft lists these conditions in its .NET Framework 3.5 installation error guidance.

Check the following before trying again:

• The ISO matches the installed Windows release.
• The sources\sxs directory exists.
• The drive letter is correct.
• The Command Prompt is running as administrator.
• Network or organization policies are not blocking optional-component installation.
• The system has enough free space for servicing.

Fix 4: Repair or reinstall the affected application

If other applications work and only one program reports mscories.dll, the application may be damaged or may contain an incorrect private dependency.

Do not assume that the application is innocent simply because the message names a Windows DLL. A damaged installer, partial update, or private application folder can trigger a generic loader error.

Repair a desktop application

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Find the affected application.
5. Select its three-dot menu.
6. Choose Advanced options if available.
7. Select Repair.
8. Launch the program again.

If Repair is unavailable or does not help, uninstall the application and reinstall it from the publisher’s official installer. Back up application data first if the program stores local projects or profiles.

Repair a game installation

For a game, use the launcher’s file-verification feature before reinstalling the entire game. Verification can restore files removed or corrupted by an interrupted update.

In Epic Games Launcher:

1. Open Epic Games Launcher.
2. Select Library.
3. Find the game.
4. Select the three dots beside the game.
5. Select Manage.
6. Select Verify.
7. Wait for verification to finish.
8. Start the game again.

Steam provides a similar file-verification function through the installed game’s properties. The exact menu wording can vary by client version, but look for Verify integrity of game files or an equivalent option.

If verification restores the game but the error returns, reinstall the game or its official prerequisite package. If only the game fails while Windows applications work, fixing the game installation remains the definitive repair.

Fix 5: Check antivirus quarantine and verify the signature

Use this fix when mscories.dll disappeared after a security scan, when the application worked previously, or when Windows Security reports that a file was removed.

Check Protection History

1. Open the Start menu.
2. Type Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Open the event that mentions the file.
7. Inspect the detected file path and action.
8. Do not restore it yet.

Microsoft’s Protection History guidance explains how Windows Security records detected and quarantined items.

Restore the file only when all of the following are true:

• The file came from the expected Windows component path.
• The file is identified as a Microsoft file.
• The detection is clearly a false positive or a known quarantine event.
• Windows or an official Microsoft installer can restore the component more safely.

Microsoft warns that a restored quarantined file may be detected again until it is explicitly allowed. See Microsoft’s Defender quarantine restoration guidance.

Check the Authenticode signature

Open PowerShell as administrator or as your normal user and run:

Get-AuthenticodeSignature -FilePath "$env:windir\System32\mscories.dll"

For the 32-bit path on 64-bit Windows, check:

Get-AuthenticodeSignature -FilePath "$env:windir\SysWOW64\mscories.dll"

Review the Status and SignerCertificate fields. A valid Microsoft signature supports the file’s origin, but it does not prove that the entire Windows installation is healthy. An unsigned file, an invalid signature, or a file in an unexpected directory is a reason to run a full Microsoft Defender scan and restore the component through Windows.

Microsoft documents this command in Get-AuthenticodeSignature.

Fix 6: Check the correct 32-bit and 64-bit component

A 64-bit Windows installation can contain both 64-bit and 32-bit versions of system and framework components. The application’s architecture determines which side it may load.

The important paths are:

C:\Windows\System32\mscories.dll
C:\Windows\SysWOW64\mscories.dll

Do not copy the file from System32 to SysWOW64, or the other way around, as a guess. Do not overwrite either file with a copy from another computer. The file may need the correct Windows servicing level, language branch, companion files, and component-store registration.

Check whether the files exist

1. Open File Explorer.
2. Browse to C:\Windows\System32.
3. Search for mscories.dll.
4. On 64-bit Windows, browse to C:\Windows\SysWOW64.
5. Check whether a separate copy exists there.
6. Record which path is missing without changing either file.

If the application is 32-bit, its error may involve the 32-bit side even though the operating system is 64-bit. The correct solution remains restoring .NET Framework and Windows components through supported installers and servicing tools.

Fix 7: Consider drivers only when the wider system is unstable

A graphics, storage, chipset, or security-driver problem does not normally explain a standalone mscories.dll error. Do not start by reinstalling every driver.

Driver investigation becomes reasonable when the DLL message appeared alongside:

• Application crashes across unrelated programs.
• Device failures in Device Manager.
• Blue screens or sudden restarts.
• Disk or display errors in Event Viewer.
• A recent driver installation or rollback.
• Windows corruption that returns after repair.

Check Device Manager

1. Right-click the Start button.
2. Select Device Manager.
3. Expand categories related to the symptom, such as Display adapters, Storage controllers, System devices, or Network adapters.
4. Look for a yellow warning icon.
5. Right-click the affected device.
6. Select Properties.
7. Review the General tab for a device status message.
8. Open the Driver tab.
9. Use Update Driver only with a driver from Windows Update or the hardware manufacturer.
10. Restart Windows and retest.

Do not use Device Manager to “register” mscories.dll. Device Manager handles hardware drivers, not .NET Framework registration helpers.

If the driver list is large and you are unsure which versions are stale, Outbyte Driver Updater can scan the installed drivers and identify what needs attention, while driver installation is handled by the full version. It is optional, and a driver update is not a substitute for repairing .NET Framework when this file is the only problem.

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

What not to do

Do not download mscories.dll from a DLL website

Random DLL download sites can provide:

• The wrong Windows servicing version.
• The wrong x86 or x64 architecture.
• A file from a different language or branch.
• A modified or malicious file.
• A file with missing companion components.
• A copy that does not repair the Windows component store.

Even when the downloaded file has the correct name, copying it into System32, SysWOW64, or the application directory may leave the actual .NET installation broken.

Use supported sources instead:

• Windows Features.
• Windows Update.
• Matching Windows installation media.
• Microsoft .NET Framework installers.
• Microsoft’s .NET Framework Repair Tool.
• The affected program’s official installer or launcher verification.
• DISM and SFC.

Microsoft provides the .NET Framework 3.5 SP1 download page, the .NET Framework Repair Tool, and the current .NET Framework 4.8.1 download page.

Do not use regsvr32 for this file

This command is commonly suggested for DLL errors:

regsvr32 mscories.dll

It is generally wrong here. regsvr32 is intended for DLLs that export DllRegisterServer and DllUnregisterServer. mscories.dll is documented with Install and Uninstall exports instead.

Running regsvr32 is likely to produce an error about a missing DllRegisterServer entry point. It does not reinstall .NET Framework, repair the component store, or restore a missing Windows feature.

Windows may invoke this file through rundll32.exe in an Active Setup context, but that does not mean you should manually run:

rundll32 mscories.dll,Install

The official installer and Windows registration process provide the correct context. Manual invocation can create confusing results and does not repair missing dependencies.

Do not install .NET 4.8.1 as a blind replacement

.NET Framework 4.8.1 is a modern supported .NET Framework release for compatible Windows versions, but it is not a guaranteed replacement for applications targeting .NET Framework 2.0, 3.0, or 3.5.

Install or repair .NET Framework 4.8.1 when the application specifically requires it. Restore .NET Framework 3.5 when the legacy application or Windows component requires the 3.5 family. Both framework generations can coexist.

Do not blame Visual C++ automatically

Visual C++ Redistributable repairs files with names such as:

MSVCP*.dll
MSVCR*.dll
VCRUNTIME*.dll

mscories.dll identifies itself as a Microsoft .NET Framework file. Install or repair Visual C++ only when the error also names a Visual C++ runtime or the affected program’s official requirements specifically call for it. The Microsoft Visual C++ Redistributable documentation covers that separate runtime family.

How to identify the real repair path

Use the symptom pattern rather than the filename alone.

Situation	Most likely repair
Several older applications fail	Enable or repair .NET Framework 3.5
Windows Features cannot enable .NET 3.5	Run DISM and SFC, then use matching media
Only one desktop application fails	Repair or reinstall that application
Only one game fails	Verify game files, then reinstall the game if necessary
Error appears at sign-in	Inspect the Active Setup path and repair .NET
File was quarantined	Check Protection History and verify path and signature
“Not designed to run on Windows” appears	Repair the component store with DISM and SFC
File exists only in a random folder	Treat it as untrusted until verified
Error began after a driver or update change	Check Device Manager and Windows repair history
Windows continues corrupting files	Investigate storage, malware, System Restore, or repair reinstall

If .NET Framework Repair Tool is needed

Microsoft’s .NET Framework Repair Tool can help with damaged .NET Framework installations, particularly older .NET Framework 3.5 SP1 and its related .NET 2.0 SP2 and 3.0 SP2 components.

Exact steps

1. Open Microsoft’s .NET Framework Repair Tool download page.
2. Download the tool from Microsoft.
3. Right-click the downloaded file.
4. Select Run as administrator.
5. Accept the license terms.
6. Follow the repair wizard.
7. Apply the recommended repair actions.
8. Restart Windows if prompted.
9. Enable .NET Framework 3.5 again through Windows Features.
10. Test the affected program.

The tool does not guarantee a repair for every current Windows 11 configuration. If your Windows release uses the newer standalone-installer model, use Microsoft’s version-specific .NET Framework 3.5 package instead.

If every repair fails

At this point, collect evidence before making larger changes. Record:

• The complete error text.
• Windows edition, version, and build.
• Whether Windows is x86, x64, or Arm64.
• The application or installer that triggers the message.
• Whether the error occurs at logon or only in one program.
• The full file path named by the error.
• Whether the file exists in System32 or SysWOW64.
• The final DISM result.
• The final SFC result.
• Windows Security Protection History details.
• Event Viewer entries recorded around the failure.

Then proceed in this order.

Test a new Windows profile

A damaged user profile can cause logon registration and application-launch problems.

1. Open Settings.
2. Select Accounts.
3. Select Other users.
4. Choose Add account.
5. Create a temporary local test account.
6. Sign out of the current account.
7. Sign in to the new account.
8. Test the application.

If the application works only in the new profile, the Windows component may be healthy and the original user profile may need repair or migration.

Use System Restore

Use System Restore when the problem began after a recent application, update, driver, or system change.

1. Press Windows + R.
2. Type:

text
rstrui.exe

1. Press Enter.
2. Select an appropriate restore point.
3. Review the affected programs and drivers.
4. Start the restore.
5. Allow Windows to restart.
6. Test the application.

System Restore can revert system files, registry settings, drivers, and installed programs while preserving personal files. It does not replace a backup. Microsoft describes the process in its System Restore guidance.

Reinstall the current Windows version

On supported Windows 11 installations, the recovery settings may include Fix problems using Windows Update.

1. Open Settings.
2. Select System.
3. Select Recovery.
4. Look for Fix problems using Windows Update.
5. Select Reinstall now if available.
6. Follow the prompts.
7. Allow Windows to reinstall the current version while preserving apps, files, and settings.
8. Test .NET Framework and the affected application afterward.

Microsoft explains this repair option in its reinstall-current-version Windows guidance.

If the option is unavailable or the problem persists, an in-place repair installation using matching Windows media may be appropriate. Back up important files first and verify that the selected installation option preserves personal files and applications.

Frequently asked questions

Is mscories.dll part of Windows

It is a Microsoft .NET Framework component commonly installed and serviced with Windows, particularly through the legacy .NET Framework 2.0, 3.0, 3.5, or 3.5.1 component family. It may be absent or inactive when .NET Framework 3.5 is disabled or its payload has been removed.

Is mscories.dll a Visual C++ file

No. It belongs to Microsoft .NET Framework. Visual C++ Redistributable repairs a different group of runtime files.

Does installing .NET Framework 4.8.1 fix the error

Not necessarily. An application targeting .NET Framework 1.1 through 3.5 may require .NET Framework 3.5 specifically. Enable or install the version the application requires.

Should I copy the file into the application folder

No. That can introduce the wrong architecture, servicing build, language branch, or an unsafe file. Repair .NET Framework or the application through official installers.

Should I run regsvr32 mscories.dll

No. This file uses Install and Uninstall exports rather than the DllRegisterServer interface expected by regsvr32.

Why is mscories.dll in Autoruns

It may be referenced by an Active Setup entry that invokes rundll32.exe during registration or logon. Its presence there is not, by itself, evidence of malware. Repair the .NET component before considering any cleanup.

Why are there files in both System32 and SysWOW64

64-bit Windows maintains separate 64-bit and 32-bit system locations. A 32-bit application may require the 32-bit side. Do not swap files between the directories manually.

Can antivirus quarantine a legitimate copy

Yes. A damaged, modified, or unusual copy can be detected even when the filename is legitimate. Check Protection History, inspect the path, verify the Microsoft signature, and prefer restoring the component through Windows servicing.

What if only a game reports the error

Verify the game’s files through its launcher. If verification does not help, repair or reinstall the game and its official prerequisites. Do not download mscories.dll separately.

What is the safest overall repair order

Enable .NET Framework 3.5, repair Windows with DISM and SFC if needed, install from matching media when Windows Update cannot supply the payload, repair the affected application, check antivirus quarantine, and escalate to a new profile, System Restore, or Windows repair reinstall only when the earlier steps do not resolve the 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.