@RobDraw wrote:
@ed.palisoc wrote:
someone that’s invested quite a bit of faith that a release is vetted enough to at least start up properly, if not at least to not torpedo an entire production environment.
This is exactly why most people wait until any major issues of a new release have been addressed before installing. While this issue is more severe than most, it could have been avoided in a production environment. They also vet the software themselves before implementing it on a live project thus avoiding any lapse in production on live projects.
This was not a scenario where I replaced the stable production environment with the upgrade, nor used it on a project in production. In all the years (decades actually) of using autodesk products, There was never an issue with installing a new version alongside the older one, so that it can indeed be evaluated while using the stable and mature older version. In this case, the installation took out both, and that's not something that should find it's way past QA. When I was at LARGE firms, there were resources to install it on a new and unused computer. Now my own practice, that's more a luxury, but it's not unreasonable to allow the installations to co-exist. I'm not sure why you assumed I threw a "live project" at it, as that wasn't even part of my original post. I simply installed 2020 along side 2019, and that action killed 2019, throwing it also into view mode.