I usually have templates of different OS laying around as quick sandboxes. All I need to do is create a linked clone, and in under 5 min I have a new Sandbox ready to be hacked. For some reason, I decided to update the Windows Server 2012 R2 template I had. So AFTER 5 iterations on Update and restart, I thought I was done. But no MS had to do something to make my life a hell.
I tried different combinations to Install SQL Server, but it will always fail. This time before upgrading the template, I decided to create a snapshot (should do it more often!). So I decided to create a clone of the state before update. And BEHOLD, SQL 2014 installed without a hitch. At least that confirmed what went worng!.. It was one of these pesky updates…
Now, how to solve the problem. As it is obvious, it would take far more time to install each update for it self and try to install SQL server. But as it happens I was not alone with this little problem.
As it turns out the problem is caused by the Update 1 pack. The solution as it turns out is quite simple:
- Go to:
- Find the folder “Default”. It might be hidden, so might need to unhide it first.
1[Right Click] -> [Click <Security Tab>] -> [Click <Advanced>] -> [Click <Change Permissions>]
1[Check <Replace all child object permissions entries with the inheritable permissions entries from this object>]
1[Click <Apply>] -> [Click <OK>] -> [Click <OK>]
Now you can install SQL Server 2014 on Windows 8.1 Update 1 and Windows Server 2012 Update 1. Although I don’t think this error should occur when you have installed Windows 8.1 with Update 1 and Windows Server 2012 R2 with Update 1 from factory, only when updated via Windows Update.