SharePoint Foundation 2013 – Setup is Unable to Proceed due to following error, requires .Net Framework 4.5
I have been setting up a MIM PAM lab at home. Following the guide here: https://technet.microsoft.com/en-us/library/mt488766.aspx
I’m installing onto Server 2012 R2, with SharePoint Foundation 2013 SP1
After installing the SharePoint Foundation 2013 Prerequisites, using the Service Pack 1 release, all installs just fine. Then I run the setup.exe, very quickly I’m prompted with the message “Setup is Unable to Proceed due to following error, requires .Net Framework 4.5“. The prerequisite installation log (C:\Users\<MyUserAccount>\AppData\Local\Temp\) shows:
2016-01-29 22:39:36 – Check whether the following prerequisite is installed:
2016-01-29 22:39:36 – Microsoft .NET Framework 4.5
2016-01-29 22:39:36 – Reading the following DWORD value/name…
2016-01-29 22:39:36 – Install
2016-01-29 22:39:36 – from the following registry location…
2016-01-29 22:39:36 – SOFTWARE\Microsoft\Net Framework Setup\NDP\V4\full
2016-01-29 22:39:36 – The value is (1)
2016-01-29 22:39:36 – Reading the following string value/name…
2016-01-29 22:39:36 – Version
2016-01-29 22:39:36 – from the following registry location…
2016-01-29 22:39:36 – SOFTWARE\Microsoft\Net Framework Setup\NDP\V4\full
2016-01-29 22:39:36 – The value is…
2016-01-29 22:39:36 – 4.6.01055
2016-01-29 22:39:36 – A post release .NET 4.5 is installed
However, the SharePoint Foundation installation log shows:
2016/01/30 19:27:00:389::[3788] Catalyst .Net version check failed. Setup requires .Net Framework version 4.5.50501 to install this product
4.6.01055 is installed but the installer wants the older version – 4.5.50501.
So, after a bit of googling, I find this: https://social.technet.microsoft.com/Forums/sharepoint/en-US/bbed58e1-4a80-4dde-91fd-c6fc95bf85ac/sharepoint-2013-installation-with-net-framework-4550501-and-4550709?forum=sharepointadmin
In that post, Rick just sets all of the registry entries. However, the one that seems to be the ‘looked up’ value (at least based on my testing today), which is contrary to the prerequisite log, is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client.
Detailed method:
Right click the Client key, choose Permissions…
Note that the Administrators group has Read access by default.
Click Advanced, note at the top of the window, the owner is shown as TrustedInstaller:
Click the Change link beside the owner label.
Change the scope (“From this location”), to the local machine, choose <localmachine>\administrators group:
Click OK, then OK again until we are back at the initial Permissions window, tick Full Control for the Administrators group:
OK, then go set the Version number to 4.5.50501
Install SharePoint Foundation 2013.
Once complete, put things back to how they were before – of course this is optional….. just depends on how lazy you feel and whether you want to be caught out by the fact that you changed this sometime in the future, then can’t figure out why something else doesn’t work. Making the change back is so straightforward and quick, I believe that it is worth doing 🙂
After installation, flip version back to 4.6.01055. Then, right click the Client key, remove full control from the Administrators group, apply. Then, click Advanced, go and change the Owner again – as before but using NT SERVICE\TrustedInstaller as the owner:
Click OK, until you are back to Square 1. Easy!
Dhawal Mehta
17th March 2016 @ 8:29 pm
Thanks Jon, I have used your content on my blog and ofcourse give you the full credit.
Please let me know.
Jon Bryan
17th March 2016 @ 8:59 pm
Dhawal,
No problem, glad it helped you out.
I note in your blog that you have omitted the fact that you need to take ownership of the registry key and provide yourself full control/ edit permissions on the registry key *before* you can make the registry edit to trick SP 2013 into installing without error.
Jon
Andy
23rd March 2016 @ 8:34 am
After two days of pulling my hair out this has solved the installation problems we we’re having. Thank you.
Jon Bryan
23rd March 2016 @ 8:58 am
Andy,
No problem.
Its an annoying issue, needing a fair bit of digging to resolve, but I’m glad I could help.
Jon
CK
19th April 2016 @ 6:46 am
Great tutorial and actually works for me, many thanks
Dimos
3rd May 2016 @ 12:29 pm
Worked for me too
Erick Aldi
9th May 2016 @ 11:43 pm
This post saved my me, thank you very much!
Greetings from Guatemala!