Stop the "Windows update madness" on WS2016!
Dear Microsoft Windows Server team. We would like _complete control_ over when we would like our our WS2016 to install windows updates! No more slow / timeconsuming server restarts because of "Getting Windows ready. Do not turn off your computer" messages when we just would like a quick restart of a production server.. No more TiWorker.exe using 100% of a CPU core during "*********" and so on.. And please fix the issues with '2017-08 Update for Windows Server 2016 for x64-based Systems (KB4035631)' asap. Thank you.
2 EFD - having no internet connection at the time of Azure & AWS and hybrid infrastructure? Sorry but its 21st century and advanced firewalling is the solution for today not to be closed in a bunker. And when I compare Linux machines, clean installs, updates with W2016/2019 it's like a heaven and ****. In case of Linux it's transparent, all infos & progress provided to admins every second and all update process takes a few minutes. In case of W2016 I had been working on clean installs this weekend and I saw rolling icon & don't turn of you computer for many hours. However W2016 is fast and stable system but WU it's something horrible. And SCCM has nothing to do with it because WU is internal and not the orchestration around it and SCCM. There can be just improvement like using WSUS and some internal issues W10/W2016 have with searching for online update MS services and downloading http .cab crazy stuff. The new WU is a replacement of a previoud Update services that W10/W2016 provide and this is the crazy stuff that Microsoft introduced with W10.
Also, what are your updates scoped to? Are you installing critical CVE patches or everything? I can assure you that installing anything other than CVE and security patches is the wrong way to go so that may be why we dont see this issue. We dont install anything else, there is no point
I'm curious to know what you are using as an update platform? We have no issues on server 2016/2019 with updates. We are using SCCM, but then again our configuration is fine tuned and our servers have zero internet connection, which should be the standard for any corporation looking to secure its infrastructure
Server 2016 updates = TOTAL NIGHTMARE !!!
Stop this Horror Please!!!
Ad Admin commented
NO! Please DO NOT fix that!
Back when I was student, I made a lot of money by maintaining Windows computers.
Bugs like this and all the other reasons why I don't use Windows made it a very good business.
People who really need their own devices for making money are not using WIndows as their main-operating-system anyway.
Oliver Richter commented
YES stop this update Horror on WS2016 asap!!!
TrustedInstaller/Tiworker with 50-100 % utilization
Restart Durations over 30-40 min. without visible reason.
This is terror for the hard working IT admin.
It cannot be so difficult to solve this problem!!!
WS2016 updating is sooooo long.
And troubleshooting (read logs) is soooo nasty compare to WS2012R2.
Please fix it.
Another example. It is in the code. Proven.
Patching Server 2016 LTSC Core 1607 vs Server 2016 SAC Core 1803 + 2 installations from scratch (each about 3 minutes)
Watch yourself: https://1drv.ms/v/s!ApTx3d3fhinPgpk-2l8Vku1C26Pz7A
Server 2016 LTSC Core 1607
Size 1393,5 MB
Search Updates > 13 sec
“downloading” Updates > aborted after 28 minutes
Server 2016 SAC Core 1803
Size 835,8 MB + SSU 1,2 MB + Delta Update 287,6
Search Updates > 19 sec
Downloading Updates > 2 min
Installing Updates > 2 min 45 sec
Reboot / Applying Updates / logon > 48 sec (typo password measured 57)
Total Patch Times > 6 min 56 sec
Server 2016 LTSC shows the usual behaviour to report download while already installing the update. The status is not consistent with the actual process. This is valid for GUI and core and was fixed later in W10 1703 / Server 2016 SAC 1709
As we see now the process is broken by design, not by update sizes as abbodi86 stated.
The Server 2016 SAC 1803 has quite similar update speed as Server 2019
Despite the package size of 2019 is even smaller.
I don’t expect 2016 1607 Core to finish before minute 25 as last time.
If I am able to install a server in a time of 3 minutes the system cannot be powerless enough to patch anything within a reasonable time.
Just for fun we could install a second 2016 server from scratch to make the sillyness of this bug obvious.
I could literally setup 15 servers + patch them – in a timeframe where one of these 2016 1607 would be completed patching, or more depending if GUI or not.
Showing this a complete clean installation should remove all doubts the issue is by design, and MSFT has fixed it in later code.
you see the new 2016 server 1607 suffers even more issues. longer update search etc. so the 02-2019 and older SSU improved it – except the installation time and wrong display of “download” phase
ok at least there seems to be a relation of SSU and download if no older SSU was installed – interesting enough
KB3192137 – mysterious…
nevertheless even the new installed 2016 has the same installation speed, despite the download issue appears to be fixed.
seems the 2016 LTSC is crashed…
0 percent CPU makes me worried
But I think you get the point, the new installed 1607 isnt that fast either.
I will stop it here. not worth the time.
We’re a small non-profit with about 20 PCs and one physical Windows 2016 server. Updates that used to take an hour or so on a Friday evening with Server 2008R2 now take an entire day or longer with Windows Server 2016. Most recently I tried installing KB4480961 (the January 2019 cumulative update)—it ran for nearly four hours, failed, and then took another hour to roll itself back. Ugh.
Not sure what our long-term plan is yet, but a Synology NAS is starting to look better and better. Windows Server 2019 is available to us through software assurance but I’m reluctant to move to a server OS that was only released a few months ago.
Microsoft, please fix!
Same massive issues and problems here with Windows Server 2016 (inside virtual machines with 2016 as well as on the hypervisor side with Hyper-V based on 2016)
Updating 02-2019 2016 & 2019 Core comparison
Server 2019 LTSC Core
Search Updates > 6 sec
Download Updates > 33 sec
install Updates > 2 min 30 sec
Restart / Apply Updates + Logon > 45 sec
Total Patch Time 02-2019 CU > 3 mins 56 sec
Server 2016 LTSC Core
Search Updates > 28 sec
Download / (install*) Updates > 13 mins 52 sec
install Updates > 6 mins 8 sec
Restart / Apply Updates + Logon > 2 min 57 sec
Total Patch Time 02-2019 CU > 23 mins +/- 26 sec
Video via Onedrive for evidence Please share video / post until fixed.
Windows 10 19H1 Hyper-V
Test: Server Patches 2016 LTSC vs 2019 LTSC GUI.
2 vCore - Host i7700k @ 4,8 GHz
32 GB RAM
2x NVMe 970 EVO 1 TB (Storage Spaces, Mirror, Thin Provisioning)
Server 2019 LTSC GUI
Search Updates > 11 secs
Download Updates > 21 secs
Install Updates > 3 mins 16 secs
Restart / Apply Updates + Logon > 52 sec
Total Patch Time 02-2019 CU + .net > 4 mins 40 sec
Server 2016 LTSC GUI
Download / (install*) Updates > 22 minutes 10 secs
install Updates > 7 mins 7 seconds + 20 secs another search
Restart / Apply Updates + Logon > 14 mins 50 secs
Total Patch Time 02-2019 CU
without .net patches available > 44 mins 28 secs
this translates to storage with no NVME to patch times of several hours as reported in uservoice
*the progress bar is wrong altogether on W2016 it reports to download but is already installing for minutes as there is no network traffic and tiworker is consuming a whole core
if you imagine to patch 20-100 servers on VMWare or Hyper-V you can literally feel the CPU pressure and time consumed comparing to Server 2019.
Stephen Barrett commented
Staring at "Getting Windows ready Don't turn off you computer" for 3 hours - Disks and CPU on VM doing nothing at all . Eventually the VM reboots and another round of updates kick off....
Staring at "Getting Windows ready Don't turn off you computer" again for the last hour.....
The suspense in wondering if there are any more updates when I eventually get back to the desktop.....
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.
Joachim Dahl commented
Sitting here updating 1 hyæer-host and 2 virtual server 2016 machines naturally when things took longer than expected I turned to Google lol.
Dang if I had realized this was a problem I would not have started theas updates. Host is done in what shuld have takken 10-20 min max took 1.5h and now I am sitting here waiting I the virtual servers to finish.
Customer asked me how long this would take and my reply was well it usuallytakes around 1-2 hours (I always say a lot more than it takes so they don't complain when it takes longer lol)
From an active sysadmin in a small firm pleas fix this so my customers and me will stay happy
Matt I cannot agree more with your comments! I've been working with MS products for a very long time too, I too am fed up with direction they have been heading, the failure to adequately test and maintain products and there eye on the all mighty $ seems to be their ONLY priority in the last 15 years. They lost sight in what made them - the customer. I refuse to install ANY MS product that has been on the street for at least 2 years, at that point, it usually has most of the bugs worked out of it. Sad but true. Their rush to gain the $ is what's driving it. Want proof? Look at their move to SaaS (Software as a Service). They weren't making enough $. 2 pieces of garbage are Cortano & Edge, we don't need them them. If we don't want them, home users should be able to disable it. I know there are ways now. Another case of MS trying to strong arm everyone to use their products. We delete it immediately on our new Windows 10 installs at work. We NEED working links that are maintained better and faster updates to products that work the first time not needing updates which are 3X the size of the original software package. What are they thinking? Their solution is always to upgrade the OS, why? They didn't get it right the 1st time, why should we trust you'll do a good/better job with the next revision? The only difference is you'll have more of our money and we'll be farther down the rabbit hole with a new list of issues and we'll be beta testing your software for you again. Thanks Matt - I read your comments and started checking them off in my head, you nailed almost everyone I have had for years. I too am frustrated with the direction MS is heading and they don't seem to care about anything but the dollar. Thanks Matt!
No Lobbies At All commented
Buah ah ah...! Winzozz is a monolitic strong failed system and when it needs to change something it has to reinstall itself totally...! Buah ah ah...! For all that it needs you have to pay for...! Buah ah ah...! They impose to you their policy and you can forget totally your privacy...! Buah ah ah...! I hope the governs in the world change and totally clean, delete winzozz from the history...! Buah ah ah...!
No Bill Gates at all commented
Buah ah ah...! Winzozz is a monolitic strong failed system and when it needs to change something it has to reinstall itself totally...! Buah ah ah...! For all that it needs you have to pay for...! Buah ah ah...! They impose to you their policy and you can forget totally your privacy...! Buah ah ah...! I hope the governs in the world change and totally clean, delete winzozz from the hisory...! Buah ah ah...!