How to fix .NET Framework error 0x800713ec in Windows?

Error 0x800713ec, often shown as "0x800713ec - Asia", comes from the .NET Framework installer and means it decided your PC does not meet its requirements. On Windows 10 and 11 that most often means a program tried to install an older .NET Framework 4.x than Windows already has. Check that .NET Framework 4.8 is turned on first (Fix 1).

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What .NET Framework error 0x800713ec means

The code has two parts. 0x8007 says a normal Windows error number is packed inside, and 13EC is that number in hexadecimal: 5100. Microsoft's deployment guide for the .NET Framework installer lists return code 5100 as The user's computer does not meet system requirements. So the installer did not crash. It checked your PC, found a reason not to continue, and stopped on purpose.

The word Asia after the code confuses almost everyone. It has nothing to do with your region, language or time zone. It appears to be a wrong text that some setup programs show next to this code. We could not find a Microsoft explanation for it, so treat 0x800713ec - Asia and plain 0x800713ec as the same error.

Why the .NET Framework installer stops with 0x800713ec

Return code 5100 covers every case where setup decides not to continue, so the code alone does not name the cause. Microsoft's list of blocked .NET Framework installations shows the possible reasons. On a current Windows 10 or 11 PC, one of them is far more common than the rest.

How to fix .NET Framework error 0x800713ec

Fix 1 solves the most common case in two minutes and changes nothing on the PC. Fixes 2 and 3 cover a program that needs a different .NET package. Fixes 4 to 6 clear the conditions setup checks, and Fixes 7 and 8 repair damaged files.

Fix 1. Check that .NET Framework 4.8 is on, then skip the program's old .NET package

2 to 5 minutesNo riskA program's setup stops with 0x800713ec - Asia while it installs its .NET Framework prerequisite. This is the most common case on Windows 10 and 11.

Microsoft says you cannot install an earlier .NET Framework 4.x on a system that already has a later one, and that on Windows 8 and later .NET Framework is an operating system component. A program built for 4.5.2 to 4.8 runs on the 4.8 or later that Windows already has, so its own old installer is not needed.

1. Select Start, type Windows Features and open Turn Windows features on or off. You can also open Control Panel > Programs > Programs and Features and select Turn Windows features on or off on the left.
2. Find .NET Framework 4.8 Advanced Services. A filled or ticked box means .NET Framework 4.8 or later is on.
3. If the box is empty, select it and select OK. You do not need to turn on ASP.NET 4.8 or WCF Services for a normal program.
4. Close the program's setup. Start it again and look for an option to skip prerequisites, or select Continue or Ignore if it offers one after the .NET step.
5. If the program comes as a folder or a ZIP with a separate .msi file next to setup.exe, run the .msi file: it usually skips the bundled .NET package.
6. Start the program. If it opens, the fix worked and the old .NET package was never needed.

Fix 2. Install the program's newer version, or Microsoft's offline .NET Framework 4.8.1 installer

10 minutesLow riskThe program cannot skip its .NET step, you started an old .NET 4.x installer yourself, or setup says the package does not apply to this operating system.

Microsoft's advice for the message that a .NET redistributable does not apply to this operating system is to run the offline installer of the right version, because the small web installer can lack the parts for your Windows. A program's newer release usually targets a .NET version Windows already has.

1. Open the maker's website and download the latest version of the program. Many old installers bundle .NET 4.5.2 or 4.6.1, while current versions do not.
2. If you need .NET Framework itself, open dotnet.microsoft.com, go to Download .NET Framework and select .NET Framework 4.8.1, the newest version on that page.
3. Under Runtime, choose the offline installer. Do not download the Developer Pack: it is for programmers.
4. Run the downloaded file. If it says .NET Framework 4.8.1 or a later version is already installed, nothing is missing: go back to Fix 1.
5. Restart the PC when setup asks, then run the program's setup again.

Fix 3. Turn on .NET Framework 3.5 if the program asks for it

5 to 10 minutesLow riskThe program or its setup names .NET Framework 2.0, 3.0 or 3.5.

