Thank you for finding the workaround.
Admittedly, we can't find an explanation for this behavior at the moment, as it doesn't replicate on our machines.
We will try to investigate and also ask for suggestions.