tfullem,
After doing some research, it looks like this is known behavior when upgrading from TestStand 4.0 to 4.0.1 or 4.0.1f1. I'm sorry if it has impacted your development, but it should not have any effect on your ability to use or license TestStand.
The behavior will be fixed in a future version.
Thank you for the feedback!
Josh W.
Certified TestStand Architect
Formerly blue