{"id":5777,"date":"2018-06-01T02:31:58","date_gmt":"2018-06-01T00:31:58","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=5777"},"modified":"2021-03-02T05:44:41","modified_gmt":"2021-03-02T04:44:41","slug":"windows-server-2016-slow-updates","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2018\/06\/01\/windows-server-2016-slow-updates\/","title":{"rendered":"Windows Server 2016: Slow updates"},"content":{"rendered":"

[German<\/a>]Administrators of Windows Server 2016 systems may be used to trouble. If you are wondering about the extremely slow update installation on your machines: You are not alone.<\/p>\n

<\/p>\n

\"\"I came across this topic by chance and did some research. For several months now, Microsoft's Answers forums have seen frustrated administrators complaining about extremely slow updates to Windows Server 2016.<\/p>\n

<\/p>\n

This thread<\/a> at Microsoft Technet forum from July 2017 describes the dilemma, admins are facing:<\/p>\n

A client has a collection of servers that are running 2008r2, 2012 and 2016<\/p>\n

Is it just me or are the server 2016 updates just slow?! I had updated all the 2008r2 and 2012 ones in about an hour, yet the 2016 servers took the best part of a day to update and install!<\/p>\n

what's with that?<\/p><\/blockquote>\n

A customer runs a range of Windows servers, from Windows Server 2008 R2, through Windows Server 2012 \/ R2, to Windows Server 2016, where it is noticeable that Windows Server 2016 is extremely slow to install updates. While the older Windows Server versions are done with the update installation after one hour, the machines with Windows Server 2016 sometimes fiddle around with updates for a day until the system is ready to work again. Within the thread there are negations, and also explanations why this takes so long (size of the cumulative updates).<\/p>\n

If you search the Internet, you will find numerous other forum entries from people who complain about a slow update installation under Windows Server 2016. Also on reddit.com you will find this thread from November 2017<\/a>, where a software developer writes the following:<\/p>\n

Why is applying Windows Updates so slow on Window Server 2016 compared to Windows 10 that shares the same core?<\/p>\n

I use server editions (2008 R2 and 2016) as \"workstation\" OS in virtual machines for software development. While Windows 2008 R2 and 10 updates are fast, it takes almost 15 minutes to restart in case of Windows Server 2016.<\/p><\/blockquote>\n

Also there it is stated that older server editions install the updates quickly, while Windows Server 2016 falters miserably long. Mind you, we are not talking about clients that can be taken off the net and updated. These are servers that are supposed to run continuously. Another user points out, that this is a known issue in the RTM version:<\/p>\n

Windows Server 2016 RTM has a known issue with Windows Updates. The first cumulative update takes like forever. Install the latest Windows CU manually (download and run it). Afterwards it's not so bad anymore. Don't get me wrong, it's still bad, but a lot better than the RTM version.<\/p><\/blockquote>\n

November 2017 update KB4048953<\/a> should fix the problem of slow update installation. But at spiceworks there is this thread<\/a> from March 15, 2018, where a user complains again about the same issue.<\/p>\n

I'm installing (or trying to) on some of our servers this morning and they are taking crazy long.\u00a0 THe 2012 R2 machines had all their patches installed in about 10 minutes.\u00a0 The 2016 machines are taking 45+ minutes to install their 1 patch and then after rebooting are getting hung up at \"Getting Windows ready\".<\/p><\/blockquote>\n

German site Golem proposes<\/a> to use a manual update installation as a workaround to fasten update installation. What's your situation? Are you affected by slow update processes on Windows Server 2016, or is that no longer an issue?<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Administrators of Windows Server 2016 systems may be used to trouble. If you are wondering about the extremely slow update installation on your machines: You are not alone.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[47,195,483],"class_list":["post-5777","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-issue","tag-update","tag-windows-server-2016"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/5777","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=5777"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/5777\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=5777"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=5777"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=5777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}