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
<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.
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.
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
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.