Be Careful Installing .Net 4.6 / Visual Studio 2015 with SharePoint 2013 (July 2015)

Brian T. Jackett General .Net, SharePoint, Visual Studio

<Update 2016/09/13>

Please see the following Microsoft support article for resolving this issue.

SharePoint 2013 or Project Server 2013 Setup error if the .NET Framework 4.6 is installed

https://support.microsoft.com/en-us/kb/3087184

</Update>

<Update 2015/7/28 2:30pm>  I received clarification that the SharePoint product group does support installing .Net 4.6 onto an existing SharePoint 2013 farm server.  It is the installer for SharePoint 2013 that will fail to detect .Net 4.5 if .Net 4.6 is already installed and thus throw an error.  A future update should correct this scenario with the installer.

 

   On a related note I was able to successfully uninstall .Net 4.6 from a server (remove the KB as mentioned at bottom of this post) and then install SharePoint 2013.

</Update>

 

   Quick publish on this item and I’ll update once I have more details.  One of my customers is exploring Visual Studio 2015 / .Net 4.6 which was just released a week or two ago.  During some testing I found out that (as of July 28 2015 when this is published) you cannot install SharePoint 2013 binaries onto a server that has .Net 4.6 (or Visual Studio 2015 which includes .Net 4.6) installed.  I received the below error message.

Net46andSP2013

   Since .Net 4.6 is an in-place upgrade of .Net 4/4.5/4.5.1/4.5.2 SharePoint has an issue with finding .Net 4.5.x after applying 4.6.  I am testing out removing the associated KB for .Net 4.6 to see if this is reversible should you accidentally deploy this to a dev / test farm.  I’m also testing if you can install .Net 4.6 / Visual Studio 2015 onto an existing SharePoint 2013 farm.

 

Removing associated KB…

  • On Windows Vista SP2 / Windows 7 SP1/ Windows Server 2008 SP2 / Windows Server 2008 R2 SP1, you will see the Microsoft .NET Framework 4.6  as an installed product under Programs and Features in Control Panel.
  • On Windows 8 / Windows Server 2012 you can find this as Update for Microsoft Windows (KB3045562) under Installed Updates in Control Panel.
  • On Windows 8.1 / Windows Server 2012 R2 you can find this as Update for Microsoft Windows (KB3045563) under Installed Updates in Control Panel.

Download .Net framework

https://msdn.microsoft.com/en-us/library/5a4x27ek(v=vs.110).aspx

 

    Hopefully this helps someone before they run into issues with their farm.  Feel free to leave a comment if you find out any additional details or workarounds.

 

      -Frog Out

28 thoughts on “Be Careful Installing .Net 4.6 / Visual Studio 2015 with SharePoint 2013 (July 2015)”

  8. Originally posted on: https://briantjackett.com/archive/2015/07/28/be-careful-installing-.net-4.6–visual-studio-2015-with.aspx#647028Wow…thanks for this! I spent a lot of time searching for a solution. I was searching for the error message, but you have just a screenshot, so I didn’t find your blog at first. So, for the benefit of others, here is the error message in question:Catalyst .Net version check failed. Setup requires .Net Framework version 4.5.50501 to install this productRegards,Mike Sharp

    Like

    Reply

  11. Originally posted on: https://briantjackett.com/archive/2015/07/28/be-careful-installing-.net-4.6–visual-studio-2015-with.aspx#647998AutoCAD 2015 does this as well, because of some stupid string comparison in the msi installer it fails with .net 4.6.The fix with AutoCAD is settings these registry keys:[HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Client]”Version” = “4.5”[HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Client1033]”Version” = “4.5”After install set it to the value it was previously. Waiting for autodesk to fix their installer would be pointless.

    Like

    Reply

  25. Originally posted on: https://briantjackett.com/archive/2015/07/28/be-careful-installing-.net-4.6–visual-studio-2015-with.aspx#649279this works, thank you jjurkus!uninstallation .NET 4.6.1 was not possible on server, no option to uninstall in programs and features, this workaround works:change registry key temporary:[HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Client]”Version” = “4.5”[HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Client1033]”Version” = “4.5” and return to original value after installation Sharepoint Foundation Server 2013, in my case 4.6.01055(ownership had to be taken from registry key, to achieve administrator permissions to change this key)I did this on a Windows Server 2012 R2 server installation

    Like

    Reply

  28. https://support.microsoft.com/en-us/kb/3087184 has download links that could be the fix. It was for my build today that encountered this same issue.

    “Download the compressed (.zip) file that contains the fix that matches the product you’re installing:

    SharePoint Foundation 2013 with Service Pack 1 fix
    SharePoint Server 2013 with Service Pack 1 fix
    Project Server 2013 with Service Pack 1 fix

    Open the .zip file.
    Copy the following Setup support file, as appropriate, from the .zip file into the “updates” folder in your writable location.

    SharePoint Foundation 2013 with Service Pack 1: wsssetup.dll
    SharePoint Server 2013 with Service Pack 1: svrsetup.dll
    Project Server 2013 with Service Pack 1: svrsetup.dll

    Run Setup.exe from the writable location to start SharePoint Setup or Project Server Setup. Setup will use the support file that contains the fix that you’ve copied into the “updates” folder.” – KB3087184

    Like

    Reply

Leave a comment