I had this same problem. In my case, I had to disable AWSoundCenter and now GoToMeeting works again. Odd that there is some kind of conflict here. I hope LogMeIn can find a solution so that us Alienware users can go back and enable AWSoundCenter again.
Couldn't connect to meetings again today. Can we be downgraded again?
I have this issue on 3 different PCs... 2 desktops.. each using different hardware (custome made).. and my laptop (MSI GS65) again different hardware and software.... not on alienware.
Is there a list of software that I can disable?
I was a part of the "rollback" group.
I have now been receiving a different generic stating GoToMeeting is a "technical error".
It will not auto-logon, start the desktop app, or run the container app.
I have uninstalled everything, and re-launched the container with no success.
I can host meetings in the browsers.
@AshC I have uninstalled (version 220.127.116.1123), rebooted, and rerun the container and it is also version 18.104.22.16823.
I am unable to start the desktop, only the browser.
Seeing a previous post, I am no longer on the rollback version of v8.38.1.