none
Windows Server 2016 Updates slow!

    Question

  • It's has become a real nightmare updating Windows Server 2016.

    Updates take forever to complete.

    Sunday, March 25, 2018 1:18 PM

All replies

  • Sunday, March 25, 2018 1:33 PM
  • Hi,

    I want to confirm with you which step takes long time:
    1. Check/download update.
    2. Install/configure update.

    If system built-in Windows Update takes long time to complete, please confirm that if manually download and install update will have same problem.

    Windows 10 and Windows Server 2016 update history:
    https://support.microsoft.com/id-id/help/4000825/windows-10-windows-server-2016-update-history

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 26, 2018 9:20 AM
    Moderator
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 28, 2018 3:08 AM
    Moderator
  • Hi,

    Is there any update?

    Please click “Mark as answer” if the reply is helpful. It would make this reply to the top and easier to be found for other people who has the similar problem.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 30, 2018 1:43 AM
    Moderator
  • Dear Eve,

    That's what we do at the moment.

    Windows Server 2016 displays the updates, we download them and apply them by hand.

    In that way we have more control over the update.

    However it still takes a long time installing the update.

    Regards,

    Adam

    Saturday, March 31, 2018 4:28 AM
  • Hi,

    >However it still takes a long time installing the update.
    So, Windows Update installation process will takes a long period of time. 

    If possible, try to re-start system in Clean Boot(do not manually start any 3rd party process) and try to install update and check the result. 

    Perform a clean startup to determine whether background programs are interfering with your game or program:
    https://support.microsoft.com/en-us/help/331796/perform-a-clean-startup-to-determine-whether-background-programs-are-i

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 2, 2018 11:17 AM
    Moderator
  • Dear Eve,

    We have 20+ windows server systems and they are all different (CPU, memory, motherboard, configuration).

    No third party processes running.

    Maybe you just have to admid that's it's different from Windows Server 2012/R2.

    However we are not allowed to go back (SPLA agreement)

    Regards,

    Adam

    Monday, April 2, 2018 2:54 PM
  • Hi,

    If same problem happens on multi OS, with different hardware configuration. I will post such problem to product group, and thank you for your feedback.

    Also, you can post your feedback by yourself via Windows Server – General Feedback forum:
    https://windowsserver.uservoice.com/forums/295047-general-feedback

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Tuesday, April 3, 2018 11:08 AM
    Moderator
  • There is something wrong here.  I have always had my servers apply updates at 4:00am(it gives backups a chance to finish and still will complete the reboots and come back online before 8:00am)  With Server 2016, I am forced to use gpedit to control the different days of the week(I cannot simply use a maintenance window of 4:00 for all of my servers to reboot at the same time on the same day), but I am now having issues with Server 2016. We always tell our servers to reboot for updates when needed(so they do not hang out and wait for a user to reconnect to a session and then that user logs out of a session in the middle of a business day, then it decides it can finally reboot)

    So at 4:00:09am I get event ID 43-WindowsUpdateClient has started installing the following update..." and then the server finally reboots 4+ hours later.  I have no issues with 2008r2, 2012r2, but I do with 2016.


    Dave


    Monday, April 23, 2018 5:22 PM
  • I've done 3 2016 servers now.  All updates very sluggish.  Including ones right after a clean installation of the OS.

    Latest example...had to manually download Security Update for Windows (KB4103723) because it wouldn't finish the download process on it's own. 

    Then started applying it at 5:39am.  Still running at 6:57am.  Looks to be maybe 20% complete.  Can't really tell because the update process gives us really no useful information on estimated time.

    I've been working on Microsoft servers since LAN Man and I've gotta say that this is probably the worst mess for updating I've ever experienced.  


    Monday, May 14, 2018 12:02 PM
  • I can confirm that the problem exists.

    I've just downloaded a latest Windows Server 2016 Standard Version 10.0.14393 from Microsoft Volume License Portal and trying to update it with latest updated from Microsoft Update site

    The "preparing to install" phase in extremely slow and looks like process (Windows Modules Installer Worker) consumes only 1 CORE.

    When this behavior gonna be fixed, Microsoft?

    Friday, May 18, 2018 9:53 AM
  • I can confirm that the problem exists.

    And another "same here". Hours and HOURS to apply updates, sometimes an hour to restart too. No 3rd party AV solution to blame. Disappointed to see this has been a known problem for some time with no official word from Microsoft on a resolution. Time for a slashdot article maybe? 

    Sunday, May 20, 2018 9:50 PM
  • Complaints from all around the world.  Why no fix yet?? 
    Tuesday, May 22, 2018 6:35 PM
  • I can confirm that the problem exists.

    And another "same here". Hours and HOURS to apply updates, sometimes an hour to restart too. No 3rd party AV solution to blame. Disappointed to see this has been a known problem for some time with no official word from Microsoft on a resolution. Time for a slashdot article maybe? 

    The problem definatly exists, we need a fix to this asap.
    Tuesday, May 22, 2018 11:43 PM
  • This is a similar response that you had with posts dating back in 2017.  Can we get an update on the direction of Microsoft on this issue?  Clearly, there is information out there that could be provided to us so we can quit going to message boards talking about how bad this is.  Is there a chance that Win 2016 throttles bandwidth on updates to the point of running out of time?
    Wednesday, May 23, 2018 12:15 AM
  • Please upvote the OP in this post if you are affected by this. I have some hope maybe that will flag this to someone...
    Wednesday, May 23, 2018 9:01 PM
  • It's has become a real nightmare updating Windows Server 2016.

    Updates take forever to complete.

    Agreed Windows Server 2016 has gone backwards for the update process.

    It taking MUCH longer and failing much more.

    The more 2016 servers we deploy the more I'm feeling my monthly updates taking much longer and becoming more painful.

    I had 3 x 2012 R2 servers this morning took 20 mins for the May updates. 1 x 2016 server took 2.5 hours.

    Microsoft need to do something.

    Thursday, May 24, 2018 3:33 AM
  •  "Upvote the OP" ???

    How do I do that?

    Friday, May 25, 2018 6:49 AM
  • Up at the top. Not sure if it does help as the other thread  I linked at the top has 11 votes.

    Monday, May 28, 2018 6:34 PM
  • Upvote to help get the story posted on /. 

    https://slashdot.org/submission/8244004/windows-server-2016-has-an-updating-problem

    Wednesday, May 30, 2018 8:59 PM
  • Hi,

    Same thing.
    Very slow when installing updates ....

    greetings
    Michael

    Friday, June 1, 2018 1:27 PM
  • We experienced similar issues after upgrading to Windows 2016 Domain Controllers.   Windows updates on our DCs were taking 4-5 hours to perform the monthly rollup when pushing them manually.   The majority of our servers are updated via a 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.

    The servers being updated by the WSUS were not being affected because we were not pushing KB890830 (Windows Malicious Software Removal Tool).  The DCs on the other hand were receiving this update.  What we witness when checking our update status the following was occurring:

    2018/05/31 13:37:10.6235744 7164  6620  Handler         CBS called Progress with state=2, ticks=10, total=1000

    This step during the update process was taking 2-3 hours.  Now for the real odd thing,  we run two VM environments Windows Hyper-V and Nutanix Acropolis.   This update was being pushed to all DCs.  THe DCs running on Acropolis did not experience the same slowness when installing this update.   I am still investigating why that is.   I hope this helps others that may be experiencing similar issues.

    Friday, June 1, 2018 1:39 PM
  • This is a real issue with Server 2016. It's not individual systems. This issue occurs on every Server 2016 host and VM that I manage.

    The update timescale is just way too long. It's got to the point where there is not enough time to backup all of our VM's, then update them all, in a night. Who wants to spend all night nursing a HV host through updates anyway.

    Come on Microsoft. you need to sort this out or I will I send you my overtime bill.

    Friday, June 1, 2018 2:22 PM
  • I can confirm this problem. Happens on physical and virtual Windows 2016 servers, Standard and Datacenter with GUI.
    Saturday, June 2, 2018 12:18 AM
  • After disabling Windows Defender before updating updates take about one and a half hour instead of almost four hours.

    So part of the problem is Microsofts own feature which is enabled by default..

    Wednesday, June 6, 2018 11:16 AM
  • Just to share my experience: I updated 4 physical nodes cluster (2012R2) with last Tuesday patch in about two hours.

    Now I'm updating a 4 nodes physical cluster (2016) and the first node is still updating for over two hours...

    All nodes are 24 core / 192GB RAM: almost no CPU usage nor disk activity...

    Very disappointed...

    Wednesday, June 20, 2018 8:31 PM
  • I have 8 servers I am responsible for.

    I install all the Microsoft Updates every month.

    All 6(six) 2012 servers download and install the June updates in 5-10 minutes, and 2-3 minutes to reboot.

    The two 2016 servers failed repeatedly when attempting to even check for updates. So I rebooted both servers, was finally able to check for updates from Microsoft. Then it takes about 30 minutes to download and install.

    Then I actually timed the first one and it took 34 minutes to reboot back to the logon screen.

    Why, why, why does a "new and improved" Server O/S take 3 times as long to download and install updates and 10 times as long to reboot (and finish installing)?  This is really, really bad.


    Thursday, June 21, 2018 12:13 AM
  • Just to share my experience: I updated 4 physical nodes cluster (2012R2) with last Tuesday patch in about two hours.

    Now I'm updating a 4 nodes physical cluster (2016) and the first node is still updating for over two hours...

    All nodes are 24 core / 192GB RAM: almost no CPU usage nor disk activity...

    Very disappointed...

    Quick update: using the 'interactive' installation (no WSUS) has sped the things up, for sure... despite multiple reboots due to failed patch installation. I had to install the KB4284880 twice on every single node...
    Friday, June 22, 2018 7:31 AM
  • Currently waiting about an hour or more on multiple VMs using "sconfig" to install updates on 2016.  CPU fluctuates and is never really idle, and definitely not being maxed out.  Watching for a little the average CPU is 25% max.  Most VMs are 4 CPUs and 8gb of memory.

    Why the hell does it take so long to do updates?  Has anyone ever put in a ticket with Microsoft so we know they are at least aware of the problem?  I've been on a few forums and tons of people are having this problem.  Out of about 8 2016 VMs, I think I had one install at 5am on it's own... and it took a while to install/reboot.

    Very frustrating.

    Wednesday, July 11, 2018 5:25 PM
  • Yes windows server 2016 has a real issue with updates. half the time, it fails to install and tells you to try again later. Then once it is installing, it sometimes can't completed it and you need to try again later. To make things even worse, it takes forever to install updates. We can't have people waiting around for hours to install an update. What is going on here with updates compared to other version of servers like 2008 and 2012 being quick and normal to install updates?
    Sunday, July 22, 2018 5:06 PM
  • I agree.

    I found a rule that gives some relieve:

    Do not combine a "malicious software removal" with a cumulative update.

    First install the cumulative update: download from windows catalog and install by hand.

    After reboot install the "malicious software removal" with Settings -> Windows Update.

    Sunday, July 22, 2018 9:33 PM
  • Added something to uservoice for those interested:

    https://windowsserver.uservoice.com/forums/295047-general-feedback/suggestions/34907032-windows-updates-shouldn-t-fail-constantly-or-take

    Monday, July 23, 2018 5:14 PM
  • Server systems using NLB (Network Load Balancing) fail on autoupdate or update with user interface. Manual installation cumulative update works ok.
    Tuesday, August 21, 2018 9:16 PM
  • Welcome to the club. One noticeable improvement was when I prevented the Anti Virus from on file access scanning the c:\windows\softwareDistribution folder.
    Tuesday, August 21, 2018 9:30 PM
  • How many of you have delta updates enabled on WSUS?  I've read that seems to mess up the updates on 2016.  I'm going to try next month without and see what happens.  I doubt it is going to make a big difference.
    Wednesday, August 22, 2018 11:57 AM
  • Some updates installed on one of my Terminal Servers running Server 2016 this morning, kicking out all the users logged on that particular server...  Rebooted on the "preparing updates" screen.  Stayed there for 25 minutes and then rebooted again.  Came back to the "installing updates" screen for another 30 minutes and rebooted again!  Came back again to the "installing updates for another 15 minutes and finally came back online!

    I have some servers still running Server 2008 and those are much faster to update. I greatly regret throwing away my Citrix farm infrastructure running on Server 2008 for these Windows Server 2016 terminal servers.  Lot of issues with processor and RAM ressources, freezes etc.

    Microsoft should look at the English definition of the word "upgrade" because moving from 2008 to 2016 was definitely not an upgrade in many aspects.

    We can clearly live and experience what can a monopolistic empire can do to customer care and service...

     

    Tuesday, September 4, 2018 2:33 PM
  • Same issues here: 2016 server takes forever to install updates, seems to be stuck already  in "Preparing windows" after clicking on "restart" to install the update.

    No such problems on 2012 (R2) or SBS2011 (before it was migrated to 2016)

    Monday, September 24, 2018 1:37 PM
  • Another "me too"!

    Stand-Alone Hardware, fresh install Server 2016 Standard (2 x CPU E5-2620 v4 @ 2.10GHz, 16 Cores, 64GB RAM, 2 x 480GB SSDs RAID1), getting updates from our local WSUS. KB4462917 from 2018-10 takes 56,57 minutes from clicking on "check for updates" until OS is rebooted. It makes no difference, if updates are installed directly via Windows Update or manually...

    Is it possilble to get some kind of useful Information from Microsoft concerning slow 2016 Server updates?



    Wednesday, October 10, 2018 12:59 PM
  • Sadly, I came upon this post whilst searching for a reason why a CLEAN install of Windows Server 2016 took (a) 4 hours to apply stage 1 of updates, then (b) over an hour "booting" - "Getting Windows ready - don't turn off your computer". Whilst waiting for the server to boot - applying updates - the server is useless, no services running. This creates a problem going forward: do you take the risk of installing updates at all? If you do, you risk your server being "unavailable" for several hours - during which time users of those services are beginning to complain. The puzzling thing is, the Server 2016 machines have really high specs - fast SSD boot disks, fast SSD NAS, plenty GB of RAM, multiple core CPUs. Is it time to go Linux?
    Sunday, October 28, 2018 10:42 AM
  • I can confirm as well. New physical 2016 install on SSD in an HP DL160 Gen 8. Windows updates are running on a single logical processor of the 24 available (2x Xeon E5-2620) .  KB4462917 ran about half an hour, got stuck at 64%, then failed.  I hit retry, stuck at 55% at the moment.  We see this on our other servers with completely different hardware as well. 

    I just tried update KB4462928 on an IBM Blade server with 96GB of RAM and 16 logical processors physical machine on Samsung 850 Pro SSDs.  Same exact behavior. Only 1 logical of the 16 is engaged (Xeon E5520).  Neither of these systems is doing anything but installing Windows Updates. No other loads.

    Therefore, at least from my vantage point, Windows Updates on Server 2016 would be much faster if they used more than one logical processor.


    • Edited by K5555212 Friday, November 2, 2018 7:23 PM minor edits
    Friday, November 2, 2018 7:15 PM
  • Upvoted. This is a serous problem that is wasting serious time=money. Window Server 2016 is now in "Preparing to install updates 72%" for >10 minutes. I finished updating 2012R2 servers hours ago.
    Friday, November 2, 2018 7:51 PM
  • Hi hifly, 

    It is annoying. 

    What I did to speed things up is:

    Download the CU (KB) from Microsoft Catalog.

    Exclude the following folders in Defender:

    C:\Windows\CbsTemp

    C:\Windows\Logs\CBS

    C:\Windows\SofwareDistribution

    You can do this with Powershell command Add-MpPreference.

    Add / remove the defender exclusions before / after rolling out the CU.

    Make sure you roll out the Malicous Software Removal (MSR) KB after all other updates.

    Often MSR starts and shortly after that the CU starts. That's a bad combination to run.

    Friday, November 2, 2018 8:41 PM
  • Before running the latest CU, read this from Microsoft.

    Install KB4465659 first!!!

    Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security fixes. For more information, see Servicing stack updates.

    If you are using Windows Update, the latest SSU (KB4465659) will be offered to you automatically. To get the stand-alone package for the latest SSU, go to the Microsoft Update Catalog

    Wednesday, November 14, 2018 7:41 AM
  • I added an extra exclusion for Windows Defender

    C:\Windows\WinSxS\Temp

    It helps, however CU is still a lengthy process.


    Wednesday, November 14, 2018 3:20 PM
  • believe me that the best practice is to go to services and disable the fucking module of updates, I'm sick of windows :(
    Tuesday, November 27, 2018 5:23 PM
  • Windows Server 2016 or Windows 10 ?
    Tuesday, November 27, 2018 7:49 PM
  • The problem is Microsoft is a cheap SOB that makes your 2016 install check every file with the cloud so it can determine how much to download.  Its all about saving CPU and bandwidth on your end.  Its a cluster.
    Saturday, December 1, 2018 1:49 AM
  • I'm having the same issue with many of my updates on server standard 2016. They seem to take about 1-2 hours on average, This is costing small businesses who contract IT work a lot of money in management.
    Saturday, December 8, 2018 8:11 AM
  • This is driving me crazy. 30 update fails later, I am now desperately trying to find a way to get my update to even work. Learning from this thread that manually updating apparently helps, I am now 3 hours into a CU from May..... I really hope this doesn't mean I have to do this for every month up till now.

    Why the radio silence from Microsoft on this? This is a massive issue.
    Thursday, December 27, 2018 2:14 AM
  • We are having the same random issues with Windows 2016.   One patch wouldn't install thru Windows Update but it did install thru a manual process
    Friday, December 28, 2018 1:23 PM
  • Another "me too"..... It took a whopping 12 hours yesterday to install updates on 4 hyper V Vm's and 2 hosts. All running server 2016. Today I'm in yet another 4 hour hell installing CU11 for Exchange and all it's prerequisites. To say this is getting out of hand is the understatement of the year.
    Monday, December 31, 2018 1:02 AM
  • About Exchange CU: Windows Defender must be disabled in order to complete the installation in a reasonable amount of time. I ran in the same situation and disabling it saved me several hours.
    Monday, December 31, 2018 9:52 AM
  • Make sure you roll out the Malicous Software Removal (MSR) KB after all other updates.

    Often MSR starts and shortly after that the CU starts. That's a bad combination to run.

    Monday, December 31, 2018 2:19 PM
  • Did you try to be selective?

    Exclude the following folders in Defender:

    C:\Windows\CbsTemp

    C:\Windows\Logs\CBS

    C:\Windows\SofwareDistribution

    You can do this with Powershell command Add-MpPreference.

    Add / remove the defender exclusions before / after rolling out the CU.

    Monday, December 31, 2018 2:20 PM
  • Another MS DORK trying to inform us about what we are doing wrong. Once again BLAMING us..the end users. Fuck you. 2016 Server is a fucking nightmare....period. Updates....fucking hell. Reboots, fucking hell.

    MS, fucking hell.

    MS...just fuck off and die.

    You fucking suck at programming. Start using a keyboard instead of this shit our of your assholes.

    Tuesday, January 1, 2019 10:34 PM
  • Can you see why people are frustrated? Standard corporate blame game on the little guy with no say in what they have to provide?

    We are NOT thick. We have been doing this for longer than some of your own employees, so give us some credit.

    Livelihoods at stake because questions are asked of US, not you Mr Microsoft Sir...

    Small businesses and schools relying on your products, because our leaders don't know any better and think Microsoft are the only solution. Downtime is not an option for us, we have no resilient server farm.

    Your stuff has got to be more end user friendly, not just your desktop OS.

    Come on Microsoft. Either fix the problem or take responsibility publicly so we are not FIRED.

    Tuesday, January 8, 2019 7:56 AM
  • This month with KB4480961 we have seen a couple of failures on a couple of our servers.   To me it seems like an issue with the trustedinstaller perhaps timing out while shutting down, we have to manually download the patch and it finally went thru on some of these.    Are there any hotfixes for these issues on Windows 2016?

    Thanks in advanced

    19 hours 18 minutes ago
  • This month we had no failures.

    However, we use WSUS, approve one update and roll out one update.

    We repeat this process a number of days until all updates are applied.

    I always start with the "malicious software removal tool". 

    Next day I pick up the CU.

    18 hours 46 minutes ago