SharePoint 2013 installer now supports .NET Framework 4.6 and above

The SharePoint installer released with SharePoint 2013 is not able to detect the most recent .NET Framework versions and incorrectly reports that .NET 4.5 needs to be installed first.
We just released a fix for the problem with the SharePoint 2013 installer if the machine has .NET Framework 4.6 or above installed.
Install location for the fix and instructions can be found in the following KB:

  • KB 3087184 – SharePoint 2013 or Project Server 2013 Setup error if the .NET Framework 4.6 is installed

 

20 Comments


  1. It fixed a big problem.

    Reply

  2. Thanks for sharing. It saved my day..

    Reply

  3. Thank you so much! I was stuck on that hang-up for months.

    Reply

  4. Thanks for sharing this Stefan.
    What I don’t understand is why has MS not included this in their latest release of the SharePoint 2013 setup. I know it’s no longer the latest version but if you’re going to leave a product downloadable, you should either include such a critical fix or put a big red warning on the download page with a redirect to this KB. I downloaded 2013 yesterday and I’ve wasted my entire morning with installation problems including this one. Very frustrating.

    Reply

    1. Hi Thierry,
      the latest release of SharePoint 2013 is the slipstream install SharePoint 2013 with SP1. this was released February 2014.
      .NET framework 4.6 was released in year 2015.
      So I think it is clear now why .NET 4.6 support could not be added in the latest released SharePoint 2013 version.
      Cheers,
      Stefan

      Reply

    1. Hi Jean,
      I tested the link and it works fine. Seems to be an issue on your end.
      Cheers,
      Stefan

      Reply

  5. Thanks, Stefan!
    Is there something similar to Office Web Apps (aka WAC) or Office Online Server?

    Reply

  6. Dear Stefan,

    I have a SharePoint 2013 farm. Lot of Visual Studio custom developed web parts are hosted in SharePoint 2013 and working fine. Those custom web parts are developed using Visual Studio 2013.

    Now, I have a requirement to upgrade all custom solutions to .Net Framework 4.7

    I have installed .net framework 4.7 developer pack but not able to see the installed .net framework 4.7 in visual studio -> project properties -> Targeted Framework section.

    This is happening only for SharePoint based project in visual studio 2013. But it works fine for ASP.Net projects.

    Kindly guide me..

    Thanks in advance

    Reply

  7. What do you do if you have windows server 2012 R2 installed?

    Reply

    1. Hi James,
      SharePoint Server 2013 with SP1 supports Windows Server 2012 R2.
      Cheers,
      Stefan

      Reply

  8. I have SharePoint Server 2013 with latest SP CU installed on Windows Server 2012 R2. Is there any challenges if we upgrade .net framework to 4.6 or higher version on SharePoint server.

    Reply

    1. Hi JA,
      not for SharePoint itself. If you have any custom code integrated you would need to validate if that custom code has any issues.
      Cheers,
      Stefan

      Reply

  9. Hello,

    i’m searching for a solution for the .net 4.6 problem and sharepoint 2013 foundation. the problem, the downloadlink to the fix doesn’t work anymore. i get a error 404 page. exist a alternative download possibility for the patch?

    hope you can help

    thx
    Alex

    Reply

  10. For me thats to dosen’t works 🙁 some can give linkt to dowland this fix

    Reply

  11. I’ve also encountered this .Net Framework error problem this week. I was attempting to install the “SharePoint Server 2013 with Service Pack 1” download from MSDN. As a few of you have commented, the fix file (svrsetup_15-0-4709-1000_x64.zip) is no longer available (broken links or erroneously pointed to the service pack which doesn’t contain the fix).

    I couldn’t locate that fix file, but as a workaround I have got the install to work successfully by running the RTM install, “SharePoint Server 2013” downloaded from the MSDN website. For whatever reason, this earlier version doesn’t encounter that problem. Then install the service pack…..

    Hope this helps somebody.

    Reply

  12. Could we not just have released a new ISO for download?

    Reply

Leave a Reply to Stefan Goßner Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.