P: Transform/Resize is constrained by default - Want ability to go back to legacy behavior

This is exactly why I think the "workaround" that Adobe provided is a non-starter.  Update blitzes "fix"

Even worse: installing 2.0.2 removed the Ps User Script which I had installed to block the dreadful change to Constraints in Ps CC 2019. (I was able to replace  the Script from a backed-up copy.)

2.0.2 also overwrote my extensive saved KBSCs, my Workspaces and my Tools presets. Fortunately, I had back-ups of thess as well but this over-writing of Users' Presets simply should NOT .

Hi Lonny... for the same reason, I'm not updating 2018 either.  The little red dot on my CC app can stay on.

I absolutely agree Nolan Conley...I will not even install the update to the 2018 version I am using for fear of Adobe screwing that up as well.

I personally am somewhat afraid to upgrade now.  Seeing the caviler attitude of Adobe toward it's customers really bothers me.  I simply don't understand why or who's idea it was to change a core function that improved nothing and impacted many professionals workflow.  Were the little kids at Adobe bored and said "Gee... let's try this!"  This attitude does NOT instill confidence in the customer's (read PROFESSIONALS) minds.  Someone (or group) at Adobe needs a serious butt kicking.

Thanks! Hopefully, the next version is then usable. That would be the longest time I stick to an old (2018) version:(

Seriously ... new update .. constraint not put back the way it was ?????? Seriously ... Adobe .... JUST FIX IT !

Well, I spoke too soon! And now I'm so confused! When I use Distort, it works right. When I use Transform, it is still the same old problem.
Today, I think that just about the time it looks like Adobe is getting their head on straight again, their head falls off!
By the way, when you look at the long list of fixes an update like this addresses, you have got to wonder why. 
Our engineers would tell us that they can put a product on the market with at least 80% of the problems solved. The other 20% of the problems had to be identified by the end user.
Many time we had to delay a release in order to reach that goal.

I can't reproduce this problem in 20.0.2. I uninstalled 20.0.1 and reinstalled. Now, when I run Distort, it works as it should. What is missing with this update? 

Thanks.