Storyline crashes when trigger conditions added

Hum, it appears this has been an on-going problem for over 2 years!?  I can't understand why such a simple thing as adding a condition to a trigger would crash Storyline?  It looks like my only option is to open a support ticket.  

As I replied in another thread over a year ago, Articulate Tech Support's first suggested "solution," was to disable anti-virus and change my user profile to local admin.  As I elaborated on in this post, the era of everyone being a local admin on their computers is over. Internal IT departments find having fewer users (including those within IT) having administrative privileges means less vectors for cyber-attacks. Suggesting either of these as a possible solution demonstrates a profound ignorance of today's enterprise environments.

Articulate Tech Support's second suggested "solution" was to use the keyboard arrow keys to get to the "Object" option. While that does, for the most part, work, it is entirely kludgy and ignores the underlying issues. I pay for software which works, not software which requires jumping through multiple hoops to get it to sorta-work. Software in the latter column is called "beta," aka "not ready for public sale." As an alpha and beta tester for several of the big names before Articulate was around, I know beta when I see it.

Use the arrow key. Yeah, it would be nice to have that fixed, but it's not that big a deal to push a different button, and it completely solved the problem for me. 

Temporary work arounds are OK, but going on a two year work around is unacceptable.  And further unacceptable with the forthcoming price increase.

I notice from the conversation above that there is not a lot of helpful information coming back from Articulate on this software problem.

From my own experience and judging by the traffic on this issue across many threads, this has been going on for years with repeated promises that it will be fixed in future upgrades but it is still happening despite the so called solutions and workarounds, none of which have worked for me.  

This is not a random thing.  It happens every single time I try to create conditions using Object or Window, and it happens the instant I click on either of those two options.  It can't be a phantom, it must be a fundamental error in the program.  Please fix it.

Well...technically there haven't actually been any promises of the issue being fixed in a future upgrade, because Articulate's line has consistently been "we don't see the problem on our end, so there's nothing for us to fix." The mouthpieces here allegedly pass the issue to the Support "Engineers"...and that's the last anyone hears of it. 2 years and counting 🤬 

Just an FYI.. all of our learning teams using Storyline are having the same issue as you all. It also is the same for creating xAPI statements

Storyline: 3.64.27845.0

Windows 10 Enterprise; version 21H2; build 19044.1706