by admin

Microsoft Net Framework 4.5 Error Hresult 0x80240016

I have heard from a few customers since the release of the .NET Framework 4 who have installed the .NET Framework 4 on Windows Vista or higher and setup reported success, but they see an error when running the .NET Framework setup verification tool. I wanted to describe this scenario in a bit more detail, including how to diagnose whether or not your computer is running into this issue based on the setup log files.

The reason is you see this 0x800736B3 is because your Windows’ Component Store is corrupted, and you need to fix it using – you guessed it – DISM.

  • Mar 23, 2012  This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
  • This error appear when try to install software How to Fix HRESULT 0xc8000222 Error Dot NET Framework 4.0 While Problem Installation. Open Command Prompt i.

How to quickly tell if this blog post might apply to you

Before reading this whole post, here is a quick way you can check whether or not you are likely to be encountering the issue described below:

  1. Your OS was Windows Vista, Windows Server 2008 or Windows 7. This particular issue does not affect Windows XP or Windows Server 2003.
  2. You installed the .NET Framework 4 and setup reported success, but you cannot use .NET Framework 4 applications on your computer afterwards.
  3. The file %windir%system32mscoree.dll and/or %windir%syswow64mscoree.dll has a file version of 2.0.* instead of 4.0.* (and you have rebooted your computer after installing the .NET Framework 4 to make sure that any files that were in use during installation have had a chance to be updated).

Symptoms of the problem

In the cases I’ve seen so far, the .NET Framework setup verification tool reported an error like the following when it tried to run a .NET Framework test application that is bundled with it:

****ERROR**** Process 'Netfx40TestApplication.exe' exited with return code -2146232576

This return code translates to 0x800131700, which is a .NET Framework common language runtime (CLR) error code that means “Failed to load the runtime.” In other words, this return code means that this version of the .NET Framework runtime failed to load at all on this computer.

Further investigation on the computers that exhibited this behavior showed that the file mscoree.dll (which is located in %windir%system32 and/or %windir%syswow64) had a version number of 2.0.*. This file is shared by all versions of the .NET Framework, and it should always have a version of at least 4.0.* after installing the .NET Framework 4. If this file is not updated to version 4.0.*, the CLR loader will be unable to load the .NET Framework 4, and it will cause the type of failure in the .NET Framework verification tool that I described above.

Gathering more detailed information from .NET Framework setup log files

I wasn’t sure how a computer could be in a state where .NET Framework 4 setup reported a successful installation but yet mscoree.dll was still versioned 2.0.*. I had the customers use the instructions in this blog post to gather their .NET Framework setup log files, and I started looking at the logs to narrow this issue down further.

In the cases I’ve seen so far, I found an error like the following in the log file named Microsoft .NET Framework 4 Setup_*.html:

Exe (C:UsersmyusernameAppDataLocalTempMicrosoft .NET Framework 4 Setup_4.0.30319Windows6.1-KB958488-v6001-x64.msu) failed with 0x80240017 - (null).

The .msu file listed in the above error message is one of the ones that are responsible for updating mscoree.dll to version 4.0.* on Windows Vista and later versions of Windows. Return code 0x80240017 means that the .msu file is not applicable on the computer it is being installed on. This type of return code can occur for several different reasons:

  1. The .msu is for an earlier or later OS version or service pack level than what is currently on the computer
  2. The .msu is for a different processor architecture than the OS running on the computer
  3. The .msu is already installed
  4. The OS update installation engine is in a broken state that prevents the installation of any OS updates (.msu files)
  5. The OS is a pre-release version of Windows Vista, Windows Server 2008 or Windows 7. See this blog post for more details about this case.

.NET Framework 4 setup prevents cases #1 and #2 from happening behind the scenes, but it cannot prevent cases #3, #4 or #5. To complicate things further, it is not possible to reliably distinguish from this return code which of the cases is the actual cause of the return code. Even worse, case #3 is a case that should be treated the same as a successful installation of this .msu as opposed to a failure.

