This could happen if you are trying to install the patch on a machine where its target MSI installation database is not already installed.
Do you have a test case when this behavior occurs? If you could replicate the behavior into a pattern or a small buildable sample which you can share with us this will be useful.