.NET Framework 3.5 is not a 4.x update and is not replaced by 4.8. On Windows 10 and 11 it is a Windows feature that you turn on, so an old 3.5 installer bundled with a program can fail the same requirement check.

1. Open Turn Windows features on or off as in Fix 1.
2. Select .NET Framework 3.5 (includes .NET 2.0 and 3.0) and select OK.
3. Choose Let Windows Update download the files for you if Windows asks.
4. Wait for Windows completed the requested changes and restart if asked.
5. Run the program's setup again.

If turning on .NET 3.5 fails with its own code, such as 0x80072EE6 or 0x800F0906, follow our guide on .NET Framework error 0x80072EE6, which also covers installing 3.5 from Windows media.

Fix 4. Restart the PC and install all pending Windows updates

10 to 30 minutesLow riskWindows Update shows Restart now or waiting updates, or you installed something just before the error.

Two of Microsoft's block messages are a restart left over from a previous installation and a required update that must come first. Both stop setup before anything is installed, and the program's setup then reports only the code.

1. Save your work and restart the PC once, even if Windows does not ask.
2. Open Settings > Windows Update and select Check for updates. On Windows 10 it is Settings > Update & Security > Windows Update.
3. Install everything offered, including updates under Advanced options > Optional updates that mention .NET Framework.
4. Restart again when the updates ask for it. Microsoft notes you may have to restart more than once.
5. Run the program's setup again.

Fix 5. Run setup as administrator and not in compatibility mode

5 minutesLow riskYou use a standard account, setup was started from a shortcut with changed settings, or an earlier setup attempt was cancelled.

Microsoft lists two more blocks: setup needs an administrator, and the .NET Framework installer cannot run in Program Compatibility Mode. The Program Compatibility Assistant can switch that mode on by itself after an earlier failed or cancelled attempt.

1. Right-click the program's setup.exe and select Run as administrator. Select Yes in the User Account Control window.
2. If it fails again, right-click setup.exe, select Properties and open the Compatibility tab.
3. Clear Run this program in compatibility mode for and select OK.
4. Select Change settings for all users at the bottom of the same tab, clear the same box there too, and select OK.
5. Run setup as administrator again.

Fix 6. Free up space on drive C:

10 minutesLow riskDrive C: has only a few GB free.

Users report that 0x800713ec - Asia went away after they freed disk space, because setup counts space on the system drive as a requirement. We could not confirm a fixed minimum from Microsoft today, so treat this as a check, not the main fix.

1. Open Storage settings. Select Start > Settings > System > Storage. The top of the page shows how full the drive is and what uses the space.
2. Open Cleanup recommendations. Under Storage management, select Cleanup recommendations.
3. Clean up what Windows suggests. Open each group (Temporary files, Large or unused files, Files synced to the cloud, Unused apps), check the items you do not need and select Clean up in that group.

These steps were written for Windows 11 (screenshots: 26H2). The full page with the other versions and what each result means: Free up disk space and delete temporary files

Fix 7. Run the Microsoft .NET Framework Repair Tool

10 minutesLow riskFix 1 to 6 did not help, or other programs that use .NET also fail to start.

Microsoft's repair tool checks for common problems with .NET Framework setup and updates, and fixes damaged registration of the built-in .NET. If the installed 4.x is half broken, setup can misread what is there.

1. Download the .NET Framework Repair Tool from Microsoft's Download Center (https://aka.ms/DotnetRepairTool).
2. Run the downloaded file, accept the licence terms and select Next.
3. Let the tool check the PC and apply the changes it recommends, then select Finish.
4. Restart the PC and run the program's setup again.

Visual C++ and .NET repair together, step by step: How to repair Microsoft Visual C++ Redistributable and .NET Framework

Fix 8. Repair Windows system files with SFC and DISM

20 to 30 minutesLow riskSetup says the component store has been corrupted, or nothing above worked.

On Windows 10 and 11 .NET Framework lives in the Windows component store. Microsoft's answer to the block message about a corrupted component store is DISM, which repairs that store; SFC then repairs the system files.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

If error 0x800713ec is still there

