Unfortunately not, this situation used to cause the destroy of deployments to fail in particular circumstances.
This "limitation" is currently by design. Running the uninstall for a software component it never ran the install/configure for could cause many issues and failures if not handled perfectly. i can see circumstances this could be benifical tho particularly if something in the previous deployments was overlooked or not done correctly.
We have attempted to combine some of our software components as a work around. Unfortunatly something appears to have gone wrong with the UI and some deployments just hang now when we click the destroy button...
We are able to destroy individual VMs still and newly created deployments as well...
Any advise here? or perhaps will upgrading to 7.4 help with this?