Originally Posted by ixtab
No, it's not.
Well, it might be. You can determine that by uninstalling JBPatch, seeing if the problem goes away, reinstalling JBPatch, seeing if the problem reappears. If, and only if, all of that is true, then it might be a problem involving JBPatch. But I honestly don't see why it would.
There might be something cached related to either of the packages.
So the above might do.
To be sure, you might want to include a full re-start (20 sec pwr hold) between the uninstalling and the installing steps above.