As a result, the .NET Framework 4 setup ignores this error and treats it as a successful installation of this .msu (case #3). This is why you will see information like the following later in the log file:

Error 0x80240017 is mapped to Custom Error: Success

Narrowing down the root cause based on the log files

Because mscoree.dll was not updated like it should have been on the affected computers, I made an educated guess that the customers who contacted me were running into case #4 on their computers. I was able to confirm this in the following ways:

  1. Looking at the log files named %windir%WindowsUpdate.log and %windir%logscbscbs.log (both of which are collected by the log collection tool linked above). In the cases I’ve seen so far, one or both of these logs showed errors while trying to evaluate applicability and/or install OS updates. These errors affected the .NET Framework 4 .msu file as well as other OS updates that the customer had attempted to install.
  2. Trying to manually install an OS update from Windows Update or by downloading it and running it directly. In the cases I’ve seen so far, attempting to install any OS update failed just like the .NET Framework 4 .msu file failed.

Possible solutions for this type of error

  1. In some cases, it can help to run SFC to repair the files that are installed as a part of Windows. You can find steps that explain how to do this in this knowledge base article.
  2. If SFC does not help, the System Update Readiness Tool might help repair the computer so that OS updates will install again. I’ve posted a set of steps I’ve had success using with this tool in some cases in the past in this blog post.
  3. Peter Marcu has posted a few additional suggestions on his blog for this type of issue as well.
  4. Unfortunately, if the above suggestions do not help, the only other way that I've found to solve this type of OS update installation error is to repair Windows.

<update date='12/30/2010'> Added a note about pre-release versions of Windows causing this error as well. </update>

Microsoft Net Framework 4 7

<update date='7/27/2011'> Added a note about using SFC to repair Windows files, as suggested in Peter Marcu's blog. </update>

<update date='11/8/2011'> Added a direct link to Peter Marcu's blog post about this issue. </update>

<update date='6/6/2012'> Fixed broken link in the 'Gathering more detailed information' section. </update>

There is no doubt that it is from the Windows Store where you are able to get the necessary apps and other stuff. This is particularly true in case you are using the latest Windows OSs including Windows 10.
However, accessing the store can sometimes be embarrassing with error messages like error code: 0x8024001e comes up on your computer screen. This error is not limited to the latest Windows operating systems; you can also encounter the error with the earlier versions although in different ways.
Error code 0x8024001e is a Windows Update error. It makes it difficult for your computer to install or update app such as Mail app. The app simply fails to sync. It also affects your computer’s performance, making it run slow, and the operating system can easily crash.

Reasons for Error code 0x8024001e in Windows

  1. Missing or corrupt DLL files.
  2. Missing or corrupt registry key.
  3. Virus/malware infection.
  4. Broken or unresolved update(s).
  5. Extra data in app cache.
Though these are the most common reasons for error 0x8024001e in Windows app store or while updating windows, But the error is not limited to only these reasons; It can be caused because of several other reasons too.

How to fix Error code 0x8024001e in Windows 7/8/8.7 &10



There are several methods you can adopt to resolve error 0x8024001e. While some are very simple, others are advanced are require that you have administrative rights to a computer with the error.

Method 1 – Basic Troubleshooting to fix 0x8024001e error

Windows error code 0x8024001e can occur because of a minor issue that you can overlook. It is, therefore, important to ensure that your Internet connection is reliable.
You also need to check whether or not your regional settings including date and time is correct. You need to restart your computer to see whether or not performing this basic housekeeping resolves the problem.

Method 2 – Clear Windows Store Cache

The simple act of clearing Windows Store cache can easily resolve error 0x8024001e. Stored cache reduces your computer’s performance, which can lead to various issues including this error.
1. Press the combination of Win + R key to open dialogue box.
2. Type “WSReset.exe” in the box before hitting Enter.
3: A command prompt window will pop up and immediately, Store will open up.
4: Now, Restart your computer to see whether or not this resolves the issue.

Method 3 – Registry Repair

This method works to resolve the error in a case where corrupt registry key is responsible. Running the repair tool automatically finds and repairs any corrupt entries. The process can take some time, and it is only appropriate that you let it complete.
Although the following procedure applies to Windows 8 OS, it should give you an idea on how to go about doing the same with any other Windows OS.
  • Click “Start”.
  • Type “Advanced” in the start search screen to open search results.
  • Click “Advanced Startup Options” to open general settings screen.
  • Click “Restart now” at the bottom to restart your computer in advanced startup mode.
  • Click the “Troubleshoot” button before clicking the “Advanced Options” button.
  • Click “Automatic Repair” to automatically reboot your computer.
  • Click on the administrator account to use after rebooting of your computer.
The in-built automatic repair tool should begin to run, which should resolve the Windows store 0x8024001e error.

Method 4 – Restart Microsoft Update

The Windows 0x8024001e error can

Microsoft Net Framework 4.5 Error Hresult 0x80240016 0

be caused by something as simple as Microsoft Update service that has stopped. Restarting the service easily resolves the error.
  • Click “Start”.
  • Type “Run” in the search box before hitting Enter Or Press Win + R Keys together.
  • Type “services.msc” before hitting Enter.
  • Right-click “Windows Update” before clicking “Start”.
  • This action should start the service in case it had stopped. Restart your computer and check if the error 0x8024001e is gone.

Method 5 – Rename Software Distribution Folder

Because it can be that Microsoft Update service is running, it becomes necessary to rename the software distribution folder in an attempt to resolve the issue.
Step 1: Click “Start”.
Step 2: Type “Run” in the search box before hitting Enter.
Step 3: Type “services.msc” before hitting Enter.
Step 4: Right-click “Windows Update” before clicking “Stop”.
Step 5: Rename software distribution folder by navigating to C:Windows, Right-click on “Software Distribution” folder > click “Rename” > type “SoftwareDistribution.old” before hitting Enter.
Step 6: Repeat steps 1-4 to restart Windows Update service.
Step 7: Restart your computer to see whether or not this resolves the problem.
Lot of users have reported simply renaming the folder has solved error 0x8024001e of them, We recommend to try this method and see by yourself if this helps you or not.

Method 6 – System Restore

4.5It may be necessary to restore your computer system to an earlier date in case any of the above methods does not resolve the problem.
1. Click “Start” >All Programs >Accessories >System Tools >System Restore.

2. Select to restore your computer to a date it worked well in the dialogue box that appears before clicking “Next”.
3. Click “Next” again in the resultant confirmation box.
The automatic system restore should begin to run and restart your computer on completion. This should most probably Guarantees to fix 0x8024001e error.

Method 7 – Uninstall Apps

This method may be your last option instead of performing the fresh installation of the OS. You can easily un-install built-in apps and re-install them again to get fresh app files. Although the following procedure applies for Windows 10 OS, it should give you an idea on how to do it with any other Windows OS.
  • Open 'Start Menu'.
  • Search for 'PowerShell'.
  • Choose 'Run as administrator'.
  • Type and run 'Get-AppxPackage', which displays all built-in apps.
  • Type and run 'Get-AppxPackage-AllUsers I Remove-AppxPackage' to remove all the apps.

Note that you can also choose to remove an individual app. For instance, removing the Sports app requires you to type and run 'Get-appxpackage-bingsports I Remove-appxpackage'. You will need to download either all the uninstalled apps or an individual app from Windows Store. Simply, Reinstalling the app can help you to get rid of the code 0x8024001e.

Method 8 - Fresh Windows OS Installation

This will no doubt be your last option although it can be time-consuming. It may be your only option in case any of the above methods fail because the error is most likely caused by a combination of issues that extend to the OS.
A clever way to prevent errors associated with Windows Update Store including error 0x8024001e is to install all updates including app updates whenever they become available. You also need to consider resetting the app cache before you undertake any download from the store.