Reading deeper into this story, it probably wasn't a patch to blame

"this was the result of Task Sequence distributed to a custom SCCM Collection. The Collection had been created/modified by an HP Engineer (adding a wildcard) and the engineer had inadvertently altered the Collection so that it was very similar in form and function to the “All Systems” Collection. The Task Sequence contained automation to format the disks"

That explains the no OS found error messages reported, and also the question of how MS OS patches could possibly be installed on the wrong systems.