Erm. The issue is that certain apps (from HP and Kerio) cause verclsid.exe to stop responding. Verclsid.exe basically verified a COM object before allowing it to be instantiated by IE.
The specific trigger in the case of HP is Hpgs2wnd.exe. In the case of Kerio, it flags when IE calls verclid.exe - which causes it to not respond.
My guess in the case of HP is that it makes a remote call from IE - which is what this patch tries to drop - remote code execution through IE. From the logs I looked at, it almost - for practical purposes - DOS's verclsid.exe (Though it is odd verclsid.exe won't work again until you reboot.) In the case of the firewall app, it is probably seeing IE try to execute an unkown file (because it is new to Windows), also causing it to terminate.
The "fix" is, in the case of HP, for their application to be added to the allowed list for executions or kill their service. In the case of Kerio, they will have to update their software (or you manually add verclsid.exe to the exception list.)
There are probably other 3rd party COM objects or calls that could also cause this. I read a few about Quick View Plus.
Then again, they could just not have anything check COM executions and leave the vulnerability