I have dealt this feedback and can provide you that update size alone is not the matter. There have been discussions that the reason is Defender or that 2019 has only 1/10 of update size comparingly to 2016 Server GUI / Core. MCP Windows Server, MCSA Windows 2008 / 2012, MCITP Hyper-V SCCM
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. *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 This translates to storage with no NVME to patch times of several hours as reported in uservoice Restart / Apply Updates + Logon > 14 mins 50 secs Install Updates > 7 mins 7 seconds + 20 secs another search net > 4 mins 40 secĭownload / (install*) Updates > 22 minutes 10 secs Test: Server Patches 2016 LTSC vs 2019 LTSC GUI.Ģx NVMe 970 EVO 1 TB (Storage Spaces, Mirror, Thin Provisioning) Video via Onedrive for evidence Please share video / post until fixed. I hope this helps others that may be experiencing similar issues.Īnd it still is, we should advocate for a working product Not experience the same slowness when installing this update. Now for the real odd thing, we run two VM environments Windows Hyper-V and Nutanix Acropolis.
This step during the update process was taking 2-3 hours.
What we witness when checking our update statusġ 13:37:10.6235744 7164 6620 Handler CBS called Progress with state=2, ticks=10, total=1000 The DCs on the other hand were receiving this update. The servers being updated by the WSUS were not being affected because we were not pushing KB890830 (Windows Malicious Software Removal Tool). The majority of our servers are updated viaĪ WSUS but our DCs were excluded from the WSUS policy because we wanted to control when updates were applied and when the DCs were restarted.
Windows updates on our DCs were taking 4-5 hours to perform the monthly rollup when pushing them manually. We experienced similar issues after upgrading to Windows 2016 Domain Controllers.
0 kommentar(er)