The program's setup shows only the code, but the .NET installer writes the real reason to a log. Microsoft says the log goes to the temporary folder by default, with a name based on the package, as an HTML file unless the name ends in .txt.

1. Press Win + R, type %temp% and select OK.
2. Sort by Date modified and open the newest file whose name mentions .NET Framework, or the setup log of your program.
3. Search for 5100, 0x13EC or Blocking and read the message near it.
4. Compare the message with the table of causes above and use the fix it points to.

For support from the program's maker, send the code, the program's version, your Windows version from winver and the block message from the log. 0x800713ec is never a hardware fault or a licence problem: it is always the installer's own decision.

How to keep error 0x800713ec from coming back

Frequently asked questions

What does 0x800713ec mean?

It is the .NET Framework installer's return code 5100 written as a Windows error code: 0x8007 marks a Windows error and 13EC is 5100 in hexadecimal. Microsoft describes 5100 as "The user's computer does not meet system requirements." Setup checked the PC and refused to continue. On Windows 10 and 11 this is most often because Windows already has a newer .NET Framework 4.x than the one the program tries to install, so start with Fix 1.

What does Asia mean in 0x800713ec - Asia?

Nothing you need to act on. The word appears next to the code in many program installers, but it has nothing to do with your region, keyboard, language or time zone, and changing them does not help. We could not find a Microsoft explanation for the text, so we treat it as a wrong message. The code 0x800713ec is what matters, and the fixes on this page apply to both spellings.

What should I do first when I see 0x800713ec?

Open Turn Windows features on or off and check that .NET Framework 4.8 Advanced Services is on (Fix 1). If it is, your PC already has what most programs need, and the error only means the program's bundled .NET installer is older. Skip that step in the program's setup or download a newer version of the program. If the program asks for .NET 3.5 instead, turn that feature on (Fix 3).

Why can I not install .NET Framework 4.5.2 or 4.7.2 on Windows 10 or 11?

Because a later version is already there. Microsoft explains that .NET Framework 4.x versions are in-place updates, so an earlier 4.x cannot be installed on a system with a later one. Its example: on Windows 10 Fall Creators Update you cannot install 4.6.2, because 4.7.1 comes with the system. A program that asks for 4.5.2 to 4.8 runs on the newer built-in version.

Does 0x800713ec happen on Windows 10?

Yes. The code and its causes are the same on Windows 10 and Windows 11, because both include .NET Framework 4.8 or later as part of the system and both block older 4.x installers. The menus differ only slightly, and each fix gives both paths where they differ. Windows 10 reached the end of support on 14 October 2025, but the fixes still work on Windows 10 22H2.

Should I uninstall .NET Framework and install it again?

No. On Windows 8 and later, Microsoft says .NET Framework is an operating system component and cannot be uninstalled on its own; its updates only show under Installed updates. Removing them can break other programs. If the built-in .NET seems damaged, use Microsoft's .NET Framework Repair Tool (Fix 7) and SFC and DISM (Fix 8) instead.

Can a full disk cause 0x800713ec?

Users report that it can: some people saw 0x800713ec - Asia go away after freeing space on drive C:. Microsoft's description of code 5100 only says the PC does not meet the requirements, and we could not confirm a minimum size today. Checking free space takes a minute, so it is worth doing when Fix 1 to 5 change nothing (Fix 6).

Where can I see the real reason for 0x800713ec?

In the .NET setup log. Microsoft says the installer writes it to the temporary folder by default. Press Win + R, type %temp%, sort by date and open the newest log of the .NET installer or of your program. Search for 5100, 0x13EC or Blocking. The message near it names the block, such as a later version already installed or a restart pending, and the table above shows the fix.

Will the .NET Framework Repair Tool fix 0x800713ec?

Sometimes, but rarely first. The tool repairs a damaged .NET Framework installation and setup problems, while 0x800713ec usually means setup found nothing wrong and simply refused an older package. Use it when Fix 1 to 6 did not help or when other .NET programs also fail. It is a Microsoft download, and the steps are in How to repair Microsoft Visual C++ Redistributable and .NET Framework.