Dear Admins, suffering companions, I've tried to bump up at a very kind and helpful person at Microsoft. I cannot promise anything but I hope it does help this issue gets a checkmark before end of main support for Server 2016 LTSC, after more than a year of reporting.
MS / users refer also
currently the only way to fix this is to upgrade to 2019 Server. This is silly if one has no Software Assurance.
Dear Admins, suffering companions, I've tried to bump up at a very kind and helpful person at Microsoft. I cannot promise anything but I hope it does help this issue gets a checkmark before end of main support for Server 2016 LTSC, after more than a year or reporting.
I still encourage anyone that have active Software Assurance to take a backup when Server is shut down and use ISO / setup.exe to upgrade to Server 2019 1809. This will fix the update issue. Updates for GUi servers will take about 10 Minutes, without GUI it's done in lesser time.
I don't see a fix coming for Server 2016, by Design, the Update packages are too big and 1607 has serious issues with TIworker process.
Server 2016 SAC is not affected as they use newer code but this is limited choice for Software Assurance and non GUI servers.
On the matter: I have hopes that MS has heard us and will implement express updates (not the same as in WSUS options), to greatly reduce size and install time. First they only wanted to bring this for Server 2019 (1809) but I've heard that this is going to be ported backwards.
anonym have you made sure to install the latest SSU before installing the latest CU?
The latest SSU was released on 11. Nov.
find a comprehensive list of all SSUs here: https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001
edit: 10 2012 R2 server installed (not upgraded) their 09-2019 updates during the same time in a piece of that time residing on the same SAN / VMware Hosts.
Last patchday 06.10. 09-2018 September CUs:
2 VMs on VMware: 2016 (LTSC)
update duration 7:30 pm to 11:30 pm.
Why? The VMs did download the 05-2018 CUs in the local cache from WSUS.
You cannot deny this installation via usoclient or PShell.
After the installation of the 05-2018 patches, the 09-2018 were obtained and installed via WSUS.
Please know that this behaviour won't be the same with Server 2016 1703 (SAC) or later or even 2019 Server.
So it provingly is a servicing stack issue / TIworker.exe issue despite all current SSU were installed. Please fix your code Microsoft.
No company will upgrade to 2019 (currently paused), or use SAC branch just for sake of having FAST updates.
In the meantime I've upgraded 10 Server 2012 R2 machines + 3 clients from 1803 to 1809.
Just to give you an idea HOW F... slow this Server 2016 1607 does do its updates. I am feeling desperate that you do not comment or solve this major issue.
Patrick I hear you, let's hope that Server 2019 will be better. Infact Server 2016 is a bit like vista and technically old, based on Windows 10 1607, which was not their best release base anyway.
I have good hopes for Windows 10 1809 / Server 2019
^^ they probably know but don't have the personel and time to do that. Still I think it has become easier with Windows 10 and 201x Server
I also recommend to install the most recent SSU first before installing any other CU or update.
Steve I absolutely agree I am sure that Server 2016 won't be addressed and MS will focus to fix this in Server 2019 aka 1809 and which is probably also the next LTSB.
This is a sad thing but I doubt they will can handle this using a servcing stack update. BTW have you installed the Servicing stack update on any 2016 Server yet to test if this ease the process? There was a very unknown advisory in the Update History.
Prerequisite: When installing both the servicing stack update (SSU) (KB4132216) and the latest cumulative update (LCU) from the Microsoft Update Catalog, install the SSU before installing the LCU.
Note these SSU (servicing stack update do not come automatically to any Windows Version, neither 1507 (and LTSC), 1511, 1607 (and Server and LTSC), 1703. 1709 and 1803 are not affected
Please give it a try if this fixes your issues.
On my behalf MS should automatically deploy these to anyone needed and code a prerequisite check. Cannot be that hard Microsoft, can it?
David, Update log is available only via Powershell. This is a change.
Anonymous try to enable software vGPU on ESX / Hyper-V this should heal your GUI slowness and greatly improve the performance on Citrix for free.
On the topic I am sad that Server 2016 does not offer Edge, as a substitute to IE as IE is still loading while other products are already ready.
So my plea is: faster updates (better utiliziation and GPOs to steer dism / installer worker)
implement Edge on Servers, please.
still not fixed
18 votes1 comment · Management Tools » Server management tools (In-box) · Flag idea as inappropriate… · Admin →
38 votes0 comments · Management Tools » Server management tools (In-box) · Flag idea as inappropriate… · Admin →
24 votes2 comments · Management Tools » Server management tools (In-box) · Flag idea as inappropriate… · Admin →
6 votes0 comments · Management Tools » Server management tools (In-box) · Flag idea as inappropriate… · Admin →
17 votes1 comment · Management Tools » Server management tools (In-box) · Flag idea as inappropriate… · Admin →
does also apply to Windows Admin Center 1809
16 votes0 comments · Management Tools » Server management tools (In-box) · Flag idea as inappropriate… · Admin →
9 votes1 comment · Management Tools » Server management tools (In-box) · Flag idea as inappropriate… · Admin →
lean I am sorry but WAC is far from being useful or to replace Server Manager. if you install a role that needs after installation actions, WAC will not notify you, you need to go into Server manager to complete the steps. But yes, the idea would be nice.
It also cannot be used to manage one thing at many servers like in Server Manager.
11 votes1 comment · Installation and Patching » Deployment & Installation · Flag idea as inappropriate… · Admin →
this has been fixed afaik
yes it is. and also I notice very often that docs.microsoft sites are no longer consistent. en-us sites have a complete different content rather than de-de
compare: Windows Admin Center, Exchange Compatibility Matrix and others. It is not a matter of "machine based translation". The contents are completely different.
correction: 8.1 and 8.2 are named in the compat matrix, 8.3 is missing.
however since 8.0 there are no documented feature changes that 8.1, 8.2 or 8.3 would bring except limiting the downwards compatibility.
requirements 2 SSDs or HDDS or VMDKS
open Manage Storage Spaces in the classic control panel
Create new pool
no resilency / parity
FS NTFS (ReFS is no longer possible)
simple / parity
provisioning type fixed
NTFS / ReFS
I have reproduced this in Window 10 Pro Insider 1809 17723, 17763 and Server 2019 17723 and it seems to be fixed.
The request of Doug has been implemented. Check out GPO ADMX 1803 Version 2.0