I've never used the quoting functionality here, so I apologize if I goof it up.
This practice is mostly about 'saving them from themselves'.
Famous words many times over from those assuming that people need it.
....the result of it not being in a place (ProgFiles) where the app could do all it needed to or to have Windows treat is properly.
That kinda my point. If an application has that much of an issue with the path of a program's installation location, it stands to reason the issue is with the application design - not the user. From my experience, a large part of an application's codebase is functionality to address all the <insert word of choice here> things that a user can -and probably at some point will- do that they shouldn't do - which should not include restricting them on where they want to install the program.
As it is a trend amongst developers to have the same practice (as you have noted), we are not alone with this mindset.
Birds of a feather flock together, I guess - but that doesn't make it right. I may very well be in the minority with my opinion, but I feel like if I don't express it to the person/entity I'm paying money to for a project or service, then the assumption will continue to be that what is being done is in the interest of "saving people from themselves".
Again, no offense meant - I appreciate your respectful responses and not ignoring them as in many a case with other forums. I take pride in the development work I do, so I speak from a professional standpoint the frustrations I have regarding the decision to remove that option.