Hello @Marius,
Thanks for confirming this and for bringing this up in the first place, much appreciated. I will now be moving this to fixed as the final correction in 1.2.9.7.3 addresses the last standing bug.
Cheers,