It’s usually better to wait when Microsoft releases its monthly updates to avoid potential problems. That’s true for March. But companies using Microsoft Exchange should make sure they’re not affected by recent attacks.
While most enterprises skip releases and only do them once a year (or longer), I find that my own machines ultimately patch better — and with fewer issues — if I keep to this delayed feature release installation process without completely skipping a release. Installing a feature release also refreshes the Windows updating components, which can fix quite a few update issues. Case in point: I had a misbehaving workstation that threw off a Windows updating error and no amount of sfc/scannow or DISM commands would fix the underlying corruption causing the problem. I had two choices: An in-place upgrade over the top, or — since I was one version behind on the feature release — I could opt to use the Windows 10 software download page to fix the issue. I clicked on “Update now” and had the system upgrade itself to Windows 10 20H2, fixing the problem. I also got a machine that has refreshed Windows updating components ready to tackle future updates. Early on, installing these feature updates would reset printers, affect video, and, in general, make for a stressful time. But Microsoft apparently heard from enterprises that change for change’s sake is not acceptable and made these releases relatively trouble-free. That said, if you still run Windows 10 1909 on hardware with a Conexant audio driver, Microsoft is still unable to provide an automatic fix that lets you to move to either Win 10 2004 or 20H2.
