none
what's with the really slow windows updates on 2016?

    Question

  • A client has a collection of servers that are running 2008r2, 2012 and 2016

    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!

    what's with that?

    Monday, July 17, 2017 2:28 PM

All replies

  • servers took the best part of a day to update and install!

    what's with that?

    Not sure what "best part of day" is time-wise but probably not normal, may need to check log files and or event logs for clues.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Monday, July 17, 2017 2:31 PM
  • Hi,

    I want to confirm with you that if there is WSUS server configured for Windows Update?

    In general, below are general processes for Windows Update:
    1. Check for Windows Update.
    2. Download Windows Update.
    3. Install Windows Update.
    4. Re-start the system to complete the installation(optional).

    Windows Update speed may be affected by several factors at each process. Such as network bandwidth, availability of windows update server, local server free resource, and etc. First to identify which step/specific update takes too long time, then, using appropriate log/tool to have an further identification.

    In general, if there are numbers of updates to be installed, it is recommended to install them one by one in a natural order of time sequence. As part of Windows Update is installed as pre-requirement for later Windows Update. Also, system re-start might be necessary to complete specific Windows Update installation.

    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, July 19, 2017 6:38 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.

    Friday, July 21, 2017 6:17 AM
    Moderator
  • All here are correct; Windows 2016 Server updates are extremely slow to install.

    Do we need to install each update separately?

    That negates any automation doing separate updates.

    Maybe the answer is to reduce the size of each furture update and not try to do HUGE CUMULTIVE updates.

    This issues has been raised in many Windows 2016 forums; not just this forum.

    Thursday, August 17, 2017 11:52 PM
  • Do we need to install each update separately?

    The updates are now cumulative. When you install the latest update only the delta updates (from previous cumulative) would be applied. I don't have problems with any of servers here both physical and virtual.

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Friday, August 18, 2017 2:46 AM
  • We are also experiencing very slow updates on ALL Windows Servers 2016. The servers are also very slow to reboot after patching is done, it can take anything between 1-60 minutes before the server actually reboots after a patch. Another problem we have is that SCCM fails to install Monthly rollups on most of the Windows Servers 2016, works fine with the rest. We are not happy with the change that is implemented in Windows Server 2016 patch process, I get a lot of Vista vibes. 
    Saturday, September 23, 2017 1:03 PM
  • Hi,

    I quietly understand the inconvenience this problem had brought to you. As mentioned above, Windows Update (including search, download, install, configure) may takes a period of time, depends on many factors. 

    I will post your feedback about update problem on Windows Server 2016 to product department, also, you can post your suggestion/feedback 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, September 26, 2017 8:17 AM
    Moderator
  • Hey bubba, We know what cumulative means but the issue is that the cumulative updates are so freekin large that it takes forevere to install even on a new all flash drive server (virtual or physical). Updates need to be made smaller so this does not happen. It does not matter if WSUS is used or not; it is the length of time it takes a cumulative update to install on Windows 2016 server that is the problem.

    Microsoft seems to continue to GO BACKWARD and not forward when it comes to development. Billions of dollars are spent for licensing of MS enterprise products so we deserve better.

    Sunday, October 29, 2017 5:07 PM
  • We're experiecing the same issue on our 2016 servers. All flash or not, it is extremely slow. It gets stuck on "Preparing installation of updates" at 10% for what seems like an eternity. I'm afraid to update my new servers because the long downtime that affects our users. 

    Brand new 2016 Domain Controllers choking for 30-60 minutes before you can press the reboot-button to make it go offline... I have a feeling our organization will want to behead me everytime I need to update our servers.

    Edit: Is it supported to use DNS alias to redirect traffic from a domain controller to another while you install updates or will that mess up Windows Update for me aswell?
    • Edited by vnip90 Tuesday, October 31, 2017 1:00 PM
    Tuesday, October 31, 2017 12:59 PM
  • Hi,

    In general, domain client will try to contact the DC which one it had successfully contacted before. New domain client will try to contact a DC which can respond to its request(try another again when first one is failed). 

    As far as I know, client using DNS RRs to fund DC, in order to manually avoid client to contact the crashing/no-responding DC, a method would be edit the DC relate RRs, however, it is not recommended as it may cause problem and may need large manual workload.

    For now, please try to install update during non-production time, and if possible, make the DC offline to install update, and make it online after completing the update installation. 

    For update installation takes long time problem, if necessary, I would recommend you to post a new thread, or, open an case with Microsoft, provide detail information about your environment, such as system information, hardware, update log etc. It may help to have an further identification.

    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, November 1, 2017 10:45 AM
    Moderator
  • Another "me too" here regarding the performance of updating Windows Server 2016. I did notice this whilst first creating templates for these machines, but brushed it off. But sat here applying the following updates to a very clean / vanilla deployment of Windows Server 2016 with Desktop Experience:

    2017-08 Update for Windows Server 2016 for x64-based Systems (KB4035631)

    2017-10 Cumulative Update for Windows Server 2016 for x64-Based Systems (KB4041691)

    So far it's been running for an HOUR, and no idea how much longer left to run. Not sure if it's just the fact that the cumulative update process obscures how many actual updates are being installed (which, in and of itself I'm not particularly fond of.. but that's for another thread) but it does seem painfully slow. Yeah, sure this is a small VM (2 vCPU, 4GB RAM) but we have hundreds of Windows Server 2012 R2 machines of a similar spec which will rattle through their updates at a considerably faster pace.. this slow installation does seem to be a very noticeable behaviour in Windows Server 2016.

    Edit

    Updates finished installing - took about an hour and ten minutes. Clicking on restart took a further 11 minutes (almost to the second) to be returned to the login screen. So almost an hour and a half to update a clean / application free Windows Server 2016 image with two updates. Really?



    • Edited by UKchicane Thursday, November 9, 2017 3:56 PM
    Thursday, November 9, 2017 3:42 PM
  • Hi,

    Thank you for your detail update and description.

    I will post this problem to relate group department, your suggestion and feedback is always welcome as they are helpful for improving our products and services.

    Also, if there is any suggestion/feedback, you can post on below link:
    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.

    Friday, November 10, 2017 6:40 AM
    Moderator
  • Just as a follow up, I was updating a Windows 2012 R2 template today. That actually had more updates than what I was installing on the 2016 template - the monthly roll-up updates for June onwards (so a total of 5 monthly roll-ups), plus an IE cumulative update.. that took a total of 7 minutes before needing a reboot. It also shutdown and restarted an awful lot quicker. The VM is configured with the same specification / resources and is on the same storage as the 2016 templates.
    Monday, November 13, 2017 3:03 PM
  • Hi,

    Thank you of your detail update. I had already post your feedback to product group.  

    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, November 14, 2017 3:03 AM
    Moderator
  • Hi,

    We have also extremely slow installation for Windows 2016 Server updates. KB4048953 was taking more than 40 minutes and the reboot was 5-10 minutes.


    /SaiTech


    • Edited by SaiTech Sunday, February 18, 2018 4:09 PM
    Monday, November 27, 2017 6:45 PM
  • Hi,

    @ SaiTech

    In general, one thread mainly discusses one question for specific customer as environment, system patch level and etc. factors may be different. So, please post a new thread and provide detail information about your system, such as OS name and version.

    Thank you for your understanding.

    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, November 28, 2017 9:40 AM
    Moderator
  • Have you check the windows update logs?


    www.sevenitblog.com

    Tuesday, November 28, 2017 10:05 AM
  • Dude, of course we're checking the windows update logs. If you read between the lines here, it is professionals complaining who have experience with patching other OSes and we are comparing that with the relative performance of deploying these updates.

    The robot that's just sitting here saying "...you can post your suggestion/feedback via Windows Server - General Feedback forum" is not helping either.

    For what it's worth, I too am having serious performance problems with installing patches on freshly-built 2016 servers. I have the same performance problem if I install the first ones from Windows Update, and then try and deploy the next month's via SCCM.

    I'm literally sitting here looking at UpdatesDeployment.log tell me that:

    <![LOG[Update (Site_5A949416-929E-4121-A1F3-9B6CB6502058/SUM_0a541419-914d-4e57-93fb-5d51a0049ec7) Progress: Status = ciStateInstalling, PercentComplete = 20, DownloadSize = 0, Result = 0x0]LOG]!><time="22:48:07.173-660"

    ...after the install task was kicked off at 22:31, and I'm looking at that log at 23:03. The machine is not oversubscribed in RAM, CPU or disk I/O.

    ...Oh look, it had failed after half an hour, with CBS.log saying Client aborted the install.

    Even with the maximum run time set to 60 min on the package, as it was when it was first deployed. Still at 20% complete according to UpdatesDeployment. The majority do succeed (it's true that this server may have a machine policy refresh problem, maybe), but after taking at least an hour

    It may be true that only the delta updates actually get INSTALLED out of the cumulative packages. However, the time to download these mega-packages and then presumably check each component to see if it's required is not at all efficient.

    I like the idea of having cumulative update packages so that you can deploy them to new servers and be sure that no un-superseded update that was in a deployment group from 3 years ago will be missed. But only as an option, and really, only if they're able to install efficiently.

    Thursday, November 30, 2017 12:40 PM
  • I would like to sign up for every line in your message!

    This new Updated Policy for Windows Server 2016 is just awful. IT Corporation like Microsoft should spend a LOT MORE TIME testing all new features and updates BEFORE publishing them.

    I'm currently sitting for more than 1 hour updating latest WS 2016 build with more than 96 GB RAM and on SSD disks! These Preparing for Install takes forever!

    I really hope that Microsoft support engineers will see this thread and forward to appropriate specialist to fix this nonsense! 

    Saturday, December 2, 2017 10:06 AM
  • I would like to weigh in also. I have an environment with many hundreds of Server OS's 2008, 2012, 2016 and many variants thereof, but it is only the Windows 2016 servers that seriously feel like a huge step backwards for inclusion into an enterprise environment.

    The interface is inferior for 2016 -- in no way at all do the downloaded Windows Updates reflect accurately as to the true download status of the Windows Updates files in Server 2016.  For example, with this new "Windows 10" window, the download will be stuck at 11% for an hour, then at 45% for another 30 minutes or so, and then quite often complete with an error status of "We couldn't install some updates because the PC was turned off", when in fact the server was never turned off.

    Simplicity is great in a *consumer* UI if your end-user is not that technically oriented.  This new "simple" interface is a nightmare for admins like me that care about knowing simple things such as:  What is the correct percentage of the file currently being downloaded?  How large is the file, and how much space is being occupied by the download?  Where is the xxMB of xxMB currently downloaded dialog at?  Why in the world did the development team think it was a good idea to replace all of the working Windows Updates parameters that admins used to have access to with an "SCONFIG" console that has to be invoked via Powershell?  Seriously, did you fire every single project manager and UI specialist you have?

    That's just the tip of the iceberg.  Server 2016 is buggy, flaky, and a HUGE step backwards in almost all aspects of interoperability so far even in terms of comparison to Windows Server 2008.  I'm sorry if this sounds very anecdotal and ranty, but I'm expected to deploy some new Server 2016 servers that have me literally sitting on my hands while I deal with this new dips&*t update system that takes five times longer to update and provides me with hardly any feedback as to what is going on with live updates.

    At this point my preference remains for deploying 2012 R2 servers, because 2016 is really not ready for prime time. I understand that yes, I have ways of figuring out what is going on via Perfmon, Event Logs, Task Manager, Powershell, etc... but PLEASE do not make me use a dozen tools just because you don't want to write a nice interface wrapper for Windows Updates.  I should be doing real, actual work right now rather than endless troubleshooting this Server 2016 that should still be in RC stage.

    Monday, December 4, 2017 9:57 PM
  • I completely agree. The time it takes to install updates in 2016 is unbelievable. I have HV hosts that take 30 minutes to reboot and get their guests back online after applying an update. That is after waiting an hour for the update to apply. THEN some systems come up and want to apply the update AGAIN. It wasn't applied the first freaking time? That leads to more downtime and lost sleep.

    Tuesday, December 5, 2017 3:14 AM
  • I have to say this Slowdown with 2016 updates is incredibly inconvenient - A Hyper-v cluster that used to take a few hours to update in 2012R2, is now taking me a whole weekend to update in 2016.

    The Fact that it also applies Cumulative updates one after the other is bonkers. Apply Novembers CU - reboot - Decembers CU is waiting to be updated now. Why didn't it just apply the December CU in the first place??? Or are they not really Cumulative despite the name?

    Wednesday, December 13, 2017 9:07 AM
  • Hi,

    Have you tried to disable the Defender Real-Time Protection, for a test (Or other AV RTP)?


    /SaiTech


    • Edited by SaiTech Tuesday, December 26, 2017 8:30 PM
    Thursday, December 21, 2017 12:31 PM
  • I need to add to this also. I just spent the last 45 minutes patching a single 2016 server. The patch was the monthly (or biweekly in some cases) cumulative patch. It isn't related to the download because I have it setup to download first, then install when I'm ready. It isn't related to hardware because I'm monitoring that through my hypervisor and the hardware isn't taxed. It is the rebooting and the forever spinning applying the patches. It is really bad to have servers down for a half an hour on average for patching so often. Having redundant DCs and related equipment is good business practice, but doing it in excess because of a poor patching process is tough to justify.
    Sunday, February 4, 2018 3:28 PM
  • The update system that Windows server 2016 uses is just completely useless and not fit for purpose. Every week I will have to manually install the updates as it just fails all the time. Whoever was put in charge of the update system has really failed, sorry!
    Monday, February 5, 2018 5:48 PM
  • Every Windows 2016 Server that we have deployed is taking over an hour to install any MS updates. This is true for new installations that have nothing on them but the Windows OS. All hosts have plenty of RAM/CPU no third party software interfering. The downloads of the MS  updates is quick, installing is not. All other Windows OS versions  we have are quick to install comparative to Windows 2016.

    Does anyone have a case open with support looking at this?

    Regards,

    John

    Thursday, February 15, 2018 7:36 PM
  • Hi,

    Is there any one how have tested this with RTP?
    Have you tried to disable the Defender Real-Time Protection, for a test (Or other AV RTP)?

    Does anyone have a case open with support looking at this?

    We have had and have MS support case. It is a slow process, and the full story is not revealed yet. And this is such case that is Microsoft supports weakest point (spanning different support team). I can do understand it is complex, but there is quite many with the same issue, so there most be some pattern to dig in to.

    For the moment we talking with the defender support team.

    Our Servers 2016 VMs is on Server 2012 Hyper-V host, on server 2012 R2 SoFs cluster. But we even see slow installation on physical servers. We now use to put 60 minutes max runtime for Windows Server 2016 cumulative in SCCM, but is also limit the maintenace windows. So it is a puzzle to get Everything to work, and for a system administrator all the hassles take away your precious time!


    /SaiTech

    Sunday, February 18, 2018 4:43 PM
  • Just adding to the conversation and reporting the same thing. Im, as we speak, waiting for a 2016 server to just reboot to start the installation at over 20 minutes. This wont count the time it takes for the reboot process to actually finish. Ive experienced this in the past taking over an hour. Something needs to be done or changed to fix this. Luckily, this is a secondary server so downtime does not matter, but Im sure its not that way for everyone.
    Thursday, February 22, 2018 5:31 PM
  • Oh man. I'm another "Me Too" as these updates are crazy slow. It's been 45 minutes and "Getting Windows Ready. Don't Turn Off Computer" is still displaying. Trying to spin up a new machine to replace a failing DNS server and this is not helpful.

    Please reduce the update packages Microsoft. This makes it nearly impossible to get things online quickly. I have no idea where the server is in the update process or how much longer I'll have to wait.

    Licenses are getting more expensive, servers require more resources, and updates are slower. Linux is looking like a better option to this. Please fix it.

    Frustrating!

    Thursday, February 22, 2018 7:34 PM
  • I'm stunned this still isn't resolved going on 9 months now... I installed 6 VMs spanning 3 hosts. The hosts are 2016 Core Server and the VMs are 2016 Standard. These are all SSD storage machines with 64GB RAM. The smallest of windows updates takes FOREVER on all of them.  I just rebooted after installing one of the 02-2018 CU's (KB4077525) on a VM and the "getting windows ready" screen and such is insane. On a machine that normally boots in under a minute, that was an 8 minute reboot, on top of the 30 min update install time.

    If it helps narrow it down, the Server Core machines take just as long (even with VMs offline) and they aren't running any AV solution.

    Something definitely isn't right.

    Previous 2008R2 servers knock through updates like normal without issues.

    Thursday, March 1, 2018 5:24 PM
  • If we're talking about using the Settings > Update & Security menu, instead of WSUS, then yes, W2016 does feel much, much slower to patch. 

    My workaround is to use SCONFIG instead. It may be all in my head, but it does feel like W2016 patch faster that way, and with less errors. 

    Thursday, March 1, 2018 8:44 PM
  • The problem for me is the damn tiworker this tool it sucks so hard always has since win vista, waiting for 4h to install 3 updates after clean install of server 2016 v dec2017 frm msdn and still its on 30% the updates are KB890830 kb405379 and KB4049065 and think its stuck on the first

    the program is porb. scanning every cluster of my drive in low level



    • Edited by acmieremet Wednesday, March 7, 2018 3:25 PM
    Wednesday, March 7, 2018 3:21 PM
  • I'm with everybody, I just install a 2012R2 server from scratch with office on it and made all of the update during the time the ........... Cumulative update hang on my 2016 server I'm so tire of this.

    WHY

    WHY

    WHY

    Why everything is so slow!!!!!

    Now I hate patching tuesday!!!

    Wednesday, March 14, 2018 2:11 PM
  • I'm having the same problem. Patches that normally take 10 minutes on a 2012 R2 server now take 1-2 hours or more on 2016 server. Same Hyper-V hosts, same NetApp storage, etc. Brand new spun up vm's -  have tried removing Defender, no difference. This thread started in July 2017 and is still going in March 2018, with no relief in sight. I really don't want to upgrade to 2016 if this keeps up. Just awful.

    KW

    Thursday, March 15, 2018 4:41 PM
  • We find the same - brand new install of windows 2016 19/mar/2018 - 2 processor Xeon with 144mb and mirrored 10k disc.. and first security tues patch - system sat at about 20% for over an hour... then jumps up to 70% again sits for 30-40 minutes - then reboots and takes another 30-40 minutes "applying updates"

    All this time CPU averages 5-10%, memory use 3% and discs not showing great activity... So Microsoft - what poor code have you written, that takes so long to do so little?

    Wednesday, March 21, 2018 1:09 PM
  • I tried to update my template image today.  It's non-domain joined vanilla install, and grabs the updates from the internet.

    At 9:10 I started checking for updates.

    At 10:17 The system said it needed to reboot, and went to the blue screen that says not to power off.

    At 11:25 the system finally completed the reboot.

    This is a esx VM on brand new Nutanix hardware.  The cluster is extremely under-populated because it's a target for DR emergencies.

    This update process is messed up and needs to be addressed as a top priority.

    Tuesday, March 27, 2018 3:32 PM
  • I also just can't stop being surprised seeing how some features went into the final release of Windows Server 2016. And extermely slow Windows Updates is unfortunately just one of those things. Certain design decisions are indeed unbelievable to be seen in a server OS.

    As many here I also regulary do VM template updates in different environments and it's always been a pain.

    Wednesday, March 28, 2018 8:06 AM
  • I too just waited 45 minutes for one update which is just ridiculous. I was under the impression that Technet was monitored by Microcrap employees, guess not.

    Wednesday, March 28, 2018 1:07 PM
  • Yup, Server 2016 is absolutely horrible with Windows Updates. We patch about 50 Win2016 servers monthly and over half fail every time and need multiple reboots and re-checks to finally get updates installed. And when it does finally work (even on the ones without errors), the update process takes on average about 30-60 minutes depending on the month.  Meanwhile, all of our 2008 and 2012 servers are patched and rebooted in less than 15 minutes with no errors.  Our Windows server maintenance would take us about an hour if all we had were 2012 R2 servers. Instead, it takes 4-6 hours because of Windows 2016.  I can't believe there isn't more outrage about this - aside from what I see from some people within this and a few other threads scattered around the Internet.
    Tuesday, April 3, 2018 10:14 PM
  • Just chiming in to say, "Same here!" It is honestly ridiculous how long updates can take. 
    • Edited by Mako-Wish Friday, April 6, 2018 3:01 PM
    Friday, April 6, 2018 12:00 AM
  • Same here. We ended up disabling updates for win server 2016, it just takes too long and renders the server useless for hours which is exactly what we do not want in a server environment.

    Not to mention the black screen after updates, broken firewall policies and so om. What a joke ! Shame on you MS!

    IT IS 2018 AND MS STILL CANT HAVE A SERVER THAT RUNS 99.99% OF THE TIME.

    Wednesday, April 18, 2018 12:16 PM
  • Lots of complaints, and no solutions. Thank you Microsoft! <bleh>

    And yes, I'm sitting in this myself. Quite frustrating.

    Wednesday, May 9, 2018 5:26 PM
  • Same here. 

    Checked for updates ok, downloaded ok, set it off to shutdown as I need to install 2nd virtual HDD and its installing the updates and has been for almost an hour.

    Edit: As I posted this, it finally shutdown.
    • Edited by tjstechie Thursday, May 10, 2018 11:04 AM
    Thursday, May 10, 2018 11:01 AM
  • Update time is getting worse with every update. Vanilla 2016 server fully up to date until the Patch Tuesday update.  Update failed after spinning for over an hour. Retry running for over an hour and is 33% complete.  Hello MS???????  Guess I will have to open a Premiere Support case for this stupidity.
    Tuesday, May 15, 2018 6:05 PM
  • Same here, updates on 2016 are taking for hours and most times they are failing and you have to retry them several times.

    Sometimes reboots are solving the problem, sometimes not.

    Tuesday, May 15, 2018 7:17 PM
  • Having the same issue, but our server seems to be much much slower than most of the reports here.
    Using a Hyper-V 2016 Core Host, with 64 GB of Ram, 4 Server 2016 VM's are running( does seem slightly faster if I stop all VM's )

    Checked for updates at: 8:30am
    Found 3 Updates:  2018-05 Cumulative Update for Windows Server 2016 for x64-based Systems(KB4103720)
    2018-05 Update for Windows Server 2016 for x64-based Systems (KB4132216)
    Definition Update for WIndows Defeneder Antivirus - KB2267602

    Started Download:  8:35am
    It started Installing: 8:45am
    It is now 2:12 PM and it is still installing!

    I see the Windows Modules Installer Worker using 5-6% CPU and 220 MB of RAM this whole time.

    I have found I have to let this run all night and it still doesn't complete.  I finally just restart the server, and sometimes it does the update, most times I have to start all over again, check and start the install and see the same updates again.

    If it is failing or having trouble it would be nice to know, all the SConfig shows is "Installing Updates...."
    No percentage, no error if it is hung.

    I have two old physical 2008 servers, one SBS 2008, updates and reboot complete in 20-30 minutes max.

    I with everyone else here, updating in Server 2016 is terrible.


    • Edited by SelMoonG Friday, May 18, 2018 8:20 PM
    • Proposed as answer by Themi kotoulas Sunday, May 20, 2018 10:12 AM
    • Unproposed as answer by Themi kotoulas Sunday, May 20, 2018 10:12 AM
    Friday, May 18, 2018 8:18 PM
  • Hello everybody, this is really month by month worst! What is the solution if any????


    Sunday, May 20, 2018 10:13 AM
  • 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:51 PM
  • I have 2 windows 2016 Servers intalled under Vsphere (thank god it's only 2) both take hours over hours to complete updates, what's the deal with this and when will we have a fix MS?

    I'm honestly considering downgrading to 2012, but It's just a lot of work, please provide a fix for this.

    Regards.

    Tuesday, May 22, 2018 11:41 PM
  • Server 2016 has been so bad for updates. Really slow and unpredictable

    The more I'm deploying the worse the monthly update process is getting.

    I'm also cautious to deploy any more 2016.

    Seems like Microsoft has gone backwards with this.

    Your killing the sleep of sysadmins

    Thursday, May 24, 2018 6:53 AM
  • Another "same here" - It now takes us the best part of 4 hours to update 1 host and 4 VMs running Server 2016. Absolutely ridiculous.  


    Tuesday, May 29, 2018 9:27 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:58 PM
  • Hi.  I've had great success with WSUS Offline Updates when Windows Updates behaves mindlessly.  I've yet to try Server 2016 but as it is supported, I don't see why it cannot at least bypass slowness that is network related.  Hope this helps.  http://download.wsusoffline.net/
    Thursday, May 31, 2018 1:34 AM
  • We are all trying to make you understand, that this is a general problem. There is not much else to say about it. Windows server 2016 patching is just EXTREMELY slow in ANY environment compared to previous versions of Windows server.

    It does not matter whether the operating system is installed on brand new out of the box top notch bare metal hardware, or on a VM running in some environment.

    If you install Windows server 2012 R2 on the same hardware/VM, you can do all of your everyday patching in a fraction of the time.

    It is sad - and annoying :-(


    Bugsy - Denmark

    Friday, June 1, 2018 5:56 AM
  • 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:45 PM
  • Also very very very slow in germany with Server 2016 Std. in esxi 6.5 vm with 2 virtual cores. I does not thought a update-process could be slower than MS Exchange 2013 CUs - but the winner in very very slow-performance is the 2016 Server form MS. Thanks zu Microsoft for more tea-time. It seams the problem exists still 2017 so we hope to Server 2020 - that MAY BE better.
    Tuesday, June 12, 2018 12:19 PM
  • I just installed the evaluation version of Microsoft Server 2016 Standard on an SSD drive without using a virtual drive, i.e. it has the whole SSD to itself. Twice I interrupted the update process while it warned me not to stop the computer. The update process recovered. As I am using DUAL BOOT, I can access the same drives from Windows 10.

    I then unzipped an Intel Ethernet driver package for all operating systems while logged in to Windows Server 2016. IT WAS SO SLOW IT EVEN STOPPED AND WAITED OCCASIONALLY. It took maybe 5 minutes to unpack. I rebooted Windows 10 and checked the SSD with Samsung Magician. Status: GOOD. No issues. So I deleted the unzipped folders and unzipped them again using Windows 10 (on the same SSD that Windows Server uses): it took maybe 5 seconds.

    My point: as I am able to compare the same SSD hardware using two different operating systems, I can confirm that under Windows Server 2016 it can be incredibly slow. All Windows Server Updates have been applied and the OS is bare - I have installed nothing but a couple of drivers and only enabled the Wireless LAN feature (as it is only for testing).

    If I have caused this, the only possible explanation is that it is caused by a driver. Internet has masses of Windows ME, XP, Vista, 7, 8 and 10 drivers but Windows Server drivers are rare. Besides Windows Server 2016 does not find them either via Ethernet.

    Tuesday, June 19, 2018 7:31 PM
  • I'd also like to chime in, even though I have another thread open.  Cumulative updates will not install automatically like it should, or even if I go through settings and kick of an update manually.  The only way I get updates to come through is manually downloading and installing or going through sconfig option 6.  And even then it takes over an hour to install the updates.
    Wednesday, June 20, 2018 6:22 PM
  • Mark me down as another member of the "windows 2016 isn't very good" brigade.

    Updates are forever failing on my server. It is a terminal server and there are two updates that i have tried to install manually and automatically via WU and it just fails. not for any reason, it just fails.

    windows server 2016 simply isn't very good and MS need to do something about it.

    Friday, June 22, 2018 10:26 AM
  • Even with brand new (High-end) hardware: HPE DL380 Gen10 : Xeon-Gold 6134/ SSD… . very sad to have to subscribe all the frustrations of the other post here. Microsoft wake up, and fix it!!!
    • Edited by Ivan_KPD Monday, June 25, 2018 1:49 PM
    Monday, June 25, 2018 1:48 PM
  • It's the same here. 

    I can only apply Updates on sundays now in non productive times. 

    Windows Updates Need forever for downloading and installing Updates.

    But even after that, when trying to reboot it takes sometimes several Hours until

    Windows Server getting up again. 

    Stuck at "Getting Windows Ready, don't turn of Computer"

    It is completely independent whether with wsus or without. 

    Also Independent from VM or hardcore Server. 

    As I can see here, this has been an issue for over a year now. 

    I would lose my Job if I did not care About a Topic for a year…

    + This is the 2018-June Update... seems not be solved yet.

    When will Microsoft wake up and solve the Problem?

    Alternatively, you are welcome to join me on Sundays and apply Updates....


    Sunday, July 1, 2018 10:46 AM
  • It's the same here. …

    almost a year later … 1 + 1/2 hours just to restart my small server, with no feedback at all

    Monday, July 2, 2018 9:16 AM
  • 64 replies and the question is only at 20 votes.  Everyone up vote this so it gets some attention.  Server 2016 should be able to patch at LEAST as fast as 2012R2!
    Monday, July 2, 2018 4:48 PM
  • Just another frustrated updater of Server 2016.  Just sits at "Preparing to install updates 1%" for well into an hour.  Installing on an Azure VM at 12:45 AM EST.  I feel like I'm running Vista...but even that was faster.

    Come on Microsoft.

    Tuesday, July 3, 2018 4:46 AM
  • One thing that has helped (a lot) with reliability was to add an exclusion for onaccess AV Scanning for the Software Distribution folder in c:\windows.

    Still its not great but better than it was.

    Wednesday, July 4, 2018 1:50 PM
  • Installing 05-2018 update took over an hour on a high performance ESX hosted VM, until the first step in windows finished. The following reboot then took so incredibly long (again over an hour), showing CPU but no  disk activity that I finnaly reset the VM. As expected, the update failed but at least the system was in production again.

    The Server 2016 Windows update mechanism is pure crap. Thanks MS that update / maintenance windows became a long time of beeing unproductive, watching my servers doing something called Windows Update that MS development is not fixing or improving.


    • Edited by L_Herzog Thursday, July 5, 2018 10:53 AM
    Thursday, July 5, 2018 10:49 AM
  • I would like to add what is hopefully some relief for others out there. I agree the cumulative patches for Server 2016 are painful and our Server 2012 R2 machines will install a dozen updates before 2016 will install one. I have found something that appears to have helped a bit.

    We run a separate solution for Malware and AV protection, so I removed Windows Defender Features and the 'preparing to install updates' stage does not seem to take quite as long now.

    I realize this may not be a option for everybody but at least it's something while we wait for MS to acknowledge there is an issue and fix it.

    Best of luck!

    JT

    Friday, July 13, 2018 2:30 PM
  • Another compain here Just patched the 2016 file server took 90 minutes to install. and another 15 to reboot. I almost quit my job for such a long down time. It's crazy missed my reboot window by an hour because of this! 
    Saturday, July 14, 2018 12:00 AM
  • same here,  just installed the KB4345418 for 2016 and still not ready after 1 1/2 hours still not ready ( 2 CPU Machine )

    Windows 2012 server took 5 minutes to install ???

    should we in future have maintenance windows of at least 4 hours ?

    Short update on this, this morning I updated a identical server with windows defender disabeld and update time was as following

    20 minutes installing before reboot

    22 minutes reboot until logon screen

    18 minutes cleanup processing ( TIworker, disk cleanup )

    This was almost 40 minutes shorter in time as first server, was willing to upload a picture but am not allowed ( account validation )

    But why is tiworker process running as normal like all other processes ? a lot of problems would be solved if this would run with priority below normal as it would not compete for cpu with higher priority, yes it would take longer but who cares ?







    • Edited by Andre NL Wednesday, July 18, 2018 8:50 AM
    Tuesday, July 17, 2018 1:35 PM
  • This solution may not apply to your case but I also had a case of very slow (0% download for extended lengths of time if not always) updates on Windows 2016.

    Our environment is behind a proxy, and doing updates via Windows Update for versions prior to 2016 works just fine. We are used to having our servers having a proxy defined in Internet Explorer and no proxy defined in Netsh/Proxycfg.

    After long hours of troubleshooting on a 2016 server I tried importing Internet Explorer settings into Netsh (Command line: netsh winhttp import proxy ie) and downloads finally started working and the update process completed without a problem.

    So in our case it boils down to a Windows Update Agent change regarding proxy usage starting from 2016.

    Wednesday, July 18, 2018 9:26 AM
  • Another frustrated Administrator.

    I'm building some new Hyper-V Machines.  dual prox, 12 core, 256GB of memory on a hardware stripe with all flash drives, and connected via dual 10GB network cards.  Maybe not the beefiest of hardware out there, but it should be able to tear through a windows update quickly.

    I kicked off windows updates and ~45 minutes later, windows update went from preparing to download to you have no updates available.  I restarted and it clearly applied Windows updates and checked again when it came back up -- more updates available.  Instead of being hung up at preparing to download, it's now hanging at preparing to install... I've got no idea how much longer this is going to take, but I'm clearly not going to be able to finish up this task today!

    I've been patching a lot of machines laterly and I've noticed that a Cumulative Update is downloaded and installed for 2018-05 (KB4103720), and after thats done, it downloads one for July.  Shouldn't it just need one cumulative update and then be done?


    Tuesday, July 31, 2018 8:06 PM
  • So this is great that we can post a what's the deal with here in the Microsoft TechNet forum, but how about a real answer from someone from Microsoft and then a solution. Saying there are 'many’ factors or are you using WSUS is neither a reason or a solution. As an MSP engineer I manage updates on many servers across multiple customers with mixed MS Server versions and 2016 is the worst at every location for updates. Every 2016 takes 2-3 times longer to download, install and then reboot than any other version of MS server back to 2008. So how about stop with the blow off question and answers like we are home users and actually fix it!
    Thursday, August 9, 2018 2:42 AM
  • I really wish i didnt buy this server or at least had the option of having it come with 2012 r2 instead of 2016. A yearago when i bought this, i was scratching my head because it was slow and with age it got even slower. Keep in mind we are using this as a basic file server, no vm, nothing else.

    Updates take forever, and now apps on the desktop also take forever to launch. We use backupassist and it can take up to 30 minutes just to launch the admin console.

    Meanwhile, the 6 yold server we retired is running circles around our very expensive 2016 server.

    FIX THIS PLEASE!!!!!!

    Thursday, August 16, 2018 10:09 PM
  • Sign me up as someone who's experiencing this as well.  Utterly ridiculous

    The workaround is that I have to install it during the day and schedule it to reboot at 1AM and HOPE it's back up and running by 4AM

    Friday, August 17, 2018 10:36 AM
  • Agreed, Windows Update on Server 2016 is very slow, compared to 2012 R2. :(
    Friday, August 17, 2018 6:00 PM
  • One thing that has helped (a lot) with reliability was to add an exclusion for onaccess AV Scanning for the Software Distribution folder in c:\windows.

    Still its not great but better than it was.

    It's unclear if you're talking about Defender here, but it looks like most if not all of that folder is automatically excluded via the default set of exclusions.
    Sunday, August 19, 2018 11:21 PM
  • 8/29/18 - Same problem here.  Server 2016 guest in a Hyper-V environment.  It's been over an hour since I told it to shut down and update.  This is on a Dell <g class="gr_ gr_209 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="209" id="209">Poweredge</g> with Solid State drives too.
    Wednesday, August 29, 2018 8:37 PM
  • No I was talking about Sophos Anti Virus, sorry should have been a bit clearer.
    Wednesday, August 29, 2018 9:22 PM
  • two hours and waiting still with no status indicators.  Brand new fast server and no this is not a WU vs. WSUS issue.  It is a partching rollup strategy by MS which is defective and worrying for any admin that hass to sit there and watch for hours wondering if their server will come back up.  
    Friday, August 31, 2018 6:12 PM
  • please, you know there is a 2016 problem with rollups.  they take hours.  Ever use a 2016 server in the real world?
    Friday, August 31, 2018 6:13 PM
  • Thanks.  MS has been very good at listening to their admins in the past so I have lots of hope.  Particularity when you decide to change the UI with each release so we have to relearn how to get to everything when it used to be a breeze (Win7).  Every admin I know has asked for this.  Thanks for listening to your customers! 
    Friday, August 31, 2018 6:16 PM
  • BINGO man.  This is a design problem and it needs to be changed.  On hour 3 on a Brand new Dell Server with 2018-08 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4343884). 

    That's right - hour three on a 1.3GB update package.  It's been on "100% complete working on features" for another 30min.  I don't even have any roles or features installed yet.  

    BROKEN

    Friday, August 31, 2018 6:22 PM
  • Hi,

    Have you tried to disable the Defender Real-Time Protection, for a test (Or other AV RTP)?


    /SaiTech


    Have you tried running a windows 2016 server in the real world and actually patching it?  It happens EVERY TIME.
    Friday, August 31, 2018 6:25 PM
  • Okay, so i just finished updating a 2008 R2 terminal server (with Office 2016) with 26 updates, in under 20 minutes (including download of the updates).
    Lets compare to a Server 2016.

    Server 2016 terminal server with Office 2016 (4 haswell CPU cores, all SSD SAN, 16GB RAM)
    Goal is to patch the server with the CU from marts (03).
    Time: 17:45 - Just pressed 'Check for updates'
    Time: 17:48 - Pressed 'Install updates'
    Time: 18:07 - Pressed 'Restart'
    Time: 18:31 - Server is back up, searching for new updates (just to be sure), all good

    Not horrible but still very slow. But the worst part is no usable status whilst Windows Update is installing.

    wondering how you did with 2018-08 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4343884)
    Friday, August 31, 2018 6:29 PM
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang

    It seems to be getting worse.  2018-08 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4343884) is a 3-4 hour update on a brand new fast server with nothing but the OS installed  It's great that the experience ends with a message that it is "working on features 100% complete Do not turn your computer off" for another hour just for kicks.  Did I mention that there are no roles or features even installed yet on this brand new server?  So let me ask you, how is this issue going on your side in publicly recognizing that there is a reproducible problem that everyone is having rather than trying to pretend there is no issue?

    Friday, August 31, 2018 6:38 PM
  • Same here, brand new Server 2016, SSDs, taking forever to even start to install anything. Left it all day and <g class="gr_ gr_140 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation only-ins replaceWithoutSep" data-gr-id="140" id="140">eventually</g> it said they were downloaded, several hours in after pressing install and still on 10%. This is terrible.
    Friday, August 31, 2018 9:34 PM
  • Here we are Sept 1st and we still have the same exact problem with Windows Server 2016 Monthly cumulative updates. I have a new production server I installed last month for a client. The update trashed the server, went into repair mode and could not come out of Safe Mode. I had to revert a a replication for an hour while I fixed the issue and reinstalled the update. The process to me three hours of work for what should have been a simple update. Windows now sits at the update screen for hours while the server shows no progress. What a bunch of Microsoft BS!!! This OS is suppose to be as good or better than 2012 R2 right!? I hate this nonsense from Microsoft, fix this issue MS, Fix it! I would love to turn off updates but the new server 2016 will not let you do that! Does anyone have any ideas for this problem? I did notice this if anyone can help. I logged on to my Exchange server that updated with no issues (same update). I opened “Computer Management” and connected to the win 2016 DC that was stuck on “don’t turn off your computer”. I looked at the services and I could see the Windows Installation Service was “stopping”. That tells me there is a problem with the server being able to stop this service (or others). Normally, I would just open the task manager and end that service. Being on another server, I could not do that. If I had to guess, I’d say the issues is with that service. If anyone knows how to end a service while on another machine that info might help me track down the issue on the next updates freeze.
    • Edited by TCMagic Sunday, September 2, 2018 4:57 AM
    Sunday, September 2, 2018 4:48 AM
  • Getting really bored of seeing this.

    Sunday, September 2, 2018 9:47 PM
  • I could not agree more with all comments here about the slowness. On multiple occasions I have installed Win2016 on a brand-spanking new fast machine, then getting it updated with especially KB4343887 followed by KB4343884 is unbelievably slow, like installing WinXP RTM and then getting it patched up...

    I have done the same with virtual instances, same issue. It feels like we are back in the year 2001.

    Tuesday, September 4, 2018 12:41 PM
  • Same here - KB4343884 on 3 x brand new Azure VMs and after 10 minutes I'm at 0% on 2 and 1% on the 3rd. Windows Modules Installer Worker and Windows Defender are consuming most of the CPU (around 51% utilized).
    Saturday, September 8, 2018 6:07 AM
  • It's a ploy to get on 2019 (soon). Think how small those updates will be, for a while, at least.
    Monday, September 10, 2018 1:06 AM
  • Similar situation here. Production service interruptions related to patching are now measured in hours instead of minutes. Given that service disruptions related to maintenance have changed so significantly and no resolution seems to be forthcoming, our customers are now actively weighing these hours-long service interruptions against the cost of higher availability solutions or moving away from Windows as the server operating system of choice.
    Thursday, September 13, 2018 1:10 PM
  • The first message in this thread was dated July 17th, 2017.   After reading the whole thread several times to make sure I am not missing anything, I've come to an inescapable conclusion.   MS simply doesn't care.

    I too have extremely slow updates on Windows Server 2016.   No issues of note in the message logs, just plain slow.  Eight processors, sixteen cores and during the update process, usually only one of the cores at a time shows any sort of significant load during the entire update process.   

    This is a level of incompetence and/or indifference on the part of windows update developers for well over a year now that really calls for a complete purge of that team and a hiring of competent individuals.

    I don't really care if this message gets deleted or not.  I'm only one of thousands, perhaps millions of system administrators that are experiencing this problem.   It's inexcusable on every level.

    Get it right or move out of the way and let someone who can do it.   Microsoft is a juggernaut, but nothing is forever, and the longer you don't care, the more you endanger your own livelihood through your own incompetence.

    Friday, September 21, 2018 1:47 PM
  • This is now really just silly. More than a year of slow updating. We have production servers 2016, 2012 r2, 2008 r2 and just 2016 has problems with updates. It takes 1-2 hours per server to update monthly update. It stops at preparing updates, then few times on some random percentage, and then it takes forever shutting down. After reboot if you are unlucky, you have to wait long on black screen.

    It does work though, if you wait long enough. And it is fast with some others smaller updates though, like defender. But every other server version we use is way faster, few minutes, up to 10 minutes for the whole process with reboot. 

    We have all kind of setups of 2016, all from HyperV hosts to many types of virtual servers. With antiviruses, without, production, testing... every single 2016 server is slow on updating. It is painful for admin to keep these up to date.

    I would really like some explanation for why is this happening.

    Friday, September 21, 2018 9:20 PM
  • I have a bunch of Server 2016 but only the servers running web services are slow to patch and reboot (last patch cycle it took nearly 2 hours to install and reboot them to a working state).  The license, SQL, and DHCP servers don't take more than 15-20 minutes to patch completely (still much slower than my 2012 R2 domain controllers).  The next round of patches, I'm going to try setting all the web related services to disabled, reboot, try installing the updates and see what happens.  Just seems like there is contention with something running because I'll watch perfmon and not see hardly any activity on cpu, disk, memory, or network while Windows Update is stuck at 30-40% for 45 minutes.
    Tuesday, September 25, 2018 8:05 PM
  • Same problem here, every 2016 server. The original post was over a year ago and we're still struggling with this issue? Microsoft has apparently gone radio silent as well, definitely thinking going to 2016 was a big mistake.
    Thursday, October 4, 2018 9:22 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?






    • Edited by J. Juergen Friday, October 19, 2018 11:34 AM
    Wednesday, October 10, 2018 12:42 PM
  • The next round of patches, I'm going to try setting all the web related services to disabled, reboot, try installing the updates and see what happens.  Just seems like there is contention with something running because I'll watch perfmon and not see hardly any activity on cpu, disk, memory, or network while Windows Update is stuck at 30-40% for 45 minutes.
    Well, that didn't do a bit of good.  I've been waiting at "Getting Windows ready Don't turn off your computer" for over an hour now. Also one of my DHCP servers has been installing updates for over an hour too. This is ridiculous.

    • Edited by Hemi345 Thursday, October 11, 2018 3:09 AM
    Thursday, October 11, 2018 3:07 AM
  • So after an hour and twenty minutes for this one web server to patch, Windows update reports there were some problems (ss below). Attempt two took right at an hour and was finally successful. What I find strange is that while watching the DHCP server patch... err, sit at 30% for about an hour... just as I see the web server reboot, the DHCP server suddenly jumps to 100% and prompts to restart.  What the hell is going on here??

    Thursday, October 11, 2018 3:28 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 klicking 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?





    This might not be the entire solution, I know - but have you tried to reboot your host before doing a Update run? This sometimes helps me, when Im all in tears ;-(
    Thursday, October 18, 2018 11:49 AM
  • I've actually instituted a block on all 2016 deployments as a result of this. The service downtime is simply unacceptable. Thank god there's still Linux.
    Thursday, October 18, 2018 2:11 PM
  • I've also decided to block any future installations of Server 2016 due to these issues.  I've now begun testing Windows Server 2019 and (so far) it does not appear to have the same slow update issues.
    Thursday, October 18, 2018 2:45 PM
  • No kidding... more than a year later, and still experiencing the same problem.  SLOW!!  Updating 2016 Standard with 1 update, and have been to the cleaners, the mailbox, and the bank... Really?  REALLY?!
    Saturday, October 20, 2018 4:34 PM
  • Just to add my two cents worth.

    Running a Windows 2016 server on a VM box with 6 vCPUs and 24GB RAM.  Installed KB4462917 and rebooted the server which took 10-15 minutes.  Right after the server came up I started installing 2018-10 Cumulative Update for Windows Server 2016 (KB4462928). 

    After it finished downloading and unpacking and 'installing' the 1.3GB(!) update, which took almost an hour, it has now been an hour on the "Getting Windows ready. Don't turn off your computer" screen and it is still not done.

    I have other 2016 servers in production on the VMware box (Exchange, DC) and I am really worried about installing this latest piece of Microsoft update crap as I have no idea how long these servers will be off-line.

    We have Linux servers as well, and their updates take a fraction of the time, so thankfully our file servers and DCHP server have virtually no downtime. 

    Microsoft, seriously, you have a problem here and it doesn't look like it is being addressed, much less fixed.


    Update:  It took 1 hour 54 minutes from starting to download the update to getting the login screen once update installed.
    Tuesday, October 23, 2018 7:43 PM
  • This might not be the entire solution, I know - but have you tried to reboot your host before doing a Update run? This sometimes helps me, when Im all in tears ;-(

    Yes, I tried that on one of mine... even stopped and disabled auto start of web services, rebooted, started download and install of patches and it still took over an hour and a half. 
    Friday, October 26, 2018 4:46 PM
  • I'm just trying to "patch" my Server 2016 Template on VMWare on a solid state SAN (over 100,000 IOP's random) and it's taken over 45 minutes to get to 22% "Preparing to install updates." For an enterprise environment, I expect an enterprise level OS to keep up considering the costs involved.  Just another frustrated sysadmin, grrrrrrrr.
    Tuesday, October 30, 2018 11:35 PM
  • Hmmm, will this help?  It does roughly coincide with the top post (mid-2017).

    Express updates for Windows Server 2016 re-enabled for November 2018 update

    "Starting with the November 13, 2018 Update Tuesday, Windows will again publish Express updates for Windows Server 2016. Express updates for Windows Server 2016 stopped in mid-2017 after a significant issue was found that kept the updates from installing correctly. While the issue was fixed in November 2017, the update team took a conservative approach to publishing the Express packages to ensure most customers would have the November 14, 2017 update (KB 4048953) installed on their server environments and not be impacted by the issue.

    "System administrators for WSUS and System Center Configuration Manager (SCCM) need to be aware that in November 2018 they will once again see two packages for the Windows Server 2016 update: a Full update and an Express update. System Administrators who want to use Express for their server environments need to confirm that the device has taken a full update since November 14, 2017 (KB 4048953) to ensure the Express update installs correctly. Any device which has not been updated since the November 14, 2017 (KB 4048953) will see repeated failures that consume bandwidth and CPU resources in an infinite loop if the Express update is attempted. Remediation for that state would be for the system administrator to stop pushing the Express update and push a recent Full update to stop the failure loop.

    "With the November 13, 2018 Express update customers will see an immediate reduction of package size between their Management system and the Windows Server 2016 end points."

    Tuesday, November 13, 2018 5:21 AM
  • Hmmm, will this help?  It does roughly coincide with the top post (mid-2017).

    Express updates for Windows Server 2016 re-enabled for November 2018 update

    "Starting with the November 13, 2018 Update Tuesday, Windows will again publish Express updates for Windows Server 2016. Express updates for Windows Server 2016 stopped in mid-2017 after a significant issue was found that kept the updates from installing correctly. While the issue was fixed in November 2017, the update team took a conservative approach to publishing the Express packages to ensure most customers would have the November 14, 2017 update (KB 4048953) installed on their server environments and not be impacted by the issue.

    "System administrators for WSUS and System Center Configuration Manager (SCCM) need to be aware that in November 2018 they will once again see two packages for the Windows Server 2016 update: a Full update and an Express update. System Administrators who want to use Express for their server environments need to confirm that the device has taken a full update since November 14, 2017 (KB 4048953) to ensure the Express update installs correctly. Any device which has not been updated since the November 14, 2017 (KB 4048953) will see repeated failures that consume bandwidth and CPU resources in an infinite loop if the Express update is attempted. Remediation for that state would be for the system administrator to stop pushing the Express update and push a recent Full update to stop the failure loop.

    "With the November 13, 2018 Express update customers will see an immediate reduction of package size between their Management system and the Windows Server 2016 end points."

    So are "Delta" updates what they are referring to as the "Express" and "Cumulative" updates as "Full" in the Microsoft Update Catalog??

    Sounds like if we have successfully installed KB4048953, we can begin installing the Deltas ?

    • Proposed as answer by ams_tschoening Friday, February 22, 2019 6:36 PM
    • Unproposed as answer by ams_tschoening Friday, February 22, 2019 6:36 PM
    Wednesday, November 14, 2018 7:38 PM
  • It doesn't look like the November 2018 patches are any different. I have a fresh Server 2016 VM with absolutely no services. Ran the November 13, 2018 cumulative and took over an hour to install and reboot. I then ran Windows Update again and a new patch came out just today (November 27, 2018). It took over an hour to get to the "restart" prompt and now I'm just sitting at the lovely "Getting Windows ready..." screen.

    Seriously Microsoft, this is a joke, fix the broken update system.

    Tuesday, November 27, 2018 11:16 PM
  • HEY MICROSOFT!

    WHAT THE HELL IS WRONG WITH YOU?

    Here it is over a year later and this abortion you've foisted off on us is still not fixed! Not only did you add an annoying nag screen that can't be bypassed telling me I have some updates; you've booted the upgrade process back to the stone age! Thanks so much!

    Helpful robot Eve Wang last posted here over a year ago and that's the last comment from MS on  the subject...

    You guys really suck donkeys,

    ianc

    • Edited by ianc3 Tuesday, December 4, 2018 10:19 PM
    Tuesday, December 4, 2018 10:15 PM
  • I've had 1 WS 2016 server today just DOWNLOADING the update for 4 hours.


    And when I decided to reboot the server to manually apply the update, the garbage took 30 minutes to reboot due to the lovely "Preparing to install updates". IT DIDN'T EVEN DOWNLOAD THE UPDATE!!!!!

    And now all I just have to do is to install the 1.45GB update. Nearing the 5th hour mark.
    Of the 5 WS 2016 servers I've had the pleasure to update, 3 of them needed 2 update cycles of 2 hours each, as they failed to install the first time.

    Ohh boi, the times I've fantasized of the turning the VM off and pressing "Delete from disk".

    My disappointment is immeasurable and my day is ruined.
    Friday, December 7, 2018 8:59 PM
  • And sconfig is broken:

    Confirmed on multiple different WS 2016 servers.

    Maybe it's the 3 Xbox services that are causing this?
    Or the "Windows Mobile Hotspot Service" service?
    Or CDPUserSvc service?
    Or the countless other "Windows 10" remains?!

    Friday, December 7, 2018 9:20 PM
  • You know what's not normal? Server 2016 updates... they take an abnormally long amount of time to complete.

    I just created two VMs, installed server 2016 and ran updates. Nothing else. My hardware is FAST. Updates took..... 5 HOURS.... and one of the servers rebooted on its own even though I didn't tell it to and had no auto reboot settings.

    WOW MICROSOFT!!! We know you suck at some things, but maybe put some more resources into the important ones like Windows updates and server backup. What the honest hell is wrong with you? You need me to come in and straighten up some of the people in your departments? They clearly need a kick in the ass or to be replaced, this is UNACCEPTABLE.

    Check my logs? No... this is a fresh install, check YOUR logs, as in the ones that you can use to debug your crap software.
    Saturday, December 8, 2018 5:47 PM
  • You can turn off updates :

    Apply a GPO that will Disable Windows Update service & Windows Module installer service. (A GPO will protect your setup from anyone at Microsoft who could decided that both services must re-enabled at startup.)

    Disabling Windows Module installer only and letting Windows update downloading the update seems viable. Updates are downloaded but YOU decide when it's time to install them. Of course that does not solve other WU shortcomings such as slow updating. At least you're not taken by surprise.




    • Edited by lolix2 Thursday, December 13, 2018 9:04 AM
    Thursday, December 13, 2018 8:21 AM
  • Has anyone found any official statements from Microsoft on the slow update issue?
    Friday, December 14, 2018 4:03 PM
  • Did Someone have try windows update on 2019 server and how ir take to run in over-all. I'm so tired on my 2016 server...... 
    Friday, December 14, 2018 4:28 PM
  • Did Someone have try windows update on 2019 server and how ir take to run in over-all. I'm so tired on my 2016 server...... 

    So far I haven't had any issues with updates on 2019.  I've completely given up on 2016 and have upgraded my servers to 2019.  No more update problems.
    Saturday, December 15, 2018 2:33 AM
  • We've install windows Server 2019 DataCenter with GUI on 6 Cluster Nodes.

    So far updates are not bad , Unless you skip a month of cumulative updates. The process might take longer.

    Our Domain Controllers with Windows Server 2016, took over 3 hours to apply updates and reboot on server.

    The first hour and 30 minutes to find out updates had failed.  As everyone else stated 2008 and 2012R2 no problems occurred

    Saturday, December 15, 2018 3:25 AM
  • Thanks for the info.
    Monday, December 17, 2018 3:56 PM
  • I installed a new 2016 Std Srv VM today and had immediate problems with windows update. I'm using an original Lenovo 2016 Server ROK - maybe this is an issue? Anyone using a ROK? The Version of windows straight after installation is 10.0.14393 that is Windows 10 1607.

    The server first wanted to install Cumulative Update 05-2018 for Server 2016. It stalled somewhere at Downloading updates - actually there was no network traffic, no disk I/O.Only TiWorker.exe going wild.

    I manually downloaded Servicing stack update for Windows Server 2016 and Windows 10, version 1607: November 13, 2018 (KB4465659) and 2018-12 Kumulatives Update für Windows Server 2016 für x64-basierte Systeme (KB4483229). Uninstalled Defender: Uninstall-WindowsFeature -Name Windows-Defender, reboot, Stopped Windows Update and Windows Installer, deleted contents of c:\windows\softwaredistribution, started Windows  Update.

    Installed the previously downloaded KB4465659 manually

    reboot

    then the previously downloaded KB4483229 manually

    It worked without further errors and later updates were also successful. AND QUICK.



    • Edited by L_Herzog Friday, December 21, 2018 12:07 AM
    Friday, December 21, 2018 12:03 AM
  • No... Microsoft's official statement is called Server 2019. It is clear Microsoft has fallen off the bus with updates.
    Saturday, January 5, 2019 10:52 AM
  • FWIW, I can confirm that 2019 updates fine even in VMs.

    Rob Holmes

    Sunday, January 13, 2019 1:11 AM
  • Has anyone found anything new on this?  This has been happening for a LONG time and I have had 2016 servers in the environment for about a year now.  Updates for these servers have taken way too long since throwing them in my environment.  Does anyone have any suggestions? I can't be coming in on a Monday morning with critical servers down because they are still installing updates or failing because the server aborted it after a certain time frame.
    Monday, January 14, 2019 1:42 PM
  • Has anyone found anything new on this?  This has been happening for a LONG time and I have had 2016 servers in the environment for about a year now.  Updates for these servers have taken way too long since throwing them in my environment.  Does anyone have any suggestions? I can't be coming in on a Monday morning with critical servers down because they are still installing updates or failing because the server aborted it after a certain time frame.

    I just received a dell R440 with 32 GB and xeon processor, the first thing I did was install the updates from windows and I've been here for over 2 hours waiting for a suspect download ... PS: CPU, RAM and network with no strange activity


    • Edited by gustavoxp Tuesday, January 15, 2019 2:34 PM
    Tuesday, January 15, 2019 2:33 PM
  • This is still happening...There is no reason that this should take this long. When a system downloads the update installs and reboots it should never take a corporate system 2 hours to finish an install, from the restart prompt this is just plain bad.  I have employees who are online at all times of day and to tell anyone that the systems have to be updated is starting to cause C-series executives to cringe and to not want systems updates because of the impact to the business operating functions.

    Get this crap fixed! 

    Monday, January 21, 2019 8:14 AM
  • It's been like this for two years now. I can think of two reasons why they don't fix it and never will.

    1. Microsoft just isn't capable of fixing this. Software installation and updates installation have always been fundamentally broken in Windows. If you compare it to more sophisticated and robust tools like APT you know what I'm talking about.

    2. Microsoft wants to boost Server 2019 sales by not supporting Server 2016 properly.

    Server 2016 and Windows 10 are the worst OSes ever.

    • Proposed as answer by red cow Wednesday, January 23, 2019 3:21 AM
    • Unproposed as answer by red cow Wednesday, January 23, 2019 3:21 AM
    Monday, January 21, 2019 10:27 AM
  • Boot Window 2016 safe mode and patch .. Bypass all dumb dumb slowness. Try it, its FREE !

    **Hope Windows server 2019 patch is better ...

    Wednesday, January 23, 2019 3:24 AM
  • We build Hyper-V hosts, and VM's to deploy to customers.

    Since Server 2016 my deployment time, for a new host, has gone from hours to days. Those days are spend waiting for the endless updates, which cripple to newly deployed Host and VMs, often for hours, while I'm trying to configure the damn things.

    Oh to have server 2012R2 back. At least that could be rolled out live in less that a week!

     
    Thursday, January 24, 2019 12:35 PM
  • Boot Window 2016 safe mode and patch .. Bypass all dumb dumb slowness. Try it, its FREE !

    **Hope Windows server 2019 patch is better ...

    In the time it has taken to install the January cumulative patch to Windows 2016, I have managed to:

    - download the 2019 evaluation ISO (on a 100Mb connection)

    - install it in VirtualBox

    - install all updates (including the cumulative update)

    - reboot to desktop

    5 mins later, Windows 2016 finally finished whatever it was doing and rebooted.

    Saturday, January 26, 2019 5:24 PM
  • I´m still having the same issues, but now it´s getting even worse … After waiting for Hours for shi* win 2016 Server to finish his work, the update fail :)

    Now additionally for waiting all this Long time I will have to troubleshoot Windows Update and telling it "I love you so much" so it get`s up again and installs the cumulative January Update.. 

    Thank you Microsoft for no improvement at all. :)

    Saturday, January 26, 2019 5:42 PM
  • So after two days of Windows server 2016 standard updates, I finally search the net for this slowness issue. I thought there was something wrong with my deployment but after reading two years of posts on this form, I have decided not to deploy 2016 servers at all.

    Some have said that 2019 fix this issue, but I don't have the money to purchase a new OS. I have 2012R2 and was "gifted" or better yet "cursed" 2016 with software assurance. That ran out before 2019 came out so I'm stuck with 2016 until they fix updates.


    Rick Turske

    Thursday, January 31, 2019 1:01 PM
  • And another one here.

    Brand New HP Gen 10 server, 16cpu cores, 64GB of RAM, SSD Storage throughout. sitting in a datacentre with multiple gigabit internet connections

    Server 2016 takes so long to download and install updates through its update process its actually quicker for me to get the KB numbers and manually download them from the Microsoft catalog. KB4465659 was an 11MB download. Windows update itself sat at preparing to download for this update for 3 hours. but even with the manual download , the install, for 11MB worth of patch took over an hour.

    Tuesday, February 12, 2019 9:42 PM
  • I agree with you.

    Windows Server 2016 in much slower in update process then Windows Server 2012R2.

    And troubleshooting proccess (logs reading) is much complicated compare to Windows Server 2012R2 with it's c:\Windows\WindowsUpdate.log file.

    MS should fix it.

    Thursday, February 21, 2019 4:45 AM
  • I can totally agree with you guys. It's a nightmare with updates on 2016 - plain and simple and a fact. Don't let MS support fool you otherwise. It needs to be fixed. With have thousands of Windows Servers for many different customers and everywhere we have 2016 we are seeing issues across the board (and they're getting more). W2K16's update process is unreliable as hell. It's 50/50 chance it either doesn't download, gets stuck on download, takes hours to apply the patch (perfect to plan a maintenance window with the customer) or spends hours on the "Working on updates screen" during shutdown or bootup with seemingly no progress from the outside. All during while W2K8, W2K8R2, W2K12 and W2K12R2 apply updates without issues at the same time.
    • Edited by Siniman Tuesday, February 26, 2019 8:44 PM
    Tuesday, February 26, 2019 7:54 PM
  • I've started using the delta update in MUC instead of the normal CU in WU for the main update, and while I haven't timed it, it's not as slow. Part of this may just be a result of the size (much smaller).
    Tuesday, February 26, 2019 8:28 PM
  • Microsoft get your rear in gear ... this server 2016 is the worst windows updates framework ever !!!!

    Either fix it or give us back our license money instead of giving us broken and not fit for purpose products.

    We only have a limited patching window of 5 hours ... not 5 days.

    Wednesday, March 13, 2019 1:55 PM
  • The question was asked: When will Microsoft fix the issue?

    Answer: When we stop buying their software until they do better. You want to hit a company where it hurts, then that has to be the bottom line. 

    Truth is MS has very little resources invested in the server team at this point. Most of their investment is in the cloud platform (Azure and O365) at this point. I don't expect them to ever really "fix" it. They just don't care. On-prem IT assets don't make them any money anymore. 

    That said I can update Ubuntu or CentOS server in minutes with APT/RPM. And it doesn't even require a reboot 98% of the time. MS's update model is just plain awful. And it's gotten worse in 2016. It used to be I could check for updates without installing them. Can't do that in the GUI now. Check for updates and you're getting them! Additionally, I used to be able to pick and choose which updates I wanted. Nope - that's gone now too. You're getting whatever they want to force down your throat. 

    The entire direction MS is going in has us looking really hard at any place we can get them gone! Example: we run some PHP web servers on IIS. Yea those are going to be CentOS and Apache servers next go around for sure. Things like that. Their OS really just does just suck at life these days. 

    Oh and don't use DFS to replicate office files unless you like loosing data. That bug has existed since Server 2003 R2 and they've reintroduced it in every server OS iteration since! 




    • Edited by ZackInMass Wednesday, March 13, 2019 6:10 PM
    Wednesday, March 13, 2019 6:04 PM
  • same for me here. 30 minutes to reboot windows 2016.

    Windows 2019 is very quick

    Monday, March 18, 2019 9:34 AM