To improve Windows Server I suggest you ...

Windows Updates shouldn't fail constantly or take hours to complete

I have a number of 2016 servers. It seems like 99% of them fail when doing automatic updates. I am able to install them manually by going through sconfig and selecting option 6 but it takes FOREVER. During installation, the CPU or Memory isn't maxed out at 100% so I have no idea what is causing it to take forever. All other previous versions of Windows run and install updates just fine in the same VMware environment.

237 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Ross shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • Karl W-E. commented  ·   ·  Flag as inappropriate

    Dear Admins, suffering companions, I've tried to bump up at a very kind and helpful person at Microsoft. I cannot promise anything but I hope it does help this issue gets a checkmark before end of main support for Server 2016 LTSC, after more than a year of reporting.

  • Karl W-E. commented  ·   ·  Flag as inappropriate
  • Felix Leven commented  ·   ·  Flag as inappropriate

    Same problem, physical servers, azure vms, hyper-v/vmware VMs, WSUS/Windows update does not make any difference. Fix this!

  • ianc commented  ·   ·  Flag as inappropriate

    Another voice and another vote. When, for the love of God, will you guys get your collective fingers out and fix this?!!!!

    I'm guessing by the new, and extremely annoying, nag screen (which can't be bypassed in 2016), which now appears every time I log on, that you care about customers updating their software. If that's the case, then why have you taken the speedy update process from 2012 R2 and booted it back to the stone age? No information about the size of downloads, erratic and inaccurate progress bars and glacial reboot times that can't fit in maintenance windows. Hello?

    People have been complaining about it for over a year:

    It's now 2018! Wake up! Fix this!


  • Joe Patterson commented  ·   ·  Flag as inappropriate

    I have configured my Server 2016 & Windows 10 GPO settings to not allow my Windows 10 & Server 2016 to received updates from computers on the Internet significantly improves update performance and reliability. Remember Windows 10 & Server 2016 have the new update code path to try and download updates from computers on the Internet. Without the new GPO settings 1709+) the OSes will continue to try to use Internet sources for updates even if the local OS GUI has the option disabled. Confirm with Process Monitor, SYSMON & TCPView tools from Sysinternals on the Microsoft TechNet site.

    *NOTE with CAUTION: You may need to add the newer Windows 10 (1709+) .ADMx/l files to your GPO Central store in SYSVOL (or PolicyDefinitions folder on a local OS) to be able to get access to the additional GPO settings specific to Windows Update and Microsoft's new Cloud based updating settings.

  • Charles commented  ·   ·  Flag as inappropriate

    We have migrate our WSUS from Windows 2008 R2 to Windows 2016 to support the new Windows 2016 Server. All Windows 2008 R2 and Windows 2012 R2 servers that are connected and receives updates from the new WSUS 2016 is vey fast, i mean the installation takes approx. the same time as it was before with the WSUS 2008 R2. But all of our Windows 2016 Servers that are connected and receives updates from the new WSUS 2016 takes many hours to update. The averages of time it takes to update is 2.5 to 3 hours compare to 30-40 minutes for the previous Windows servers versions. This week, we had servers that took 2 days to install the updates...

    Is it normal ?

  • John commented  ·   ·  Flag as inappropriate

    We are moving from Win2012 to 2016 and the experience is terrible with Updates. It takes hours to update and its many times slower when compared with 2008/2012. And even it is unreliable. Sometimes Updates are broken without any info. Upgrading domain controllers to 2016 becomes a nightmare.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We have more and more windows 2016 servers now. the patching before rebooting will need around 2.5 hours...

  • Chris commented  ·   ·  Flag as inappropriate

    A 2016 server, with nothing but exchange on it (a Microsoft product and not some 3rd party, unsupported application) takes 2 hours to update and reboot. How is that acceptable?

  • keith commented  ·   ·  Flag as inappropriate

    A windows server should update as fast as a linux server. We should not have to install a new OS version for you to address this problem

  • stsong commented  ·   ·  Flag as inappropriate

    Still having issue updating CU updates on one Windows 2016 Standard server. Problem started with 2018-05, haven't been able to install any CU updates since. Tried sconfig option, no Bueno.

  • Anonymous commented  ·   ·  Flag as inappropriate

    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?

  • Dan commented  ·   ·  Flag as inappropriate

    Takes nearly 2 hours to update a single 2016 server.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Also multiple experiences of very slow updates with Server 2016 Standard (vm on VMware ESXi 6.0). Resource Manager showed 100% disk usage for a long time

  • binary commented  ·   ·  Flag as inappropriate

    I got some good and bad news... It seems like MS is working on the problem but not for Server 2016

    "making those types of changes to older versions of the OS would be risky (the update stack is absolutely critical). With a new version of the OS we have many months of both internal testing as well as Windows Insider previews that we can use to validate the changes at scale and reduce risk."

  • Pieter commented  ·   ·  Flag as inappropriate

    +1 here.
    Server is saying "restarting...." forever. After forced shutdown and reboot, sometimes hotfix is installed, sometimes it's revert.
    Win2016 is not WSUS client, is VM on Hyper-V 2012R2, firewall is Watchguard.

Feedback and Knowledge Base