In this particular example, we have a server that is running an operating system previous to Server 2016 if you’re not in the corporate environment, that would translate to an operating system previous to Windows 7.
Old Operating Systems not supported
If you are running an operating system this old just remember that there’s a high chance it will even not be in support or very near the end of it extended support cycle so this might be a good time to think about upgrading it.
Upgrade the OS - well its not always that simple
While upgrading the operating system comments sounds fantastic we also need to be realistic and understand that some corporations will have a legacy application for some weird requirements will not be able to support the new operating systems however, this application is sometimes critical to your business operating.
Operating Systems : Cumulative Updates
If you do have an operating system, that was pre-cumulative updates then you will remember the pain of having to get all the prerequisite updates before being able to install the update you needed, this new CU update was included from Windows 8 or Server 2016.
Dependency Woes and Incompatabilitys.
This particular dependency problem seem to rear its head at the most inconvenient time, for example, there was a hotfix to fix a critical problem with for example, an NPS server (The role or purpose of a server is not really important here) upon finding an article that matched your problem, you eagerly downloaded the Windows update and then tried to install the update, only have your efforts thwarted at the moat with this:
Standalone Installer is wrong and detecting the wrong information
When I see that I immediately think well yes, it is, It is absolutely applicable of my system and if you rule out The usual errors like downloading for the wrong architecture or the wrong platform completely it does make you wonder why the set up thinks it’s not applicable?
We still need to update to be installed
In this case, however somewhere a dependency checker has failed and it doesn’t think it’s relevant for your computer, however, for this example, that is not the case, I’ve downloaded the correct update for the correct architecture, furthermore, I need this hotfix installing to fix a problem?
Hotfixes that I required
First, we need to explain the situation I was trying to solve In this particular instance, I was trying to get a down level server, which was server 2012 R2 you seem to require a couple of hot fixes these include;
KB3159706 : this update add support for your hybrid join to Entra.
KB3140245 : this update allows you to enable TLS 1.2 as a secure default protocol.
DISM - the tool for the job
I was only getting this error with KB3159706, regardless this needed to be installed on the server, so there is another way to accomplish this goal using DISM, this is still a valid way of installing updates. It’s just not the default double click action.
Install update with DISM
Copy the downloaded MSU file to a directory, in this example, I used the directory c:\Hotfix what you have created the dietary start a new command prompt in elevated mode and then navigate to that folder you’ve just created.
Unpack the MSU file with the command below:
windows8.1-kb3159706-x64_034b30c6c261d4e76b8c6f8fe3cc9fa5fa4e977b.msu /extract
Then from the same directory run the following command that will then successfully install the update:
dism /online /add-package /packagepath:Windows8.1-kb3159706-x64.cab