We're running ZENworks 2017 Update 4.
On June 15th, 2021, there was released KB5003974. It's a servicing-stack update for Windows 10 version 1909 - the second such SSU released in a single month, which in my experience is highly unusual.
Unlike every other SSU I've ever seen, this one is flagged as "reboot required: no" (and also "supports uninstall: no", which is less relevant).
I did not specifically check on that detail before approving this update for deployment via patch policies. Now, I'm seeing that many computers across the organization are being rebooted automatically in the middle of the day (in alignment with the patch-policy schedule), without prompting the user; this is interrupting work in a significant way.
What I think is happening is that because the patch is not flagged as "reboot required" in ZPM, the remediation engine does not pass in the flags to disable reboot, and so the SSU applicator proceeds with its default behavior, which is to reboot automatically.
Is that analysis likely correct?
Has anyone else been encountering such issues?
Has this incorrect "reboot required: no" flag been fixed?
What can I do to be able to deploy this SSU without causing these reboots?
I suspect that if Lumension has resolved the problem upstream, then I wouldn't necessarily see it right away, but by deleting the SSU from my ZPM instance and running a "check for available patches" I might be able to get the corrected version to show up. However, I'm not positive about what would happen even in that scenario, or even about what would happen if they haven't changed the patch upstream - and much less certain that they even have fixed the issue to begin with.