There should full powershell integration for both WSUS and Server Side WU Client. This would enable scenarios such as post reboot checks for additional patches and mass patching automation.
It would also allow for things like managing small server deployments that don't have WSUS by being able to use remote powershell to query the patches currently installed on servers, check for available patches and then tell them to remediate and reboot if required.
Currently these can be done mostly through WMI and customer powershell scripts that wrap around these, but it really needs proper integration.
Having powershell to query required updates for a server/s and then use that information to approve just those updates in WSUS would be a huge plus as well.

In general, if it could have the functionality of the PSWindowsUpdate module natively (https://www.powershellgallery.com/packages/PSWindowsUpdate/1.5.1.11) and extended powershell in WSUS role, it would be a huge step forward.

Does anyone else out there feel the same as I do about Microsoft and their completely broken update system.

I am at my wits end with these huge cumulative updates that just fail 90% of the time on every Server and Windows 10 PC. I have to spend so much time manually installing these updates and it is got to the point where I am beginning to really hate Microsoft! I used to be a loyal fan of their tech but my patience is now at an all time low.

Sort it Microsoft, tell your update team that they have really dropped the ball! I cannot believe you have done nothing about sorting this issue as its been like this for a year already!

Servers are being left vulnerable due to constant failing of updates.

it is simply disgraceful!

After installing update KB3213986 on Server 2016 Desktop Experience, a failed logon is logged every time the BITS service is started.

Failed Logon Event:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 2/27/2017 1:27:10 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: PLB-DXX-TP01.dev-products.local
Description:
An account failed to log on.

Subject:

Security ID:        SYSTEM

Account Name:       PLB-DXX-TP01$

Account Domain:     DEV-PRODUCTS

Logon ID:       0x3E7

Logon Type: 5

Account For Which Logon Failed:

Security ID:        NULL SID

Account Name:       -

Account Domain:     -

Failure Information:

Failure Reason:     An Error occured during Logon.

Status:         0xC0000073

Sub Status:     0xC0000073

Process Information:

Caller Process ID:  0x49c

Caller Process Name:    C:\Windows\System32\svchost.exe

Network Information:

Workstation Name:   -

Source Network Address: -

Source Port:        -

Detailed Authentication Information:

Logon Process:      Advapi  

Authentication Package: Negotiate

Transited Services: -

Package Name (NTLM only):   -

Key Length:     0

Removing the update resolves the issue. I've tested this on multiple fresh installs of Windows Server 2016 from media.

The failed logon is problematic because it triggers false-positives in our monitoring solutions.

The issue is easily reproducible.

The monthly Windows Update rollup releases greatly sped up creating a machine from scratch, upgrading an image to latest, and just patching machines. These rollups ceased shipping in December 2014. There has been no rollup release in over 14 months for the current latest production server OS from Microsoft.

This translates to over a hundred updates (about 150 past the last rollup) and a few reboots, multiple ngen passes for .Net that aren't needed. Only the last of these time-costly operations needs to run, a handy side-effect the rollup has.

Instead on thousands of tens of thousands of sysadmins spending a great deal more time patching or additional time slipstreaming image deploys, it would be a much better use of time if Microsoft resumed shipping these very useful rollups.

These updates should also be listed in a single place, not the blogs people relied on before. Microsoft should house the source of truth here.

Related: can we add a category to this UserVoice for patching/updated or similar?