The September KB4515384 cumulative update to Windows 10 1903 is the latest patch to make headlines for introducing showstopping bugs. It’s updates like this one that have some desktop admins nostalgic for the days before Windows as a service (WaaS) when updates were larger, but less frequent.

The optional quality update was released to fix a CPU spiking issue, but some users who downloaded it reported new problems with Windows desktop search, Wi-Fi, the Start menu, and in-game audio as well as a mysterious orange tint to screenshots and snips.

While most large businesses won’t be affected by the September Windows update because they’re on one of Microsoft’s delayed update cycles or still holding out on Windows 7, this news is a reminder of why having a defined monitoring and management strategy for Windows updates is so important. When an update is applied, it’s the IT department, not Microsoft, who is responsible for the digital employee experience.

With appropriate tools in place, it’s entirely possible to detect and prevent potential Windows 10 update problems before rolling them out to the entire organization. Done correctly, end users should reap the benefits of enhanced security and productivity features while barely perceiving any change at all.

WaaS Isn’t the Enemy

Since I’ll be focusing the rest of this post on how to address problems related to Windows 10 updates, I want to make one thing clear up front: WaaS isn’t the enemy. I repeat—WaaS isn’t the enemy!