Patching Windows Server 2019 Core with Windows Update.

Tzahi Kolber
3 min readDec 21, 2018

--

In this blog, I will review the process of patching Windows Server 2019 Core with Windows Update and changing the patch installation settings.

Choosing the right update process for you:

In my opinion, the easiest way to update Windows 2019 core, is by running Sconfig.
In case you are not familiar with Sconfig, just type sconfig at the CMD window and you will be able to see the nice “Dos” based GUI.

After opening the Sconfig menu, you will get many options for changing the main features in Windows OS.

Regarding Windows Update, 2 options are available:
- Option number 5: Windows updates settings, choosing between 3 options (Automatic, DownloadOnly or Manual).
- Option number 6: Download and Install Updates.

The default settings are set to Automatic updates, but in case you would like to change it from Manual to Automatic, since it wasn’t configured to automatic updates, just choose option number 5 A

Running the update process:

After the setting was changed you will get the Sconfig menu back.
From the menu, just type 6 (Windows Update Settings):

You will get the option for searching all updates (A)or recommended updates only (R).
In this example, I have chosen all update (Just type A):

Now you will get the list of all updates available for your system.
Type A for all updates.
In case you would like to download and install the only specific update, type S and select the number of the update (1 in our example):

The system will download and install the update:

After finishing the installation, you will be able to view the installation status and in case the system needs to be rebooted.
Type any key and close the windows update installation screen:

Please notice that automatic updates are not recommended for Exchange servers since .Net Framework versions are almost always released before the Exchange’s product group supports them with the Exchange’s Cumulative Updates.
Therefore, keep in mind to update Exchange servers with .Net Framework only after checking the Exchange’s Supportability Matrix:
https://docs.microsoft.com/en-us/exchange/exchange-server-supportability-matrix-exchange-2013-help

HTH :-)

--

--

Tzahi Kolber

During the last 17 years, I was working as a Senior PFE within Exchange area at Microsoft. Now I’m Senior Consult as Azure IAAS, DevOps & Automations.