I experienced this when upgrading to both 2.4 and to 2.4.1. Each time, after the upgrade, I was unable to use the cloned version of Python and had to delete the cloned directory and recreate it. Not a show stopper, but definitely a time sink . Is there a way to avoid this? I am asking because I will be rolling out 2.4.1 early next week to all of our staff and would like know if there is a work-a-round or simple solution I am missing.