Why is my Windows Server 2016 1607 installing, in order:
2018-05 Cumulative Update
(Download, reboot)
2018-06 Cumulative Update
(Download, reboot)
2018-07 Cumulative Update
(Download, reboot)

If the update is cumulative, should not only the last one be requited? This is an incredibly wasteful and annoying time sink.

Currently for arch it looks like someone dissassembles your .deb package and moves things around. It would be a lot easier on us to just be able to make install, or at least for a suggested folder structure to go into the .tar.gz. At very least, the files should be put into a subdirectory as is the norm with all linux installs. I ruined my download folder with the current package

Exchage within a Hyper-V VM with Windows Server 2012 r2: Update KB4057903 leads to an almost unresponsive server. I could reproduce the behaviour twice by deinstalling the update. Please, provide a new version of KB4057903 without the bug. Thanks.

See also the discussion in https://social.technet.microsoft.com/Forums/windowsserver/en-US/387da0db-6046-4838-9db7-c8ddcb6810da/update-kb4057903-fails-in-windows-server-2012-r2-hyperv?forum=winserverhyperv

On the Windows Admin Center Manager WSUS, allow updates, allow machines, create groups ...

WSUS should have an easy way to search for all updates for a specific product

Please fix the broken link when importing updates into WSUS in Server 2016 from the update catalog.

The issue is that the link contains a protocol version 1.20 at the end but the correct version is 1.80!

the "Scheduled install day" and "scheduled install time" group policy settings under "computer/administrative templates/windows components/windows update/configure automatic updates" are being ignored by server 2016 in favor of "active hours." having active hours on servers is utterly ridiculous. I need certain servers to reboot in a certain order only on Saturday nights.

It would be nice to have a way to easily upgrade or migrate from Windows Server 2016 to Windows Server Semi-Annual

Windows update troubleshooter (fully patched server 2016) using the built-in tool always reports 0x80070057 "potential windows update database error detected" If you run the tool available here then no errors are reported. https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter

Can WSUS be updated to use Azure Active Directory Authentication in addition to Windows Integrated? I'd love to be able to offload the WSUS database into the Azure Cloud Database As A Service - SQL Database offering.

As an added bonus, it would also be great if it could also use Azure's new 'Managed Identity Provider' so that, if I have WSUS hosted on an Azure VM, it can just grab needed authorizations through there.

The server works fine without the update. So why do we need it??

Please provide full information what is fixed in cumulative updates. What kind of information is this:

https://support.microsoft.com/en-us/help/4038782
Security updates to Microsoft Graphics Component, Windows kernel-mode drivers, Windows shell, Microsoft Uniscribe, Microsoft Edge, Windows scripting, Device Guard, Windows TPM, Internet Explorer, Microsoft Scripting Engine, Windows Hyper-V, Windows kernel, and the Windows DHCP Server.

We need proper description of fixes for an OS we pay licenses.

Include al necessary symbol files and updates to base OS and current updates. Many environments do not allow server access (and in some instances workstation access) to the internet to update symbol files as needed. I have tried every posted articles suggestions on getting the windows update log into useful, understandable English, with the only success being to reimage my windows 10 Enterprise desktop. I refuse to do so with my domain 2016 servers!

Actually it is not really possible to use automatic acknowledgement rules without acknowledgeing any Preview security or preview feature upates for Windows 7, 8.1 etc.

Please put them a seperate WSUS Category e.g. preview rollups so that an effective testing can be made with rulesets and a test group of computers.

after much troubleshooting this morning, we were forced to uninstall kb4038777 on our 2008 r2 domain controllers and restart them. it appears LDAP authentication is failing over port 389 for a handful of our applications, as well as our production mailarchiva instance.

was curious if anyone else had seen / experienced similar.

I am missing to have more options than just a very common keyword search in Microsoft Update Catalog.

setting up filters like OS version, branch, x86 / x64 and update categories AND date equal / greater than would be amazingly helpful to find a specific group of updates.

Admit it, the current search is not very helpful if you are NOT searching for a specific KB but a set of updates.

E.g. try to enlist all Windows 2003 Server Updates released after January 2017. Good luck, trying.