I see that there are now available "workaround" SSU patches in ZPM, of a "Software Installer" type rather than the more usual "Critical" type. I understand that these apply what is essentially the same update as the regular SSU patch, they just do their detection differently, so that they will appear as applicable even when the SSU is causing most detection to be broken. I have tested deploying one to an affected computer, and it has indeed restored detection to work properly, on the next scan following the first reboot after the deployment.

What is the recommendation for how to handle deploying this type of patch vs. the "normal" one, in an environment where some computers are affected and others are not?

The "workaround" patches recommend to deploy them only to computers which are experiencing the CBS.log update-detection errors. However, in an even slightly large organization, it is not practical to examine computers en masse to determine which ones are and are not exhibiting these log messages - and in cases where a large fraction of computers, out of a total of hundreds or thousands, fall on each side of that line, it's even less practical to restrict deployment of each patch type to only the machines which are or not affected.

How would deployment be expected to behave, on an unaffected computer, if we set our SSU patch policy to deploy both the regular SSU and the latest "workaround" SSU? Would it Just Work (at the cost of added network, server, and system load), or would it have a reasonable potential to misbehave?

My semi-intuitive suspicion is that it would work basically the same way as if the policy deploys only the regular SSU but the patch policy schedule triggers again after the first application of the policy and before the next reboot (something which happens routinely in our environment, since we have the policy schedule triggering up to three times a day), but I don't have a clear enough picture of the situation to be sure about that.

Both should not cause an issue or even simpler just assign the work-around SSU.  It is the same exact patch from MS.  It is just how it is called.

A Co-worker reported an issue with 1809 on Wednesday......

Yea, definitely a problem on the backend.  Workaround 1909 will not download but all others did.

Jim

Presuming you have the Full ZCM, as a temporary fix, you could download the SSU from MS and deploy as a traditional bundle.  The nice thing is it has built-in system requirements, so if it is not needed it will not install.

Looks like the 64bit 1909 is now downloading for me.....