Yes…there are a couple of solutions in the thread itself, but BigFix later added some automatic recovery options for stuck actions, in version 9.5.11. There are now several client settings you can configure to abandon stuck actions, and to kill the child process of the stuck action. See BigFix 9.5 Patch 11 is now available
If you do configure a global action timeout, be sure it’s long enough. This does not fix the root cause, which usually occurs because the admin did not configured “silent” options for an installer, but it does allow for recovery.
When I set the timeout globally, I usually use a really long value - like 24 hours.