You can't.
I assume it is a bug, and one that has existed since 1.0 of the product.
To get around this issue the custom start code our portal uses first set the VM to something besides "none" - starts it - then sets it back to none.
Please report this to VMware as they seem to not think it is a big deal as it has been around for so long.