Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If Windows says “Microsoft.AspNetCore.Mvc.Core.dll is missing” or “The code execution cannot proceed because Microsoft.AspNetCore.Mvc.Core.dll was not found,” install or repair the exact ASP.NET Core shared framework that the application targets. Do not download one DLL from a third-party site. First identify the app’s target .NET version and whether it is 32-bit or 64-bit; then install the matching ASP.NET Core Runtime, repair Windows with DISM followed by SFC, and reinstall the application if its private deployment files are damaged.
This error usually indicates a missing, damaged, or incompatible ASP.NET Core framework rather than one isolated file. The correct fix differs for a framework-dependent app, a self-contained app, a failed Windows update, and a broken application installation. The sequence below applies to Windows 11 and Windows 10.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat does Microsoft.AspNetCore.Mvc.Core.dll missing mean?
Microsoft.AspNetCore.Mvc.Core.dll is part of the ASP.NET Core dependency chain. Beginning with .NET Core 3.0, many ASP.NET Core assemblies stopped being published as separate NuGet packages and moved into the Microsoft.AspNetCore.App shared framework. That framework is installed with the .NET SDK or a .NET runtime and contains the supported ASP.NET Core assemblies.
When an application reports this filename, it generally cannot locate the ASP.NET Core framework version or deployment files it was built to use. The filename alone does not identify the required major or minor version. A program targeting one .NET release may not accept an arbitrary newer release, and a 32-bit program cannot be repaired reliably with only a 64-bit installation.
Popular on Amazon
- Spacious Design: Measuring 21.1" wide and 14.1" deep, our lap desk comfortably fits most laptops up to 15.6". Extra room for accessories ensures convenience.
- Enhanced Functionality: Packed with handy features, including a 5x9" precision tracking mouse pad and a built-in phone slot for seamless work or video calls. Plus, enjoy ergonomic support with the integrated cushioned wrist rest.
- Cool Comfort: Enjoy a stable surface with our lap desk's dual bolster cushion, designed for comfort and airflow, keeping your lap cool during extended use.
- Durable Surface: Work with confidence on our lap desk's solid surface, featuring a sleek black carbon color, ensuring optimal air circulation to prevent your laptop from overheating.
- On-the-Go Convenience: With an integrated handle and lightweight design (2.8 lbs), our lap desk is portable for travel or moving around the house, offering flexibility in any space.
The safest approach is therefore to restore the complete, version-matched framework and let the application’s configuration select it. Replacing a single DLL can leave the rest of the framework at different versions and create a second failure.
How do I identify the .NET version the application requires?
Find the application’s target framework before installing anything. Use the application’s documentation, installer requirements, deployment archive, project files, or its .runtimeconfig.json file. The target framework and deployment configuration determine whether the machine needs a shared runtime at all and which major/minor version is compatible.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check the runtime configuration
If the application folder contains a file ending in .runtimeconfig.json, open it in Notepad and look for the framework name and version under the runtime options. Record the major and minor version exactly as shown. Do not infer the version from the missing DLL’s filename.
Check the project or installer
For software you build or maintain, inspect the project file for its target framework. For software you installed, read the vendor’s system requirements or the installer’s prerequisite screen. If the deployment package includes a private runtime directory, note that as well; it may indicate a self-contained deployment rather than a framework-dependent one.
Distinguish a runtime from an SDK
A runtime is intended to run a deployed application. An SDK includes the tools needed to build and develop applications and also installs the framework components needed by those tools. Installing an SDK solely to run a finished program adds development components you may not need, while installing only a runtime will not provide build commands.
| Package type | Use it when | What to match |
|---|---|---|
| ASP.NET Core Runtime | You need to run a deployed ASP.NET Core application | The application’s target .NET release and architecture |
| .NET SDK | You build, develop, or publish the application | The project’s target framework and the required development architecture |
How can I see which runtimes and SDKs are already installed?
Open Command Prompt or Windows Terminal and run the inventory commands below. Compare their output with the target framework recorded from the application. These commands list installed products; they do not decide which version the application should use.
Also popular on Amazon
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
dotnet --list-runtimes
dotnet --list-sdksThe runtime list should show an ASP.NET Core shared framework corresponding to the application’s target release. The SDK list matters when you build or publish the program. If the dotnet command shows no matching entry, install the required package rather than copying a DLL.
Check x86 and x64 alignment
Determine whether the application is 32-bit or 64-bit from its documentation, installer, executable properties, or deployment requirements. Install the matching x86 runtime for a 32-bit application and the matching x64 runtime for a 64-bit application. Microsoft’s installation guidance supports side-by-side runtimes and architectures, but the application, runtime, and any native dependencies still need to be aligned.
| Application architecture | Runtime to install | Diagnostic implication |
|---|---|---|
| x86 (32-bit) | Matching x86 ASP.NET Core Runtime | An x64-only installation may not satisfy the application |
| x64 (64-bit) | Matching x64 ASP.NET Core Runtime | An x86-only installation may not satisfy the application |
How do I install or repair the ASP.NET Core Runtime?
Use Microsoft’s official .NET installer or the supported Windows Package Manager entries. Select the ASP.NET Core Runtime that matches the application’s target release and architecture. Examples of documented WinGet package identifiers include Microsoft.DotNet.AspNetCore.8, Microsoft.DotNet.AspNetCore.9, and Microsoft.DotNet.AspNetCore.10; the correct one depends on the application, not on which number is newest.
Install with WinGet
In an administrator-capable Windows Terminal session, use the package identifier for the required major version. For example:
Recommended Free Tools
winget install Microsoft.DotNet.AspNetCore.8
winget install Microsoft.DotNet.AspNetCore.9
winget install Microsoft.DotNet.AspNetCore.10Run only the command that matches the application’s documented target. If the program is a development project, use the corresponding SDK package listed in Microsoft’s current WinGet documentation instead of substituting a runtime package.
Repair an existing installation
If the correct runtime is already listed but the error persists, the installation may be damaged. Download or open the official .NET installer for the same release and use its Repair option. Microsoft’s installer also supports the /repair switch. Repair the matching x86 or x64 installation rather than repairing an unrelated architecture.
Also popular on Amazon
- Note: Not suitable for MacBooks released after 2023 or devices with a protruding front camera; Not applicable to full-screen or notch-style tempered glass screen protectors; Do not use on the rear camera of the phone.
- 💻 Why Do You Need a Webcam Cover Slide? — Safeguard your privacy by covering your webcam with our reliable webcam cover when not in use. Don't let anyone secretly watch you. Stay protected!
- ✅ Thin & Stylish — Enhance your laptop's functionality and aesthetics with our 0.027" ultra-thin webcam covers. Seamlessly close your laptop while adding a touch of sophistication.
- ✅ Fits Most Devices — Compatible with laptops, phones, tablets, desktops! Keep your privacy intact on Ap/ple, Mac/Book, iPh/one, iP/ad, H/P, L/novo, De/ll, Ac/er, As/us, Sa/msung devices.
- ✅ 365 Days Protection — Our upgraded 3.0 adhesive ensures a strong hold that won't damage your equipment. Experience reliable, long-term privacy protection day in and day out.
Restart and test
After installation or repair, close the application completely and start it again. If it is launched by a game client, launcher, scheduled task, or shortcut, test the same launch path that originally produced the error. A successful runtime installation should remove the missing-framework message; a new error can indicate that the application’s private files or another dependency is damaged.
How do I repair Windows with DISM and SFC?
If the error appeared after a failed update, an interrupted installation, or other Windows file corruption, repair the Windows component store and protected system files. Microsoft’s supported order is DISM first and SFC second: DISM provides the files required to repair corrupted files, and SFC scans protected system files and replaces corrupted copies from its cache.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Open an elevated Command Prompt. Search for Command Prompt, select Run as administrator, and approve the User Account Control prompt.
- Repair the online Windows image. Run:
DISM.exe /Online /Cleanup-image /RestorehealthWait for the operation to finish. DISM normally uses Windows Update as its repair source.
- Scan protected system files. After DISM completes, run:
sfc /scannowAllow the scan to reach 100 percent before closing the window.
- Restart Windows. Reboot even when the commands report that repairs completed, then test the application again.
Interpret the SFC result
SFC reports whether it found no integrity violations, repaired corrupted files, or found files it could not repair. A clean result means Windows protected files were not the remaining issue; it does not prove that the application has the correct ASP.NET Core runtime. A repair result means Windows files changed, so restart before testing. If SFC cannot repair some files, repeat the process only after DISM has completed successfully or continue with the alternate-source procedure below.
What if DISM cannot use Windows Update?
DISM can use matching Windows installation media, a network share, or another approved source when Windows Update cannot provide the repair files. The source must correspond to the installed Windows edition and build closely enough for the required files; a random USB image is not a substitute for matching licensed installation media.
- Connect the matching installation media or make the approved network source available.
- Identify the source path that contains the Windows installation files.
- Run DISM with the source and prevent it from contacting Windows Update:
DISM.exe /Online /Cleanup-image /Restorehealth /Source:<path> /LimitAccessReplace <path> with the path to the matching source. When DISM finishes, run sfc /scannow again, restart Windows, and retest the application. A USB flash drive is simply the physical container for the media; it does not itself repair Windows or supply a valid license.
Choose between Windows Update and alternate media
| DISM source | Use it when | Important condition |
|---|---|---|
| Windows Update | The PC can reach the required repair files normally | This is DISM’s default source |
| Installation media, network share, or removable media | Windows Update cannot supply the files | The source must match the installed Windows version and edition |
How should I handle an error that started after a failed Windows update?
A failed update can leave component-store or protected-file corruption that prevents applications from starting. Run the documented DISM-then-SFC sequence, restart, and retry Windows Update before deciding that the ASP.NET Core installation alone is at fault.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Also popular on Amazon
- Anti-Slip Surface - Transform your laptop into a mobile workstation with the AboveTEK portable laptop lap desk. The anti-slip surface provides a strong grip for laptops up to 15.6 inches(Diagonal), while the double rubber strip on the bottom ensures a stable display or typing experience on your lap, couch, or bed.
- Retractable Mouse Pad - Retractable laptop mouse pad extends on both directions for the left/right handed with elevation along the edges for stopping mouse from falling off. The size of laptop tray is 14" X 9.7" and the size of mouse pad is 7.4" X 6.1".
- Effective Heat Shield - The effective heat shield made of sturdy and thick material protects your laptop from overheating. Prioritizes your comfort and safety, an ideal lap pad or board for working anywhere.
- EASY to Carry and Store - With an ergonomic and simplistic design, the lap desk is portable to store in a backpack. Only 15" in size, 2.2 lb of weight and with slim 0.6 inch thickness, it is ready to be easily carried around.
- Widely Applicable - The smooth platform accommodates laptops and tablets up to 15.6 inches(Diagonal), making it a versatile accessory and one of the best gifts for mom, dad, students and professionals. Perfect for use as a laptop bed tray or tablet holder anywhere at home, library, or park.
- Record the application’s target framework and architecture.
- Run
DISM.exe /Online /Cleanup-image /Restorehealth. - Run
sfc /scannow. - Restart the computer.
- Retry the pending Windows update.
- Install or repair the matching ASP.NET Core Runtime if the application still reports the missing framework.
If the update repeatedly fails, preserve important files and use Microsoft’s supported recovery options only after the non-destructive repair paths are exhausted.
Does the deployment type change the fix?
Yes. A framework-dependent application expects the target shared framework to be installed on the computer. A self-contained application is intended to carry its runtime files with its deployment, so a missing shared-framework DLL in that case points more strongly to an incomplete, damaged, or incorrectly copied deployment package.
| Deployment model | Where the runtime is expected | Most useful next check |
|---|---|---|
| Framework-dependent | In the machine’s compatible shared framework installation | Install or repair the exact ASP.NET Core Runtime and architecture |
| Self-contained | Within the application’s deployment files | Verify the package was completely extracted or recopy the deployment from a trusted installer |
Do not convert a self-contained deployment into a framework-dependent one by deleting files or copying a single DLL. If the vendor supplied a deployment package, reinstall that package so all private assemblies are restored together.
Should I reinstall the application?
Reinstalling is appropriate after the framework is confirmed and Windows repair does not resolve the error, especially when the application was moved, partially extracted, interrupted during an update, or cleaned by storage software. Use the application’s own uninstaller or Windows’ installed-app controls, restart if requested, and install again from the original trusted package.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Back up settings, saved data, and add-ons that the application stores outside its installation folder.
- Uninstall the affected application using its documented procedure.
- Restart Windows if the installer requests it or if files remain locked.
- Install the same application release again, preserving the required x86/x64 choice.
- Launch it once before restoring optional plug-ins or modified files.
If reinstalling restores a self-contained package, the missing file was likely part of the application’s deployment rather than a Windows shared-framework problem. If the newly installed program still requests the same framework, return to the target-version check instead of repeatedly reinstalling.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What should I avoid when fixing this DLL error?
- Do not download the DLL from a random DLL website. The supported model is a complete ASP.NET Core shared framework or a complete application deployment, not an isolated file.
- Do not install an arbitrary newer runtime. Identify the target framework and rely only on documented compatible versions and roll-forward behavior.
- Do not replace files inside a shared framework directory manually. A hand-copied assembly can create a mixed installation in which related assemblies no longer match.
- Do not assume the newest SDK is the right runtime. SDK and runtime serve different purposes, and the application may target an earlier major release.
- Do not use a mismatched repair source. DISM needs installation files that correspond to the Windows installation being repaired.
- Do not delete the application’s runtime files to force a different loading path. That can turn a recoverable deployment issue into a missing-dependency chain.
When should I use Windows recovery or a clean installation?
Recovery is a last resort after the target runtime is installed, DISM and SFC have been run, the application has been reinstalled, and Windows Update still leaves the system damaged. Microsoft documents recovery and clean-install options, but these actions can remove applications or personal data depending on the option selected.
Also popular on Amazon
- Spacious Design: Measuring 21.1" wide and 12" deep, our lap desk comfortably fits most laptops up to 15.6". Extra room for accessories ensures convenience.
- Enhanced Functionality: Packed with handy features, including a 5x9" precision tracking mouse pad and a built-in phone slot for seamless work or video calls. Plus, enjoy laptop support with the integrated device ledge.
- Cool Comfort: Enjoy a stable surface with our lap desk's dual bolster cushion, designed for comfort and airflow, keeping your lap cool during extended use.
- Durable Surface: Work with confidence on our lap desk's solid surface, featuring a blush pink color, ensuring optimal air circulation to prevent your laptop from overheating.
- On-the-Go Convenience: With an integrated handle and lightweight design (2.14 lbs), our lap desk is portable for travel or moving around the house, offering flexibility in any space.
- Back up documents, saved games, configuration files, browser data, and recovery keys before proceeding.
- Confirm that you have installation media, account credentials, and installers for software you must restore.
- Choose the least destructive supported recovery option that addresses the Windows problem.
- After recovery, install Windows updates, the matching .NET runtime, and the application in that order.
A clean installation should not be used merely because one DLL is missing. It becomes reasonable only when broader Windows corruption cannot be repaired through the supported component-store, system-file, update, and recovery paths.
What is the fastest decision path for this error?
- Capture the exact message. Note whether it says the code execution cannot proceed or names a different missing dependency as well.
- Identify the target. Read the application documentation, installer requirements, project file, or
.runtimeconfig.json. - Check inventory. Run
dotnet --list-runtimesanddotnet --list-sdks, then compare versions and architecture. - Install or repair. Use the matching ASP.NET Core Runtime for a deployed app, or the matching SDK for development.
- Repair Windows. Run DISM first, SFC second, restart, and test.
- Use an alternate DISM source. Supply matching installation media with
/Sourceand/LimitAccessif Windows Update cannot provide files. - Reinstall the application. Do this when its private deployment files are incomplete or damaged.
- Escalate carefully. Preserve data before recovery or a clean installation.
This order restores the dependency chain instead of guessing at one filename. It also separates an application packaging problem from a Windows component-store problem, which prevents unnecessary system resets.
As an optional shortcut after the manual checks, Outbyte PC Repair can look for common broken Windows elements, invalid redirects, shared DLL issues, temporary-file and cache problems, and application-crash clues. It complements antivirus software rather than replacing it; results vary, no tool repairs every crash, and its free trial is limited by category before a subscription is required.
Frequently Asked Questions
Why does the application work on one Windows PC but not another?
The two computers may have different ASP.NET Core shared-framework versions, architectures, or deployment contents. A framework-dependent program relies on what is installed on the destination PC, while a self-contained package should bring its runtime files with it.
Can multiple .NET runtimes remain installed at the same time?
Yes. Microsoft’s installation model supports side-by-side runtimes and architectures. Keeping the required release installed is usually safer than removing older versions merely because a newer release is available.
Will installing the newest .NET release automatically fix an older application?
Not necessarily. The application’s target framework and documented roll-forward behavior determine compatibility, so a newer runtime should not be treated as a universal replacement for the version the program requests.
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 errorsWhat does it mean if reinstalling the runtime changes the error to another missing DLL?
That pattern can indicate an incomplete application deployment or several mismatched dependencies rather than one missing shared-framework file. Recheck whether the program is self-contained and reinstall its complete trusted package instead of adding individual DLLs.
Quick Recap
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.
