It was Dynatrace in the end for us. We added a 'do not monitor' rule targeting processes where the 'Java main class' matches 'com.inductiveautomation.ignition' and the launcher opened without any issues. Monitoring of the gateway should still work because its main class is not in 'com.inductiveautomation.ignition'.
I don't know if this is relevant for anyone else here but I thought I'd mention it just in case. I think the key takeaway is that it isn't just antivirus but also (in theory) transparent monitoring that can cause this problem.
I suspect that anything that disables class data sharing will cause this problem.
4 Likes