I've worked around it in build 15.00.36 (already uploaded).
I had to revert Take Command to Visual Studio 2010, because Microsoft did such a thorough job of breaking XP support in Visual Studio 2012 Update 2. And developers can't uninstall Update 2 without uninstalling & reinstalling 2012 (a very lengthy process), or even revert to the original Visual Studio 2012 (which doesn't support XP by design, as opposed to the apparent careless neglect / ineptitude of Update 2). And reverting to Visual Studio 2012 + Update 1 (which does support XP), isn't possible, because Microsoft has removed Update 1 from its web sites.
Those of you clinging to your creaky, slow, insecure, and buggy XP systems in the hopes that Microsoft will relent on its April 2014 end of life date can give up that faint hope. Microsoft's response thus far to the VS2012 Update 2 fiasco has been (1) don't statically link your programs (not an option for Take Command), or (2) don't support XP.