Hello @Jonas,
Thanks for confirming this bug is fixed in 1.2.9.7.3.
Sorry for the trouble once again.
Cheers,