Hi @Markus_Hubner & others following this thread,
I have some news to share! It looks like there was a slight mix-up regarding which release this fix would be included in - it’s actually been included in the current production (build 1202) and was present in our last earlyaccess release as well.
Can you and others impacted by this issue please check to see if the current production release (build 1202) solves this issue for you, without having to go through @crieke’s workaround installer? Please, do let me know the results when you have a moment, thanks!