2016 unexpected quit when 2018 opens a file

The bulk of my work is still done in 2016 pro, it’s very stable on my system and outfitted with the extensions I need and I’m too slammed to move over yet, but I’ve got '17 and '18 pro loaded on the HD so I can geolocate and work with newer files as needed.

If I have 16 open, then go to the finder to open another file that happens to be in '18, then '18 opens and '16 “unexpectedly quits” without bugsplat. If I re-open '16 then the two run fine simultaneously, it just gets jealous when '18 is opening and decides to go home during launch of '18. Anyone else see this behavior? Curious.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.