It's an issue with Internet Explorer. Try using Firefox or Chrome.
We've looked into a fix, it doesn't appear there will be one until the plugin is updated to work with vBulletin4 and Keith makes the move to upgrade .net.
If we come across something else that fixes it though, we'll definitely give it a try. :tup: